CVE-2026-117616 Jenkins 2.587 and earlier, LTS 2.580.1 and earlier provides an HTTP endpoint that loads agents by name without validating the name, allowing
Not scored
Published
Updated
Check this codebase for CVE-2026-117616 and fix it if it is affected.
What it is: CVE-2026-117616 is a vulnerability in Jenkins, published on 28 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-117616 in the wild and no public exploit code.
Affected product: Jenkins. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-117616/ (Markdown: https://insights.sbomify.com/CVE-2026-117616/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-117616?
CVE-2026-117616 is a vulnerability in Jenkins, published on 28 Oct 2026.
Official description
Jenkins 2.587 and earlier, LTS 2.580.1 and earlier provides an HTTP endpoint that loads agents by name without validating the name, allowing attackers with Overall/Read permission to load any config.xml file on the controller file system as an agent configuration, and to overwrite an arbitrary config.xml file when that agent is saved, potentially resulting in arbitrary code execution.
Which versions are affected by CVE-2026-117616?
How do I fix CVE-2026-117616?
No fix has been published for CVE-2026-117616 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-117616 being exploited?
There is no known exploitation of CVE-2026-117616 in the wild and no public exploit code.
Sources
Also known as GHSA-gmh6-98p7-vvcx.