Skip to content
skopnix
← Sigma detections

Sigma · CVE exploitation

CVE-2026-109619 exploitation IP indicators

severity
high
confidence
75/100
generated
14 Nov 2026
Linked CVE
CVE-2026-109619

2 IP indicators threat feeds tag with CVE-2026-109619, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).

False-positive notes

2 indicators. Evidence: 2 listed by 2 or more independent non-scanner feed publishers. Listed by 6 independent sources in all. Newest feed sighting 2026-11-13, oldest 2026-10-28 (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-109619 exploitation IP indicatorsid: 03e9d27c-7c76-5ab9-8022-6d70f7bc61b7status: experimentaldescription: 2 IP indicators threat feeds tag with CVE-2026-109619, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).references:  - https://skopnix.com/cve/CVE-2026-109619author: skopnixdate: '2026-11-14'tags:  - attack.command-and-control  - attack.t1071logsource:  category: firewalldetection:  selection:    dst_ip:      - 162.35.99.94      - 122.10.110.72  condition: selectionfalsepositives:  - Legitimate services sharing the address; verify against skopnix confidence + last_seenlevel: high

skopnix-sigma-cve-cve-2026-109619-ip-53822fe7.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.