CVE-2015-2080

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 74.9%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 75%
CISA-KEV: Not listedEPSS: 75%CVSS: 7.5Exploit: NoneExposed: 0

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

The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process memory via illegal characters in an HTTP header, aka JetLeak.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
99.5%
KEV
Not listed

Published

October 7, 2016

Last Modified

May 6, 2026

References (22)

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.eclipse.jetty:jetty-server7.0.0.M0 ... 9.2.8.v20150217 (153 versions)9.2.9.v20150224—

Data Freshness Timeline

(refreshed 7× 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-22 21:57 UTCEG score recompute▼ 1.50
  2. 2026-07-22 14:04 UTCEPSS rescore
  3. 2026-07-21 15:21 UTCEPSS rescore
  4. 2026-07-21 15:21 UTCEPSS rescore
  5. 2026-07-20 17:03 UTCEPSS rescore
  6. 2026-07-16 16:59 UTCEPSS rescore
  7. 2026-07-16 16:59 UTCEPSS rescore
  8. 2026-07-15 16:54 UTCEPSS rescore
  9. 2026-07-15 16:54 UTCEPSS rescore
  10. 2026-07-15 01:56 UTCEPSS rescore
  11. 2026-07-12 05:42 UTCEPSS rescore
  12. 2026-07-11 08:23 UTCEPSS rescore
  13. 2026-07-08 15:10 UTCEPSS rescore
  14. 2026-07-06 02:20 UTCEPSS rescore
  15. 2026-07-02 15:21 UTCEPSS rescore
  16. 2026-07-01 15:02 UTCEPSS rescore
  17. 2026-07-01 15:02 UTCEPSS rescore
  18. 2026-06-30 23:19 UTCEPSS rescore
  19. 2026-06-30 23:19 UTCEPSS rescore
  20. 2026-06-29 14:03 UTCEPSS rescore
  21. 2026-06-27 03:05 UTCEPSS rescore
  22. 2026-06-25 13:47 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-24 14:02 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
Show 29 more
  1. 2026-06-23 21:30 UTCEPSS rescore
  2. 2026-06-21 01:57 UTCEPSS rescore
  3. 2026-06-21 01:57 UTCEPSS rescore
  4. 2026-06-17 17:49 UTCEPSS rescore
  5. 2026-06-15 17:45 UTCEPSS rescore
  6. 2026-06-12 23:09 UTCEPSS rescore
  7. 2026-06-10 22:15 UTCEPSS rescore
  8. 2026-06-06 13:45 UTCEPSS rescore
  9. 2026-06-05 22:44 UTCEPSS rescore
  10. 2026-06-05 06:08 UTCEPSS rescore
  11. 2026-06-05 06:08 UTCEPSS rescore
  12. 2026-06-02 20:10 UTCEPSS rescore
  13. 2026-06-02 20:10 UTCEPSS rescore
  14. 2026-06-01 13:49 UTCEPSS rescore
  15. 2026-06-01 13:49 UTCEPSS rescore
  16. 2026-05-29 13:41 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-26 07:16 UTCEPSS rescore
  20. 2026-05-26 07:16 UTCEPSS rescore
  21. 2026-05-24 16:43 UTCEPSS rescore
  22. 2026-05-23 15:10 UTCEPSS rescore
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-22 21:15 UTCEPSS rescore
  25. 2026-05-22 18:27 UTCEG score recompute
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-20 22:37 UTCEPSS rescore
  28. 2026-05-18 21:30 UTCEPSS rescore
  29. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(2 references)

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-39455
    First seen Feb 17, 2016

    Inductive Automation Ignition 7.8.1 - Remote Leakage Of Shared Buffers

    Open source ↗
  • Nucleihttp/cves/2015/CVE-2015-2080.yaml
    First seen Jan 1, 2015

    Eclipse Jetty <9.2.9.v20150224 - Sensitive Information Leakage

    Open source ↗

Frequently asked(5)

What is CVE-2015-2080?
CVE-2015-2080 is a high vulnerability published on October 7, 2016. The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process memory via illegal characters in an HTTP header, aka JetLeak.
When was CVE-2015-2080 disclosed?
CVE-2015-2080 was first published in the National Vulnerability Database on October 7, 2016, 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-2080 actively exploited?
CVE-2015-2080 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2015-2080?
CVE-2015-2080 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2015-2080?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-2080, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-2080

Explore →

Is Your Infrastructure Affected by CVE-2015-2080?

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

Start Free Scan →Browse All CVEs