Answer in brief
CVE-2025-59476 records a Medium severity (CVSS 5.3) vulnerability in Jenkins has a log message injection vulnerability. The current sources do not mark it as known exploited. The current feed maps org.jenkins-ci.main:jenkins-core (maven), org.jenkins-ci.main:jenkins-core (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.jenkins-ci.main:jenkins-core (maven), org.jenkins-ci.main:jenkins-core (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.jenkins-ci.main:jenkins-coremaven | >=0 <2.516.3 | 2.516.3 |
| org.jenkins-ci.main:jenkins-coremaven | >=2.517 <2.528 | 2.528 |
Published upstream
Sep 17, 2025
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Aug 7, 2026
In Jenkins 2.527 and earlier, LTS 2.516.2 and earlier, the log formatter that prepares log messages for console output (including `jenkins.log` and equivalent) does not restrict or transform the characters that can be inserted from user-specified content in log messages. This allows attackers able to control log message contents to insert line break characters, followed by forged log messages that may mislead administrators reviewing log output. Jenkins 2.528, LTS 2.516.3 adds an indicator at the beginning of a line that was inserted as part of log message content: `[CR]`, `[LF]`, or `[CRLF]` (representing the kind of line break), followed by `>` .
Quoted source text, attributed separately from HOL analysis.