CVE-2019-10405

HIGHNVD 5.47.7▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.7 because EPSS predicts 66% probability of exploitation within the next 30 days (top 0.8% of all CVEs). NVD baseline CVSS 5.4 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
7.7EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 77 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 66%
CISA-KEV: Not listedEPSS PROB: 66%CVSS: 5.4Exploit: Elevated riskExposed: 77

A fix is available — apply it.

Jenkins 2.196 and earlier, LTS 2.176.3 and earlier printed the value of the "Cookie" HTTP request header on the /whoAmI/ URL, allowing attackers exploiting another XSS vulnerability to obtain the HTTP session cookie despite it being marked HttpOnly.

Live · internet exposure

77 internet-exposed hosts are running an affected version of CVE-2019-10405 right now.

across 17 countries (United States, China, Japan, Germany, Canada)top: jenkins
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
5.4
EG Score
7.7(high)
EG Risk
65(Track)
EG Risk 65/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
Severity77% × 45%
Exploitation66% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
66%
EPSS %ILE
99%
KEV
Not listed

Published

September 25, 2019

Last Modified

November 21, 2024

References (4)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjenkins-0:2.204.1.1578490170-1.el72020-01-23redhat
redhatjenkins-0:2.176.4.1578402941-1.el72020-01-14redhat

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.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.jenkins-ci.main:jenkins-core2.177 ... 2.196 (22 versions)2.197—

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 24× 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 14:51 UTCEPSS rescore
  2. 2026-07-24 14:14 UTCEPSS rescore
  3. 2026-07-24 14:14 UTCEPSS rescore
  4. 2026-07-23 14:15 UTCEPSS rescore
  5. 2026-07-23 01:38 UTCEG score recompute▲ 2.30
  6. 2026-07-22 22:18 UTCEG score recompute
  7. 2026-07-22 14:05 UTCEPSS rescore
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-20 05:16 UTCOSV refresh
  10. 2026-07-18 10:01 UTCEPSS rescore
  11. 2026-07-15 16:55 UTCEPSS rescore
  12. 2026-07-13 22:27 UTCEPSS rescore
  13. 2026-07-12 05:43 UTCEPSS rescore
  14. 2026-07-11 08:24 UTCEPSS rescore
  15. 2026-07-09 19:06 UTCEPSS rescore
  16. 2026-07-06 16:25 UTCEPSS rescore
  17. 2026-07-04 06:28 UTCEPSS rescore
  18. 2026-07-04 06:28 UTCEPSS rescore
  19. 2026-07-02 22:05 UTCOSV refresh
  20. 2026-07-02 16:56 UTCEPSS rescore
  21. 2026-07-01 15:03 UTCEPSS rescore
  22. 2026-07-01 15:03 UTCEPSS rescore
  23. 2026-06-30 23:20 UTCEPSS rescore
  24. 2026-06-30 23:20 UTCEPSS rescore
  25. 2026-06-27 03:06 UTCEPSS rescore
Show 33 more
  1. 2026-06-27 03:06 UTCEPSS rescore
  2. 2026-06-25 13:47 UTCEPSS rescore
  3. 2026-06-25 13:47 UTCEPSS rescore
  4. 2026-06-23 21:30 UTCEPSS rescore
  5. 2026-06-23 21:30 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-21 01:57 UTCEPSS rescore
  8. 2026-06-18 17:50 UTCEPSS rescore
  9. 2026-06-17 17:50 UTCEPSS rescore
  10. 2026-06-16 17:50 UTCEPSS rescore
  11. 2026-06-15 17:45 UTCEPSS rescore
  12. 2026-06-14 18:13 UTCOSV refresh
  13. 2026-06-12 23:09 UTCEPSS rescore
  14. 2026-06-11 13:58 UTCEPSS rescore
  15. 2026-06-11 13:58 UTCEPSS rescore
  16. 2026-06-10 22:16 UTCEPSS rescore
  17. 2026-06-08 14:15 UTCEPSS rescore
  18. 2026-06-08 14:14 UTCEPSS rescore
  19. 2026-06-06 13:45 UTCEPSS rescore
  20. 2026-06-06 13:45 UTCEPSS rescore
  21. 2026-06-05 22:45 UTCEPSS rescore
  22. 2026-06-05 22:45 UTCEPSS rescore
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-05 06:08 UTCEPSS rescore
  25. 2026-06-02 20:11 UTCEPSS rescore
  26. 2026-06-01 13:50 UTCEPSS rescore
  27. 2026-06-01 13:50 UTCEPSS rescore
  28. 2026-05-31 00:14 UTCEPSS rescore
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-29 13:42 UTCEPSS rescore
  31. 2026-05-28 13:43 UTCEPSS rescore
  32. 2026-05-27 13:59 UTCEG score recompute
  33. 2026-05-27 13:59 UTCVendor advisory

Publicly available exploits

(1 reference)

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

  • Nucleihttp/cves/2019/CVE-2019-10405.yaml
    First seen Jan 1, 2019

    Jenkins <=2.196 - Cookie Exposure

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-10405?
CVE-2019-10405 is a high vulnerability published on September 25, 2019. Jenkins 2.196 and earlier, LTS 2.176.3 and earlier printed the value of the "Cookie" HTTP request header on the /whoAmI/ URL, allowing attackers exploiting another XSS vulnerability to obtain the HTTP session cookie despite it being marked HttpOnly.
When was CVE-2019-10405 disclosed?
CVE-2019-10405 was first published in the National Vulnerability Database on September 25, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-10405 actively exploited?
CVE-2019-10405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 66% probability of exploitation in the next 30 days, which ranks it in the top 0.8% of all scored CVEs.
What is the CVSS score of CVE-2019-10405?
CVE-2019-10405 has a CVSS v3 base score of 5.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.7.
How do I remediate CVE-2019-10405?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-10405, 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-2019-10405

Explore →

Is Your Infrastructure Affected by CVE-2019-10405?

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

Start Free Scan →Browse All CVEs