CVE-2009-3641

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 39%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Snort before 2.8.5.1, when the -v option is enabled, allows remote attackers to cause a denial of service (application crash) via a crafted IPv6 packet that uses the (1) TCP or (2) ICMP protocol.

CVSS v3
—
EG Score
0.0(none)
EPSS
98.4%
KEV
Not listed

Published

October 28, 2009

Last Modified

April 23, 2026

References (24)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
debian:11snort @ 2.8.5.2-1—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

(refreshed 4× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 15:11 UTCOSV refresh
  2. 2026-07-06 16:23 UTCEPSS rescore
  3. 2026-07-04 06:27 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-30 23:19 UTCEPSS rescore
  6. 2026-06-28 14:03 UTCEPSS rescore
  7. 2026-06-28 04:52 UTCEPSS rescore
  8. 2026-06-28 04:52 UTCEPSS rescore
  9. 2026-06-27 03:05 UTCEPSS rescore
  10. 2026-06-25 13:46 UTCEPSS rescore
  11. 2026-06-25 13:46 UTCEPSS rescore
  12. 2026-06-24 14:02 UTCEPSS rescore
  13. 2026-06-24 14:02 UTCEPSS rescore
  14. 2026-06-23 21:29 UTCEPSS rescore
  15. 2026-06-23 21:29 UTCEPSS rescore
  16. 2026-06-21 01:56 UTCEPSS rescore
  17. 2026-06-21 01:56 UTCEPSS rescore
  18. 2026-06-19 02:35 UTCOSV refresh
  19. 2026-06-18 17:49 UTCEPSS rescore
  20. 2026-06-18 17:49 UTCEPSS rescore
  21. 2026-06-17 17:49 UTCEPSS rescore
  22. 2026-06-17 17:49 UTCEPSS rescore
  23. 2026-06-16 17:49 UTCEPSS rescore
  24. 2026-06-16 17:49 UTCEPSS rescore
  25. 2026-06-15 17:44 UTCEPSS rescore
Show 42 more
  1. 2026-06-13 22:57 UTCEPSS rescore
  2. 2026-06-12 23:08 UTCEPSS rescore
  3. 2026-06-12 23:08 UTCEPSS rescore
  4. 2026-06-10 22:14 UTCEPSS rescore
  5. 2026-06-10 13:17 UTCEPSS rescore
  6. 2026-06-07 15:22 UTCEPSS rescore
  7. 2026-06-07 15:22 UTCEPSS rescore
  8. 2026-06-06 13:44 UTCEPSS rescore
  9. 2026-06-06 13:44 UTCEPSS rescore
  10. 2026-06-06 13:44 UTCEPSS rescore
  11. 2026-06-05 22:44 UTCEPSS rescore
  12. 2026-06-05 22:44 UTCEPSS rescore
  13. 2026-06-05 06:07 UTCEPSS rescore
  14. 2026-06-04 13:09 UTCEPSS rescore
  15. 2026-06-04 13:09 UTCEPSS rescore
  16. 2026-06-02 20:10 UTCEPSS rescore
  17. 2026-06-02 20:10 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-05-31 22:28 UTCEPSS rescore
  21. 2026-05-31 22:28 UTCEPSS rescore
  22. 2026-05-31 00:13 UTCEPSS rescore
  23. 2026-05-31 00:13 UTCEPSS rescore
  24. 2026-05-30 14:46 UTCEG score recompute
  25. 2026-05-30 14:46 UTCGHSA enrichment
  26. 2026-05-29 13:40 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-27 13:38 UTCEPSS rescore
  31. 2026-05-27 13:38 UTCEPSS rescore
  32. 2026-05-26 13:41 UTCEPSS rescore
  33. 2026-05-26 13:41 UTCEPSS rescore
  34. 2026-05-26 07:16 UTCEPSS rescore
  35. 2026-05-26 07:16 UTCEPSS rescore
  36. 2026-05-24 16:43 UTCEPSS rescore
  37. 2026-05-22 03:06 UTCOSV refresh
  38. 2026-05-20 22:37 UTCEPSS rescore
  39. 2026-05-20 22:37 UTCEPSS rescore
  40. 2026-05-20 11:21 UTCEPSS rescore
  41. 2026-05-20 11:20 UTCEPSS rescore
  42. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-9969✓ verified
    First seen Oct 23, 2009

    Snort 2.8.5 - IPv6 Denial of Service

    Open source ↗
  • Exploit-DBEDB-33306✓ verified
    First seen Oct 22, 2009

    Snort 2.8.5 - Multiple Denial of Service Vulnerabilities

    Open source ↗

Related CVEs(same product)

Frequently asked(4)

What is CVE-2009-3641?
CVE-2009-3641 is a none vulnerability published on October 28, 2009. Snort before 2.8.5.1, when the -v option is enabled, allows remote attackers to cause a denial of service (application crash) via a crafted IPv6 packet that uses the (1) TCP or (2) ICMP protocol.
When was CVE-2009-3641 disclosed?
CVE-2009-3641 was first published in the National Vulnerability Database on October 28, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2009-3641 actively exploited?
CVE-2009-3641 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2009-3641?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-3641, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2009-3641

Explore →

Is Your Infrastructure Affected by CVE-2009-3641?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs