# Jenkins allows for Privilege Escalation by Remote Authenticated Users

Advisory record · `GHSA-3269-jqp5-v8c9`

- **Identifiers:** `GHSA-3269-jqp5-v8c9` · `CVE-2015-1814`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-266](https://cwe.mitre.org/data/definitions/266.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md)
- **Published:** 17 May 2022
- **Updated:** 13 Mar 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 03:53 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.597, <1.606 || <1.596.2`; fixed in `1.606`, `1.596.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.597 before 1.606 and versions before 1.596.2 are affected. A remote attacker can gain privileges through a forced API token change involving anonymous users, though the source gives few details on the exact conditions. Upgrade to version 1.606 or 1.596.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

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.023, the 83rd 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-3269-jqp5-v8c9)

## Sources

- [GitHub Advisory Database: GHSA-3269-jqp5-v8c9](https://github.com/advisories/GHSA-3269-jqp5-v8c9)
- [OSV: GHSA-3269-jqp5-v8c9](https://osv.dev/vulnerability/GHSA-3269-jqp5-v8c9)
- <https://nvd.nist.gov/vuln/detail/CVE-2015-1814>
- <https://github.com/jenkinsci/jenkins/commit/57e78880cc035874bda916ef4d8d7fd7642af9db>
- <https://access.redhat.com/errata/RHSA-2016:0070>
- <https://bugzilla.redhat.com/show_bug.cgi?id=1205616>
- <https://github.com/jenkinsci/jenkins>
- <https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-03-23>
- <http://rhn.redhat.com/errata/RHSA-2015-1844.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-3269-jqp5-v8c9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3269-jqp5-v8c9/>. Everything for agents: <https://agentprime.io/llms.txt>.
