CVE-2024-23897

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-08-19), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Exploited in the wild
9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 1,606 internet-facing services (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
  • Actively exploited in the wild (CISA-KEV)
  • Linked to ransomware campaigns
CISA-KEV: ExploitedEPSS PROB: 100%CVSS: 9.8Exploit: cisa kev · ssvc active · kev ransomware · Metasploit · epss top5pct · epss high · public exploitExposed services: 1,606

A fix is available — apply it.

Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character followed by a file path in an argument with the file's contents, allowing unauthenticated attackers to read arbitrary files on the Jenkins controller file system.

Internet exposure · derived from Shodan data

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

across 67 countries (United States, China, Germany, Korea, Republic of, Japan)top: jenkins🔒 ransomware-linked
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 v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/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
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low mission impact; Act at medium or high.
Action: A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
100%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCAttend at low mission impact; Act at medium or high.

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

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

January 24, 2024

Last Modified

October 24, 2025

Advisory Details (5)

Auto-updated Oct 9, 2026
Patch available.
generic

SourceForge Vulnerability | Arbitrary File Read to RCE | Sonar

https://www.sonarsource.com/blog/excessive-expansion-uncovering-critical-security-vulnerabilities-in-jenkins/
generic

Jenkins Security Advisory 2024-01-24

https://www.jenkins.io/security/advisory/2024-01-24/#SECURITY-3314
generic

oss-security - Multiple vulnerabilities in Jenkins and Jenkins plugins

http://www.openwall.com/lists/oss-security/2024/01/24/6
generic

Packet Storm

http://packetstormsecurity.com/files/176840/Jenkins-2.441-LTS-2.426.3-Arbitrary-File-Read.html
generic

Packet Storm

http://packetstormsecurity.com/files/176839/Jenkins-2.441-LTS-2.426.3-CVE-2024-23897-Scanner.html

Vendor Advisories for CVE-2024-23897(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjenkins-0:2.426.3.1706516254-3.el82024-02-12redhat
redhatjenkins-0:2.426.3.1706515686-3.el82024-02-12redhat
redhatjenkins-0:2.426.3.1706516929-3.el82024-02-12redhat

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 rangeFix by version rangeDependents
org.jenkins-ci.main:jenkins-core2.441
  • 1.606 up to 2.426.3: fixed in 2.426.3
  • 2.427 up to 2.440.1: fixed in 2.440.1
  • 2.441 up to 2.442: fixed in 2.442
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 40× in last 7d / 187× 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.

Showing the most recent 100 of 821 total refreshes for this CVE.

  1. 2026-10-10 04:07 UTCVendor advisory
  2. 2026-10-09 23:58 UTCVendor advisory
  3. 2026-10-09 19:50 UTCVendor advisory
  4. 2026-10-09 15:42 UTCVendor advisory
  5. 2026-10-09 11:34 UTCVendor advisory
  6. 2026-10-09 07:25 UTCVendor advisory
  7. 2026-10-09 03:17 UTCVendor advisory
  8. 2026-10-08 23:09 UTCVendor advisory
  9. 2026-10-08 19:02 UTCVendor advisory
  10. 2026-10-08 14:54 UTCVendor advisory
  11. 2026-10-08 10:44 UTCVendor advisory
  12. 2026-10-08 06:35 UTCVendor advisory
  13. 2026-10-08 02:27 UTCVendor advisory
  14. 2026-10-07 22:19 UTCVendor advisory
  15. 2026-10-07 18:11 UTCVendor advisory
  16. 2026-10-07 14:02 UTCVendor advisory
  17. 2026-10-07 09:52 UTCVendor advisory
  18. 2026-10-07 05:44 UTCVendor advisory
  19. 2026-10-07 01:36 UTCVendor advisory
  20. 2026-10-06 21:28 UTCVendor advisory
  21. 2026-10-06 17:20 UTCVendor advisory
  22. 2026-10-06 13:12 UTCVendor advisory
  23. 2026-10-06 09:04 UTCVendor advisory
  24. 2026-10-06 04:56 UTCVendor advisory
  25. 2026-10-06 00:49 UTCVendor advisory
Show 75 more
  1. 2026-10-05 20:40 UTCVendor advisory
  2. 2026-10-05 16:32 UTCVendor advisory
  3. 2026-10-05 12:24 UTCVendor advisory
  4. 2026-10-05 08:17 UTCVendor advisory
  5. 2026-10-05 04:09 UTCVendor advisory
  6. 2026-10-04 23:58 UTCVendor advisory
  7. 2026-10-04 19:51 UTCVendor advisory
  8. 2026-10-04 15:43 UTCVendor advisory
  9. 2026-10-04 11:35 UTCVendor advisory
  10. 2026-10-04 07:28 UTCVendor advisory
  11. 2026-10-04 03:20 UTCVendor advisory
  12. 2026-10-03 23:12 UTCVendor advisory
  13. 2026-10-03 19:04 UTCVendor advisory
  14. 2026-10-03 14:53 UTCVendor advisory
  15. 2026-10-03 10:46 UTCVendor advisory
  16. 2026-10-03 06:38 UTCVendor advisory
  17. 2026-10-03 02:30 UTCVendor advisory
  18. 2026-10-02 22:22 UTCVendor advisory
  19. 2026-10-02 18:14 UTCVendor advisory
  20. 2026-10-02 14:05 UTCVendor advisory
  21. 2026-10-02 09:57 UTCVendor advisory
  22. 2026-10-02 05:50 UTCVendor advisory
  23. 2026-10-02 01:42 UTCVendor advisory
  24. 2026-10-01 21:33 UTCVendor advisory
  25. 2026-10-01 17:25 UTCVendor advisory
  26. 2026-10-01 13:17 UTCVendor advisory
  27. 2026-10-01 09:09 UTCVendor advisory
  28. 2026-10-01 05:01 UTCVendor advisory
  29. 2026-10-01 00:53 UTCVendor advisory
  30. 2026-09-30 20:45 UTCVendor advisory
  31. 2026-09-30 16:37 UTCVendor advisory
  32. 2026-09-30 12:28 UTCVendor advisory
  33. 2026-09-30 08:19 UTCVendor advisory
  34. 2026-09-30 04:10 UTCVendor advisory
  35. 2026-09-30 00:02 UTCVendor advisory
  36. 2026-09-29 19:52 UTCVendor advisory
  37. 2026-09-29 15:41 UTCVendor advisory
  38. 2026-09-29 11:33 UTCVendor advisory
  39. 2026-09-29 07:24 UTCVendor advisory
  40. 2026-09-29 03:16 UTCVendor advisory
  41. 2026-09-28 23:09 UTCEG score recompute
  42. 2026-09-28 23:09 UTCVendor advisory
  43. 2026-09-28 18:59 UTCVendor advisory
  44. 2026-09-28 14:51 UTCVendor advisory
  45. 2026-09-28 10:43 UTCVendor advisory
  46. 2026-09-28 06:35 UTCVendor advisory
  47. 2026-09-28 02:27 UTCVendor advisory
  48. 2026-09-27 22:19 UTCVendor advisory
  49. 2026-09-27 21:51 UTCCISA KEV update
  50. 2026-09-27 18:11 UTCVendor advisory
  51. 2026-09-27 14:03 UTCVendor advisory
  52. 2026-09-27 09:54 UTCVendor advisory
  53. 2026-09-27 05:47 UTCVendor advisory
  54. 2026-09-27 01:38 UTCVendor advisory
  55. 2026-09-26 21:29 UTCVendor advisory
  56. 2026-09-26 17:22 UTCVendor advisory
  57. 2026-09-26 13:13 UTCVendor advisory
  58. 2026-09-26 09:03 UTCVendor advisory
  59. 2026-09-26 04:54 UTCVendor advisory
  60. 2026-09-26 00:46 UTCVendor advisory
  61. 2026-09-25 20:38 UTCVendor advisory
  62. 2026-09-25 19:35 UTCCISA KEV update
  63. 2026-09-25 16:27 UTCVendor advisory
  64. 2026-09-25 14:55 UTCCISA KEV update
  65. 2026-09-25 12:19 UTCVendor advisory
  66. 2026-09-25 08:11 UTCVendor advisory
  67. 2026-09-25 04:04 UTCVendor advisory
  68. 2026-09-24 23:56 UTCVendor advisory
  69. 2026-09-24 19:48 UTCVendor advisory
  70. 2026-09-24 19:31 UTCCISA KEV update
  71. 2026-09-24 15:40 UTCVendor advisory
  72. 2026-09-24 11:32 UTCVendor advisory
  73. 2026-09-24 07:24 UTCVendor advisory
  74. 2026-09-24 03:16 UTCVendor advisory
  75. 2026-09-23 23:08 UTCVendor advisory

Publicly available exploits

(10 references)

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

  • Metasploitauxiliary/gather/jenkins_cli_ampersand_arbitrary_file_read✓ verified
    First seen Jan 24, 2024

    Jenkins cli Ampersand Replacement Arbitrary File Read

    Open source ↗
  • GitHub PoCverylazytech/CVE-2024-23897
    First seen Sep 30, 2024

    POC - Jenkins File Read Vulnerability - CVE-2024-23897

    Open source ↗
  • GitHub PoCMaalfer/CVE-2024-23897
    First seen May 16, 2024

    Poc para explotar la vulnerabilidad CVE-2024-23897 en versiones 2.441 y anteriores de Jenkins, mediante la cual podremos leer archivos internos del sistema sin estar autenticados

    Open source ↗
  • Exploit-DBEDB-51993
    First seen Apr 15, 2024

    Jenkins 2.441 - Local File Inclusion

    Open source ↗
  • GitHub PoCgodylockz/CVE-2024-23897
    First seen Feb 16, 2024

    POC for CVE-2024-23897 Jenkins File-Read

    Open source ↗
  • GitHub PoCkaanatmacaa/CVE-2024-23897
    First seen Feb 4, 2024

    Nuclei template for CVE-2024-23897 (Jenkins LFI Vulnerability)

    Open source ↗
  • GitHub PoCVozec/CVE-2024-23897
    First seen Jan 28, 2024

    This repository presents a proof-of-concept of CVE-2024-23897

    Open source ↗
  • GitHub PoCP4x1s/CVE-2024-23897
    First seen Jan 27, 2024

    CVE-2024-23897 jenkins-cli

    Open source ↗
  • GitHub PoCwjlin0/CVE-2024-23897
    First seen Jan 27, 2024

    CVE-2024-23897 - Jenkins 任意文件读取 利用工具

    Open source ↗
  • GitHub PoCbinganao/CVE-2024-23897
    First seen Jan 26, 2024
    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(6)

What is CVE-2024-23897?
CVE-2024-23897 is a critical vulnerability published on January 24, 2024. Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character followed by a file path in an argument with the file's contents, allowing unauthenticated attackers to read arbitrary files on the Jenkins controller file system.
When was CVE-2024-23897 disclosed?
CVE-2024-23897 was first published on January 24, 2024, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-23897 actively exploited?
Yes. CISA added CVE-2024-23897 to the Known Exploited Vulnerabilities catalog on August 19, 2024, affecting Jenkins Jenkins Command Line Interface (CLI). KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2024-23897?
CVE-2024-23897 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2024-23897?
CVE-2024-23897 affects Jenkins Jenkins Command Line Interface (CLI). The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2024-23897?
A fix for CVE-2024-23897 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-23897 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-23897

Explore →

Is Your Infrastructure Affected by CVE-2024-23897?

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

Book a Demo →Browse All CVEs