GitHub Advisoryadvisory · Maven
GHSA-qrh5-jg98-cr48 Jenkins has a log message injection vulnerability
MEDIUM
Official page ↗
- Aliases
- CVE-2025-59476
- Ecosystem
- Maven
- Packages
- org.jenkins-ci.main:jenkins-core
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Weaknesses
- CWE-117, CWE-74
- Reviewed
- 2025-09-17
Affected packages
• Maven org.jenkins-ci.main:jenkins-core: < 2.516.3 → fixed in 2.516.3
• Maven org.jenkins-ci.main:jenkins-core: >= 2.517, < 2.528 → fixed in 2.528
Description
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 `>` .
Related
Alias · CVE (1)
- CVE-2025-59476 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… vulnerability