# Jenkins has CRLF Injection Vulnerability in the CLI

Advisory record · `GHSA-8p3c-m625-wh83`

- **Identifiers:** `GHSA-8p3c-m625-wh83` · `CVE-2016-0789`
- **State:** Confirmed
- **Severity:** CVSS 6.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-113](https://cwe.mitre.org/data/definitions/113.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 14 May 2022
- **Updated:** 13 Mar 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 03:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jenkins-ci.main:jenkins-core` (Maven): affected `>=1.643, <1.650 || <1.642.2`; fixed in `1.650`, `1.642.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Jenkins core (org.jenkins-ci.main:jenkins-core) versions from 1.643 before 1.650, and versions before 1.642.2, are affected by a CRLF injection flaw in the CLI command documentation. A remote attacker can inject arbitrary HTTP headers and carry out HTTP response splitting through unspecified vectors. The source gives few details. Upgrade to version 1.650 or 1.642.2.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.1 Medium, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.018, the 78th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8p3c-m625-wh83)

## Sources

- [GitHub Advisory Database: GHSA-8p3c-m625-wh83](https://github.com/advisories/GHSA-8p3c-m625-wh83)
- [OSV: GHSA-8p3c-m625-wh83](https://osv.dev/vulnerability/GHSA-8p3c-m625-wh83)
- <https://nvd.nist.gov/vuln/detail/CVE-2016-0789>
- <https://github.com/jenkinsci/jenkins/commit/f5c51fbad2b62b81dc1e0402aeee058a4a478046>
- <https://access.redhat.com/errata/RHSA-2016:0711>
- <https://github.com/jenkinsci/jenkins>
- <https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24>
- <http://rhn.redhat.com/errata/RHSA-2016-1773.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-8p3c-m625-wh83>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8p3c-m625-wh83/>. Everything for agents: <https://agentprime.io/llms.txt>.
