CVE-2015-3183

MEDIUMCVSS v2 · 5.05.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — 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:L/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 73.3% 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
Elevated
5.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 252 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 73%
CISA-KEV: Not listedEPSS PROB: 73%CVSS v2: 5.0Exploit: Elevated riskExposed: 252

A fix is available — apply it.

The chunked transfer coding implementation in the Apache HTTP Server before 2.4.14 does not properly parse chunk headers, which allows remote attackers to conduct HTTP request smuggling attacks via a crafted request, related to mishandling of large chunk-size values and invalid chunk-extension characters in modules/http/http_filters.c.

Live · internet exposure

252 internet-exposed hosts are running an affected version of CVE-2015-3183 right now.

across 45 countries (United States, Japan, United Kingdom, Italy, Germany)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)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0(low)
EG Risk
56(Track)
EG Risk 56/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
Severity50% × 45%
Exploitation73% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
73%
EPSS %ILE
99%
KEV
Not listed

Published

July 20, 2015

Last Modified

May 6, 2026

References (106)

Vendor Advisories for CVE-2015-3183(1)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2.2-bin (2.4.10-9ubuntu1.1) @ vivid2026-05-23ubuntu
redhatpatch2016-10-12redhat
redhattomcat-native-0:1.1.34-5.redhat_1.ep6.el62016-10-12redhat
redhattomcat-native-0:1.1.34-5.redhat_1.ep6.el72016-10-12redhat
redhathttpd2016-01-21redhat
redhatmod_cluster-native-0:1.2.9-6.Final_redhat_2.ep6.el72016-01-21redhat
redhattomcat-vault-0:1.0.8-4.Final_redhat_4.1.ep7.el62015-12-16redhat
redhatpatch2015-12-16redhat
redhattomcat-vault-0:1.0.8-4.Final_redhat_4.1.ep7.el72015-12-16redhat
redhathttpd-0:2.4.6-31.ael7b_1.12015-08-24redhat
redhathttpd-0:2.2.15-47.el6_72015-08-24redhat
redhathttpd24-httpd-0:2.4.12-6.el7.12015-08-24redhat

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

(11)

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

Frequently asked(4)

What is CVE-2015-3183?
CVE-2015-3183 is a medium vulnerability published on July 20, 2015. The chunked transfer coding implementation in the Apache HTTP Server before 2.4.14 does not properly parse chunk headers, which allows remote attackers to conduct HTTP request smuggling attacks via a crafted request, related to mishandling of large chunk-size values and invalid chunk-extension…
When was CVE-2015-3183 disclosed?
CVE-2015-3183 was first published in the National Vulnerability Database on July 20, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-3183 actively exploited?
CVE-2015-3183 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73% probability of exploitation in the next 30 days, which ranks it in the top 0.6% of all scored CVEs.
How do I remediate CVE-2015-3183?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-3183, 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-2015-3183

Explore →

Is Your Infrastructure Affected by CVE-2015-3183?

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

Start Free Scan →Browse All CVEs