CVE-2026-55772: CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') in cedar-policy cedar-java
CVE-2026-55772 is a high-severity type confusion vulnerability in cedar-java, an open source Java implementation of the Cedar policy language. It affects versions prior to 2.3.6, versions from 3.0.0 up to but not including 3.4.1, and versions from 4.0.0 up to but not including 4.9.0. The issue arises when integrating services build CedarMap objects from untrusted key/value data containing reserved keys (__entity and __extn), causing the Rust evaluator to misinterpret records as entity references. This vulnerability requires specific conditions involving actor-controlled keys and policy references. It has been fixed in versions 2.3.6, 3.4.1, and 4.9.0.
AI Analysis
Technical Summary
CVE-2026-55772 is a type confusion vulnerability (CWE-843) in cedar-java that occurs due to improper input validation when serializing CedarMap objects across the Java-Rust FFI boundary. The JSON protocol used reserves certain single-key object shapes (__entity and __extn) for entity references and extension values, but cedar-java versions prior to 2.3.6, 3.4.1, and 4.9.0 do not prevent these reserved keys from being used in CedarMap keys. If an integrating service constructs a CedarMap from caller-controlled data containing these reserved keys, the Rust cedar-policy evaluator may interpret a record as an entity reference, potentially leading to unauthorized access or policy bypass. Exploitation requires that the integrating service uses attacker-controlled keys and that a policy references those values in when/unless clauses. The vulnerability is fixed in versions 2.3.6, 3.4.1, and 4.9.0.
Potential Impact
Successful exploitation can lead to unauthorized access or manipulation of authorization decisions due to type confusion between records and entity references in the policy evaluation process. The vulnerability impacts confidentiality, integrity, and availability as indicated by the CVSS vector (C:H/I:H/A:H).
Mitigation Recommendations
This vulnerability has been fixed in cedar-java versions 2.3.6, 3.4.1, and 4.9.0. Users should upgrade to one of these versions or later to remediate the issue. No official patch or temporary fix is indicated beyond upgrading. Until upgraded, integrating services should avoid building CedarMap objects from untrusted or actor-controlled key/value data containing reserved keys (__entity and __extn).
CVE-2026-55772: CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') in cedar-policy cedar-java
Description
CVE-2026-55772 is a high-severity type confusion vulnerability in cedar-java, an open source Java implementation of the Cedar policy language. It affects versions prior to 2.3.6, versions from 3.0.0 up to but not including 3.4.1, and versions from 4.0.0 up to but not including 4.9.0. The issue arises when integrating services build CedarMap objects from untrusted key/value data containing reserved keys (__entity and __extn), causing the Rust evaluator to misinterpret records as entity references. This vulnerability requires specific conditions involving actor-controlled keys and policy references. It has been fixed in versions 2.3.6, 3.4.1, and 4.9.0.
CVSS v3.1
Score 8.8high
Affected software
pkg:maven/io.cedarpolicy/cedar-javaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-55772 is a type confusion vulnerability (CWE-843) in cedar-java that occurs due to improper input validation when serializing CedarMap objects across the Java-Rust FFI boundary. The JSON protocol used reserves certain single-key object shapes (__entity and __extn) for entity references and extension values, but cedar-java versions prior to 2.3.6, 3.4.1, and 4.9.0 do not prevent these reserved keys from being used in CedarMap keys. If an integrating service constructs a CedarMap from caller-controlled data containing these reserved keys, the Rust cedar-policy evaluator may interpret a record as an entity reference, potentially leading to unauthorized access or policy bypass. Exploitation requires that the integrating service uses attacker-controlled keys and that a policy references those values in when/unless clauses. The vulnerability is fixed in versions 2.3.6, 3.4.1, and 4.9.0.
Potential Impact
Successful exploitation can lead to unauthorized access or manipulation of authorization decisions due to type confusion between records and entity references in the policy evaluation process. The vulnerability impacts confidentiality, integrity, and availability as indicated by the CVSS vector (C:H/I:H/A:H).
Mitigation Recommendations
This vulnerability has been fixed in cedar-java versions 2.3.6, 3.4.1, and 4.9.0. Users should upgrade to one of these versions or later to remediate the issue. No official patch or temporary fix is indicated beyond upgrading. Until upgraded, integrating services should avoid building CedarMap objects from untrusted or actor-controlled key/value data containing reserved keys (__entity and __extn).
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-17T14:34:51.881Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a55366a68715ace43b0b29d
Added to database: 07/13/2026, 19:03:06 UTC
Last enriched: 07/30/2026, 22:38:20 UTC
Last updated: 08/26/2026, 22:52:11 UTC
Views: 87
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.