Incorrect identity decisions via inverted equals branches
Published Jul 13, 2026 · Updated Jul 13, 2026
Incorrect comparison in Cedar Policy CedarJava before 4.9.0 allows attackers to influence integrator decisions through entity identifier checks. EntityIdentifier.equals() reverses its null and self-reference branches, returning true for null and false when an object is compared with itself. The defect does not affect authorization decisions computed by the Rust engine; impact requires integrator code to rely on these Java equality results.
Summary
What happened
Incorrect comparison in Cedar Policy CedarJava before 4.9.0 allows attackers to influence integrator decisions through entity identifier checks. EntityIdentifier.equals() reverses its null and self-reference branches, returning true for null and false when an object is compared with itself. The defect does not affect authorization decisions computed by the Rust engine; impact requires integrator code to rely on these Java equality results.
The record
- CVE
- CVE-2026-55771
- Published
- Jul 13, 2026
- Updated
- Jul 13, 2026
- Vendor
- Cedar Policy
- Product
- CedarJava
- Classifications
- CWE-697, CWE-843, CWE-94
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 13, 2026CVE publishedPublication date reported by the CVE source.
- Jul 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.9.0
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