JenkinsApplication
CVE-2025-59476
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJenkins versions 2.527 and earlier, LTS 2.516.2 and earlier fail to restrict or sanitize characters in user-controlled log message content. Attackers who can influence log message contents can inject newline characters to forge additional log entries, potentially misleading administrators reviewing logs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
JenkinsApplication
< 2.516.3< 2.528CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- 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
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Jenkins versionAccess Manage Jenkins > About Jenkins page, or run 'java -jar jenkins.war --version' from the Jenkins installation directory, or check the version displayed on the login pageAffected if Version shown is 2.527 or earlier, or LTS 2.516.2 or earlier
-
Confirm version matches affected rangeCompare your installed version number to the known vulnerable versions: any version below 2.516.3 (LTS) or below 2.528 (weekly)Affected if Your installed version is 2.516.2 or earlier, or 2.527 or earlier, but not 2.516.3+ or 2.528+
You are affected if your Jenkins version is 2.516.2 or earlier (LTS) or 2.527 or earlier (weekly), as these versions fail to sanitize newline characters in user-controlled log message content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.516.32.528
Upgrade Jenkins to a version that properly sanitizes or transforms special characters (including line breaks) in user-specified log content before output.
Jenkins LTS 2.516.3 or Jenkins 2.528 (weekly)
- Upgrade Jenkins to the fixed version. For LTS release line, upgrade to Jenkins 2.516.3 or later. For weekly release line, upgrade to Jenkins 2.528 or later.
- After upgrading, verify the fix by checking that log messages properly escape or restrict newline characters from user-supplied content.
- Review Jenkins logs after upgrade to confirm normal operation and proper log formatting.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59476 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59476 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data