Privilege escalation via inconsistent Unicode name canonicalization
Published Aug 5, 2026 · Updated Aug 5, 2026
Improper case handling in Jenkins 2.575 and earlier and LTS 2.568.1 and earlier allows attackers to impersonate users or inherit permissions. The canonical ID lowercases a name, but authorization comparisons use String#equalsIgnoreCase, which equates additional Unicode characters. Exploitation requires a security realm that accepts those characters and permits creation of names matching existing users or groups; the built-in user database blocks non-ASCII sign-ups.
Summary
What happened
Improper case handling in Jenkins 2.575 and earlier and LTS 2.568.1 and earlier allows attackers to impersonate users or inherit permissions. The canonical ID lowercases a name, but authorization comparisons use String#equalsIgnoreCase, which equates additional Unicode characters. Exploitation requires a security realm that accepts those characters and permits creation of names matching existing users or groups; the built-in user database blocks non-ASCII sign-ups.
The record
- CVE
- CVE-2026-70429
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-178, T1136
- Attack vector
- network
- Privileges
- unauthenticated
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?
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.
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