GHSA-qrh5-jg98-cr48

Jenkins has a log message injection vulnerability

At a glance

Published
Updated
CVE
CVE-2025-59476
Aliases
BIT-jenkins-2025-59476
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 `>` .

Affected packages

PackageVersions
Maven · org.jenkins-ci.main:jenkins-coreintroduced 0, fixed 2.516.3
Maven · org.jenkins-ci.main:jenkins-coreintroduced 2.517, fixed 2.528

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database