# CVE-2026-117625: Jenkins missing HTTP proxy permission check

Source: https://junglewise.ai/threats/cve-2026-117625-a-missing-permission-check-in-jenkins-2-587-and-earlier-lts-2  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-28. Updated: 2026-10-28  
License: CC BY 4.0 with a link back

CVE-2026-117625 · Severity: info · Published 2026-10-28

Jenkins is an open-source automation server used to build, test, and deploy software. A missing permission check allows users with basic read access to view sensitive HTTP proxy configuration details including server address, port, username, and bypass hosts. While this does not directly enable code execution, the exposed credentials could be used for further attacks on network infrastructure.

Technologies: [Jenkins](https://junglewise.ai/threats/technologies/jenkins). Vendors: [Jenkins](https://junglewise.ai/threats/vendors/jenkins).

## Quick answers

**Is CVE-2026-117625 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-117625 being exploited in the wild.

**How severe is CVE-2026-117625?** Informational severity, published 28 October 2026.

**Which products and versions are affected?** Jenkins 2.587 and earlier, LTS 2.580.1 and earlier.

**Is there a fix for CVE-2026-117625?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-117625 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-117625?** Check whether you run Jenkins at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A missing permission check in Jenkins 2.587 and earlier, LTS 2.580.1 and earlier fails to validate permissions before exposing HTTP proxy configuration details. Attackers with Overall/Read permission can access the server hostname, port, username, and no-proxy host list. The vulnerability requires network access to Jenkins and an authenticated account with minimal privileges; no user interaction is needed.

## Affected products

- Jenkins Jenkins 2.587 and earlier, LTS 2.580.1 and earlier

## Timeline

- 2026-10-28: disclosed

## References

- [https://www.jenkins.io/security/advisory/2026-10-28/](https://www.jenkins.io/security/advisory/2026-10-28/)

## Related threats

- [Jenkins path traversal in file browser workspace disclosure](https://junglewise.ai/threats/cve-2026-117626-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-improperly)
- [Jenkins deserialization filter bypass in XStream resolves-to attribute](https://junglewise.ai/threats/cve-2026-117624-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-does-not)
- [Jenkins stored cross-site scripting in breadcrumb menu tooltips](https://junglewise.ai/threats/cve-2026-117623-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-does-not)
- [Jenkins agent XSS via Stapler HttpResponse exceptions](https://junglewise.ai/threats/cve-2026-117622-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-allows-agents)
- [Jenkins workspace browser XSS in agent URL computation](https://junglewise.ai/threats/cve-2026-117621-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-computes-on)