Log forgery via unsanitized line breaks
Published Sep 17, 2025 · Updated Sep 17, 2025
Log injection in Jenkins 2.527 and earlier and LTS 2.516.2 and earlier allows remote attackers to forge entries in server logs. The console-output log formatter passes user-controlled carriage returns and line feeds without restriction or transformation, so injected text begins forged log lines. Exploitation requires control of content that Jenkins records and can mislead administrators reviewing jenkins.log or equivalent output without altering underlying events.
Summary
What happened
Log injection in Jenkins 2.527 and earlier and LTS 2.516.2 and earlier allows remote attackers to forge entries in server logs. The console-output log formatter passes user-controlled carriage returns and line feeds without restriction or transformation, so injected text begins forged log lines. Exploitation requires control of content that Jenkins records and can mislead administrators reviewing jenkins.log or equivalent output without altering underlying events.
The record
- CVE
- CVE-2025-59476
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-117
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo