CVE-2006-3918

MEDIUMCVSS v2 · 4.34.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — v2 rates that MEDIUM (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:M/Au:N/C:N/I:P/A:N. 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 94.9% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Trending — 4 sources updated this weekWeaponized
4.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 7 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 95%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 95%CVSS v2: 4.3Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 7

A fix is available — apply it.

http_protocol.c in (1) IBM HTTP Server 6.0 before 6.0.2.13 and 6.1 before 6.1.0.1, and (2) Apache HTTP Server 1.3 before 1.3.35, 2.0 before 2.0.58, and 2.2 before 2.2.2, does not sanitize the Expect header from an HTTP request when it is reflected back in an error message, which might allow cross-site scripting (XSS) style attacks using web client components that can send arbitrary headers in requests, as demonstrated using a Flash SWF file.

Live · internet exposure

7 internet-exposed hosts are running an affected version of CVE-2006-3918 right now.

across 5 countries (Taiwan, United States, Japan, Poland, Switzerland)top: http_server
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 v2.0 (legacy)
4.3MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.3(low)
EG Risk
62(Track)
EG Risk 62/100SSVC: Track

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
Severity43% × 45%
Exploitation95% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
95%
EPSS %ILE
100%
KEV
Not listed

Published

July 28, 2006

Last Modified

April 16, 2026

References (112)

Vendor Advisories for CVE-2006-3918(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-mpm-perchild (2.2.4-3ubuntu0.1) @ gutsy2026-07-23ubuntu
redhatxml-commons-0:1.3.02-2jpp_1rh2010-08-04redhat
redhatrhn-modperl-0:1.29-16.rhel42008-06-30redhat
redhatpatch2006-09-29redhat
redhathttpd-0:2.0.52-28.ent2006-08-10redhat
redhatpatch2006-08-08redhat

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.

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 26× 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-26 13:29 UTCEG score recompute▲ 4.30
  2. 2026-07-23 00:51 UTCEG score recompute
  3. 2026-07-23 00:39 UTCVendor advisory
  4. 2026-07-23 00:39 UTCGHSA enrichment
  5. 2026-07-23 00:36 UTCVendor advisory
  6. 2026-07-23 00:36 UTCGHSA enrichment
  7. 2026-07-23 00:36 UTCVendor advisory
  8. 2026-07-23 00:36 UTCGHSA enrichment
  9. 2026-07-23 00:34 UTCVendor advisory
  10. 2026-07-23 00:34 UTCGHSA enrichment
  11. 2026-07-23 00:33 UTCVendor advisory
  12. 2026-07-23 00:33 UTCGHSA enrichment
  13. 2026-07-23 00:32 UTCVendor advisory
  14. 2026-07-23 00:32 UTCGHSA enrichment
  15. 2026-07-23 00:30 UTCVendor advisory
  16. 2026-07-23 00:30 UTCGHSA enrichment
  17. 2026-07-23 00:30 UTCEG score recompute▼ 9.00
  18. 2026-07-22 23:55 UTCEG score recompute
  19. 2026-07-22 21:35 UTCEG score recompute
  20. 2026-07-20 17:02 UTCEPSS rescore
  21. 2026-07-15 16:53 UTCEPSS rescore
  22. 2026-07-13 06:07 UTCEPSS rescore
  23. 2026-07-13 06:07 UTCEPSS rescore
  24. 2026-07-11 08:22 UTCEPSS rescore
  25. 2026-07-09 19:03 UTCEPSS rescore
Show 35 more
  1. 2026-07-08 20:39 UTCOSV refresh
  2. 2026-06-27 03:04 UTCEPSS rescore
  3. 2026-06-25 13:46 UTCEPSS rescore
  4. 2026-06-24 14:01 UTCEPSS rescore
  5. 2026-06-24 14:01 UTCEPSS rescore
  6. 2026-06-23 21:29 UTCEPSS rescore
  7. 2026-06-23 21:29 UTCEPSS rescore
  8. 2026-06-22 14:22 UTCEPSS rescore
  9. 2026-06-21 01:56 UTCEPSS rescore
  10. 2026-06-20 08:12 UTCOSV refresh
  11. 2026-06-19 19:22 UTCEPSS rescore
  12. 2026-06-19 19:22 UTCEPSS rescore
  13. 2026-06-15 17:44 UTCEPSS rescore
  14. 2026-06-13 22:56 UTCEPSS rescore
  15. 2026-06-12 23:08 UTCEPSS rescore
  16. 2026-06-10 22:14 UTCEPSS rescore
  17. 2026-06-06 13:44 UTCEPSS rescore
  18. 2026-06-06 13:44 UTCEPSS rescore
  19. 2026-06-05 22:43 UTCEPSS rescore
  20. 2026-05-31 22:28 UTCEPSS rescore
  21. 2026-05-31 07:28 UTCEG score recompute
  22. 2026-05-31 07:28 UTCVendor advisory
  23. 2026-05-31 07:28 UTCGHSA enrichment
  24. 2026-05-27 13:37 UTCEPSS rescore
  25. 2026-05-27 13:37 UTCEPSS rescore
  26. 2026-05-26 13:41 UTCEPSS rescore
  27. 2026-05-26 13:41 UTCEPSS rescore
  28. 2026-05-26 07:16 UTCEPSS rescore
  29. 2026-05-26 07:16 UTCEPSS rescore
  30. 2026-05-22 23:25 UTCOSV refresh
  31. 2026-05-22 21:15 UTCEPSS rescore
  32. 2026-05-22 21:15 UTCEPSS rescore
  33. 2026-05-20 22:36 UTCEPSS rescore
  34. 2026-05-20 22:36 UTCEPSS rescore
  35. 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-28424✓ verified
    First seen Aug 24, 2006

    Apache 1.3.35/2.0.58/2.2.2 - Arbitrary HTTP Request Headers Security

    Open source ↗

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2006-3918?
CVE-2006-3918 is a medium vulnerability published on July 28, 2006. http_protocol.c in (1) IBM HTTP Server 6.0 before 6.0.2.13 and 6.1 before 6.1.0.1, and (2) Apache HTTP Server 1.3 before 1.3.35, 2.0 before 2.0.58, and 2.2 before 2.2.2, does not sanitize the Expect header from an HTTP request when it is reflected back in an error message, which might allow…
When was CVE-2006-3918 disclosed?
CVE-2006-3918 was first published in the National Vulnerability Database on July 28, 2006, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-3918 actively exploited?
CVE-2006-3918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
How do I remediate CVE-2006-3918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-3918, 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-2006-3918

Explore →

Is Your Infrastructure Affected by CVE-2006-3918?

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

Start Free Scan →Browse All CVEs