Privilege boundary bypass via unrestricted type instantiation
Published Aug 5, 2026 · Updated Aug 5, 2026
Access control failure in Jenkins 2.575 and earlier and LTS 2.568.1 and earlier allows remote authenticated users to instantiate admin-only types. The project naming strategy configuration accepts arbitrary configuration-related object types instead of restricting instantiation to types belonging to that feature. Overall/Manage permission is required; the bounded result is access to configuration objects otherwise reserved for administrators.
Summary
What happened
Access control failure in Jenkins 2.575 and earlier and LTS 2.568.1 and earlier allows remote authenticated users to instantiate admin-only types. The project naming strategy configuration accepts arbitrary configuration-related object types instead of restricting instantiation to types belonging to that feature. Overall/Manage permission is required; the bounded result is access to configuration objects otherwise reserved for administrators.
The record
- CVE
- CVE-2026-70430
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-284, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo