CVE-2009-4444

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 66 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 64%
CISA-KEV: Not listedEPSS: 64%CVSS: —Exploit: NoneExposed: 66

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

Microsoft Internet Information Services (IIS) 5.x and 6.x uses only the portion of a filename before a ; (semicolon) character to determine the file extension, which allows remote attackers to bypass intended extension restrictions of third-party upload applications via a filename with a (1) .asp, (2) .cer, or (3) .asa first extension, followed by a semicolon and a safe extension, as demonstrated by the use of asp.dll to handle a .asp;.jpg file.

Live · internet exposure

66 internet-exposed hosts are running an affected version of CVE-2009-4444 right now.

across 23 countries (United States, Canada, China, France, Hong Kong)top: internet_information_services
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

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

Published

December 29, 2009

Last Modified

April 23, 2026

References (12)

Data Freshness Timeline

(refreshed 3× in last 7d / 25× 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-06 02:19 UTCEPSS rescore
  2. 2026-07-06 02:19 UTCEPSS rescore
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-06-28 04:52 UTCEPSS rescore
  5. 2026-06-28 04:52 UTCEPSS rescore
  6. 2026-06-27 03:05 UTCEPSS rescore
  7. 2026-06-25 13:46 UTCEPSS rescore
  8. 2026-06-24 14:02 UTCEPSS rescore
  9. 2026-06-24 14:02 UTCEPSS rescore
  10. 2026-06-23 21:30 UTCEPSS rescore
  11. 2026-06-23 21:29 UTCEPSS rescore
  12. 2026-06-18 17:49 UTCEPSS rescore
  13. 2026-06-18 17:49 UTCEPSS rescore
  14. 2026-06-17 17:49 UTCEPSS rescore
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-16 17:49 UTCEPSS rescore
  17. 2026-06-15 17:44 UTCEPSS rescore
  18. 2026-06-13 22:57 UTCEPSS rescore
  19. 2026-06-13 22:57 UTCEPSS rescore
  20. 2026-06-13 22:57 UTCEPSS rescore
  21. 2026-06-12 23:08 UTCEPSS rescore
  22. 2026-06-12 23:08 UTCEPSS rescore
  23. 2026-06-11 13:56 UTCEPSS rescore
  24. 2026-06-10 22:14 UTCEPSS rescore
  25. 2026-06-10 13:17 UTCEPSS rescore
Show 32 more
  1. 2026-06-07 15:22 UTCEPSS rescore
  2. 2026-06-07 15:22 UTCEPSS rescore
  3. 2026-06-05 22:44 UTCEPSS rescore
  4. 2026-06-05 22:44 UTCEPSS rescore
  5. 2026-06-05 06:07 UTCEPSS rescore
  6. 2026-06-05 06:07 UTCEPSS rescore
  7. 2026-06-02 20:10 UTCEPSS rescore
  8. 2026-06-02 20:10 UTCEPSS rescore
  9. 2026-06-01 13:49 UTCEPSS rescore
  10. 2026-06-01 13:49 UTCEPSS rescore
  11. 2026-05-31 00:14 UTCEPSS rescore
  12. 2026-05-31 00:13 UTCEPSS rescore
  13. 2026-05-29 13:40 UTCEPSS rescore
  14. 2026-05-29 13:14 UTCEG score recompute
  15. 2026-05-29 13:14 UTCGHSA enrichment
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-26 13:41 UTCEPSS rescore
  19. 2026-05-26 13:41 UTCEPSS rescore
  20. 2026-05-26 07:16 UTCEPSS rescore
  21. 2026-05-26 07:16 UTCEPSS rescore
  22. 2026-05-24 16:43 UTCEPSS rescore
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-22 21:15 UTCEPSS rescore
  25. 2026-05-22 21:15 UTCEPSS rescore
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-20 22:37 UTCEPSS rescore
  28. 2026-05-20 22:37 UTCEPSS rescore
  29. 2026-05-20 11:21 UTCEPSS rescore
  30. 2026-05-20 11:21 UTCEPSS rescore
  31. 2026-05-18 21:29 UTCEPSS rescore
  32. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2009-4444?
CVE-2009-4444 is a none vulnerability published on December 29, 2009. Microsoft Internet Information Services (IIS) 5.x and 6.x uses only the portion of a filename before a ; (semicolon) character to determine the file extension, which allows remote attackers to bypass intended extension restrictions of third-party upload applications via a filename with a (1) .asp,…
When was CVE-2009-4444 disclosed?
CVE-2009-4444 was first published in the National Vulnerability Database on December 29, 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-4444 actively exploited?
CVE-2009-4444 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2009-4444?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-4444, 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-4444

Explore →

Is Your Infrastructure Affected by CVE-2009-4444?

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

Start Free Scan →Browse All CVEs