Skip to main content
VulnerabilityPublished Updated

CVE-2025-59476: Org.jenkins ci.main:jenkins core: Jenkins has a log message injection vulnerability

Affects org.jenkins-ci.main:jenkins-coreSource GCVE Database

0
Compare
Authoritative record:CVE-2025-59476· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.516.3 when convenient.

Data as of 4 Nov 2026, 18:17 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.15.3
Patch
Available – fixed in 2.516.3, 2.528
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade org.jenkins-ci.main:jenkins-core to 2.516.3; org.jenkins-ci.main:jenkins-core to 2.528.

Affected software

ProductAffectedFixed in
Mavenorg.jenkins-ci.main:jenkins-coreAffected
  • <2.516.3
Fixed in
  • 2.516.3
Mavenorg.jenkins-ci.main:jenkins-coreAffected
  • >=2.517 <2.528
Fixed in
  • 2.528

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and has been released in Jenkins versions 2.516.3 and 2.528. Users should upgrade affected Jenkins instances to these or later versions to mitigate this vulnerability. No additional mitigation steps are indicated by the vendor.

Description

Jenkins versions 2.527 and earlier, including LTS 2.516.2 and earlier, have a log message injection vulnerability where user-controlled input in log messages can include line break characters. This allows attackers to insert forged log entries that may mislead administrators. Fixed in Jenkins 2.516.3 and 2.528 by adding indicators for inserted line breaks in log output.

References

Community reviews

Loading reviews…