CVE-2026-55772High· 8.8▾ TwilightCedarJava has type confusion vulnerability
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 14.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via GHSA
0.5%
CedarJava is an open source Java implementation of the Cedar policy language, used for fine-grained authorization decisions. Under certain circumstances, improper input handling could allow type confusion across the Java-Rust FFI boundary.
Record-to-Entity type confusion across the Java-Rust FFI boundary
CedarJava sends authorization requests to the Rust cedar-policy evaluator as JSON. The JSON protocol reserves magic single-key object shapes (__entity and __extn) for entity references and extension values. When serializing a CedarMap, there is no validation preventing these reserved keys from being used. If an integrating service builds a CedarMap from caller-supplied key/value data (such as request headers, user-defined metadata, or resource tags), an actor who controls those keys could cause the Rust evaluator to interpret a record as an entity reference.
This issue requires the integrating service to build a CedarMap where the an actor controls the keys, and a policy must reference that value in a when/unless clause.
< 4.9
Addressed in CedarJava version 2.3.6, 3.4.1, and 4.9 and above. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Enable schema-based request validation to catch type mismatches. Validate that user-controlled data does not contain reserved keys (__entity or __extn) before building CedarMap objects.
If you have any questions or comments about this advisory, we ask that you contact us directly via email to [email protected]. Please do not create a public GitHub issue.
com.cedarpolicy:cedar-java < 2.3.6com.cedarpolicy:cedar-java >= 3.1.2, < 3.4.1com.cedarpolicy:cedar-java >= 4.0.0, < 4.9.0Upgrade to a patched release:
com.cedarpolicy:cedar-java 2.3.6com.cedarpolicy:cedar-java 3.4.1com.cedarpolicy:cedar-java 4.9.0Connected by shared product, vendor, weakness, or advisory.
CVE-2026-55771High· 8.8Cedar-Java has policy injection, type confusion, and incorrect equality comparison vulnerabilities
CVE-2026-55773High· 8.8CedarJava has policy injection vulnerability
CVE-2019-0752High· 7.5A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'
CVE-2026-5865High· 8.8Type Confusion in V8 in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page
CVE-2025-10585Critical· 9.8Type confusion in V8 in Google Chrome prior to 140.0.7339.185 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page
CVE-2026-11389Medium· 6.8Out-of-bounds Read, Function Call With Incorrect Number of Arguments, Access of Resource Using Incompatible Type ('Type Confusion') vulnerability in RTI Connext Professional (Core Libraries) allows Overread Buffers