CVE-2025-59476
jenkins: Log message injection vulnerability
Overview
Description
Jenkins 2.527 and earlier, LTS 2.516.2 and earlier does not restrict or transform the characters that can be inserted from user-specified content in log messages, allowing attackers able to control log message contents to insert line break characters, followed by forged log messages that may mislead administrators reviewing log output.
Source: OX vulnerability database
Severity
5.3 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness: CWE-117
Affected packages · 2
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Bitnami | jenkins | <2.516.3>=2.517.0, <2.528.0 | 2.516.32.528.0 |
| Maven | org.jenkins-ci.main:jenkins-core | <2.516.3>=2.517, <2.528 | 2.516.32.528 |
Open a package to see all its vulnerabilities.
Operating systems · 5 fixes
alpine 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| edge | jenkins | 2.528.3-r0 |
chainguard 1 release · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| jenkins-2-516 | 2.516.3-r0 | |
| jenkins-2 | 2.528-r0 |
minimos 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| jenkins | 2.528-r0 |
wolfi 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| jenkins-2 | 2.528-r0 |
References
- www.openwall.com http://www.openwall.com/lists/oss-security/2025/09/17/1
- access.redhat.com https://access.redhat.com/security/cve/CVE-2025-59476
- github.com https://github.com/jenkinsci/jenkins
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2025-59476
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2025-59476
- www.jenkins.io https://www.jenkins.io/security/advisory/2025-09-17/#SECURITY-3424
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.