← Sigma detections
Sigma · CVE exploitation
CVE-2026-41940 exploitation IP indicators
- severity
- high
- confidence
- 75/100
- generated
- 20 Nov 2026
- Linked CVE
- CVE-2026-41940
1 IP indicator threat feeds tag with CVE-2026-41940, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).
False-positive notes
1 indicator. Evidence: 1 by one feed with confidence >= 75 (lowest 75). Listed by 1 independent source in all. Newest feed sighting 2026-11-20, oldest 2026-11-20 (a live actor sweep accepts at most 90 days). Screened against reserved space, public known-good lists (CDN / cloud / scanners / top sites), internet-noise reputation when enriched, and sinkhole address lists. Re-validate against last_seen before blocking: infrastructure is re-assigned.
References
title: Skopnix - CVE-2026-41940 exploitation IP indicatorsid: 1992b7e9-40ba-535a-a424-85a8afa25a60status: experimentaldescription: 1 IP indicator threat feeds tag with CVE-2026-41940, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).references: - https://skopnix.com/cve/CVE-2026-41940author: skopnixdate: '2026-11-20'tags: - attack.command-and-control - attack.t1071logsource: category: firewalldetection: selection: dst_ip: - 92.119.178.59 condition: selectionfalsepositives: - Legitimate services sharing the address; verify against skopnix confidence + last_seenlevel: highskopnix-sigma-cve-cve-2026-41940-ip-e0ad38a4.yml
How to deploy on Sigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 3
- Promote to an alert once a week of results is clean on your data.
- Check
- The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.