CVE-2009-2629

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 75.1% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 1 internet-facing service (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • High exploitation likelihood — EPSS 75%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 75%CVSS v2: 7.5Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: 1

A fix is available — apply it.

Buffer underflow in src/http/ngx_http_parse.c in nginx 0.1.0 through 0.5.37, 0.6.x before 0.6.39, 0.7.x before 0.7.62, and 0.8.x before 0.8.15 allows remote attackers to execute arbitrary code via crafted HTTP requests.

Internet exposure · derived from Shodan data

1 internet-facing service (distinct ip:port) on record running a version that maps to CVE-2009-2629, in our KEV-Exposure radar’s Shodan-derived sample.

across 1 countries (Saudi Arabia)top: nginx
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5HIGHlow confidence
EG Risk
68
EG Risk 68/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation75% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
75%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 15, 2009

Last Modified

April 23, 2026

References (20)

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 0.7.61-3: fixed in 0.7.61-3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 0.7.61-3: fixed in 0.7.61-3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 0.7.61-3: fixed in 0.7.61-3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 0.7.61-3: fixed in 0.7.61-3
—
Debian:4.0(1)
PackageVulnerable rangeFix by version rangeDependents
nginx0.4.13-2
  • every version up to 0.4.13-2+etch2: fixed in 0.4.13-2+etch2
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
nginx0.6.32-3
  • every version up to 0.6.32-3+lenny2: fixed in 0.6.32-3+lenny2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 12× 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-10-09 20:00 UTCEPSS rescore
  2. 2026-10-07 23:37 UTCEPSS rescore
  3. 2026-10-04 23:15 UTCEPSS rescore
  4. 2026-10-03 05:09 UTCOSV refresh
  5. 2026-09-29 07:59 UTCEG score recompute
  6. 2026-09-26 15:52 UTCEPSS rescore
  7. 2026-09-24 13:57 UTCEPSS rescore
  8. 2026-09-17 19:20 UTCEPSS rescore
  9. 2026-09-14 02:20 UTCOSV refresh
  10. 2026-09-13 16:40 UTCEPSS rescore
  11. 2026-09-12 14:54 UTCEPSS rescore
  12. 2026-09-10 09:24 UTCEPSS rescore
  13. 2026-09-06 13:41 UTCEPSS rescore
  14. 2026-09-05 15:22 UTCEPSS rescore
  15. 2026-08-28 21:34 UTCEPSS rescore
  16. 2026-08-26 03:40 UTCOSV refresh
  17. 2026-08-25 13:43 UTCEPSS rescore
  18. 2026-08-19 16:58 UTCEPSS rescore
  19. 2026-08-15 01:24 UTCEPSS rescore
  20. 2026-08-09 20:10 UTCOSV refresh
  21. 2026-07-30 16:22 UTCEPSS rescore
  22. 2026-07-26 13:38 UTCEG score recompute▲ 7.50
  23. 2026-07-24 20:41 UTCOSV refresh
  24. 2026-07-24 14:12 UTCEPSS rescore
  25. 2026-07-23 00:59 UTCEG score recompute
Show 67 more
  1. 2026-07-23 00:37 UTCEG score recompute▼ 7.40
  2. 2026-07-23 00:04 UTCEG score recompute▲ 7.40
  3. 2026-07-22 21:43 UTCEG score recompute
  4. 2026-07-22 14:03 UTCEPSS rescore
  5. 2026-07-20 17:03 UTCEPSS rescore
  6. 2026-07-20 17:03 UTCEPSS rescore
  7. 2026-07-18 09:59 UTCEPSS rescore
  8. 2026-07-16 16:58 UTCEPSS rescore
  9. 2026-07-15 16:54 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-13 06:07 UTCEPSS rescore
  12. 2026-07-11 08:22 UTCEPSS rescore
  13. 2026-07-11 08:22 UTCEPSS rescore
  14. 2026-07-08 15:10 UTCEPSS rescore
  15. 2026-07-07 16:11 UTCOSV refresh
  16. 2026-07-05 02:26 UTCEPSS rescore
  17. 2026-07-05 02:26 UTCEPSS rescore
  18. 2026-07-01 15:02 UTCEPSS rescore
  19. 2026-06-29 14:02 UTCEPSS rescore
  20. 2026-06-29 14:02 UTCEPSS rescore
  21. 2026-06-28 04:52 UTCEPSS rescore
  22. 2026-06-28 04:52 UTCEPSS rescore
  23. 2026-06-25 13:46 UTCEPSS rescore
  24. 2026-06-25 13:46 UTCEPSS rescore
  25. 2026-06-23 21:29 UTCEPSS rescore
  26. 2026-06-23 21:29 UTCEPSS rescore
  27. 2026-06-22 14:22 UTCEPSS rescore
  28. 2026-06-22 14:22 UTCEPSS rescore
  29. 2026-06-19 03:35 UTCOSV refresh
  30. 2026-06-18 17:49 UTCEPSS rescore
  31. 2026-06-18 17:49 UTCEPSS rescore
  32. 2026-06-17 17:49 UTCEPSS rescore
  33. 2026-06-17 17:49 UTCEPSS rescore
  34. 2026-06-16 17:49 UTCEPSS rescore
  35. 2026-06-16 17:49 UTCEPSS rescore
  36. 2026-06-15 17:44 UTCEPSS rescore
  37. 2026-06-13 22:57 UTCEPSS rescore
  38. 2026-06-12 23:08 UTCEPSS rescore
  39. 2026-06-12 23:08 UTCEPSS rescore
  40. 2026-06-10 22:14 UTCEPSS rescore
  41. 2026-06-06 13:44 UTCEPSS rescore
  42. 2026-06-06 13:44 UTCEPSS rescore
  43. 2026-06-06 13:44 UTCEPSS rescore
  44. 2026-06-05 22:44 UTCEPSS rescore
  45. 2026-06-05 22:44 UTCEPSS rescore
  46. 2026-06-05 06:07 UTCEPSS rescore
  47. 2026-06-04 13:09 UTCEPSS rescore
  48. 2026-06-04 13:09 UTCEPSS rescore
  49. 2026-06-01 13:49 UTCEPSS rescore
  50. 2026-06-01 13:49 UTCEPSS rescore
  51. 2026-05-31 22:28 UTCEPSS rescore
  52. 2026-05-31 22:28 UTCEPSS rescore
  53. 2026-05-31 00:13 UTCEPSS rescore
  54. 2026-05-31 00:13 UTCEPSS rescore
  55. 2026-05-30 15:15 UTCEG score recompute
  56. 2026-05-30 15:15 UTCGHSA enrichment
  57. 2026-05-29 13:40 UTCEPSS rescore
  58. 2026-05-26 13:41 UTCEPSS rescore
  59. 2026-05-26 13:41 UTCEPSS rescore
  60. 2026-05-25 05:07 UTCOSV refresh
  61. 2026-05-22 21:15 UTCEPSS rescore
  62. 2026-05-22 21:15 UTCEPSS rescore
  63. 2026-05-20 22:37 UTCEPSS rescore
  64. 2026-05-20 22:37 UTCEPSS rescore
  65. 2026-05-20 11:21 UTCEPSS rescore
  66. 2026-05-20 11:20 UTCEPSS rescore
  67. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-14830✓ verified
    First seen Aug 29, 2010

    Nginx 0.6.38 - Heap Corruption

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(4)

What is CVE-2009-2629?
CVE-2009-2629 is a high vulnerability published on September 15, 2009. Buffer underflow in src/http/ngxhttpparse.c in nginx 0.1.0 through 0.5.37, 0.6.x before 0.6.39, 0.7.x before 0.7.62, and 0.8.x before 0.8.15 allows remote attackers to execute arbitrary code via crafted HTTP requests.
When was CVE-2009-2629 disclosed?
CVE-2009-2629 was first published on September 15, 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-2629 actively exploited?
CVE-2009-2629 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 75% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-2629?
A fix for CVE-2009-2629 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2009-2629

Explore →

Is Your Infrastructure Affected by CVE-2009-2629?

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

Book a Demo →Browse All CVEs