Loading...
Skip to main content

CVE-2026-55772 — Vulnerability in com.cedarpolicy:cedar-java — CVE...

HIGH

CedarJava has type confusion vulnerability

Published June 19, 2026Updated July 28, 2026Source: osv

Summary

### Summary 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. ### Impact **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. ### Impacted versions: < 4.9 ### Patches 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. ### Workarounds 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. ### References If you have any questions or comments about this advisory, we ask that you contact us directly via email to [cedar-policy-security@lists.cncf.io](mailto:cedar-policy-security@lists.cncf.io). Please do not create a public GitHub issue.

Advisory Timeline

  • First published June 19, 2026 (115 days ago).
  • Last revised July 28, 2026 — 38 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update com.cedarpolicy:cedar-java to 3.4.1 or later
<!-- Update pom.xml dependency version to 3.4.1 for com.cedarpolicy:cedar-java -->
Maven
Update com.cedarpolicy:cedar-java to 4.9.0 or later
<!-- Update pom.xml dependency version to 4.9.0 for com.cedarpolicy:cedar-java -->
Maven
Update com.cedarpolicy:cedar-java to 2.3.6 or later
<!-- Update pom.xml dependency version to 2.3.6 for com.cedarpolicy:cedar-java -->

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (3)

Affects 1 ecosystem: maven (1).

PackageEcosystemAffectedFixed In
com.cedarpolicy:cedar-java
maven
3.1.2, 3.2.0, 3.2.5, 3.3.0 (+1 more)3.4.1
com.cedarpolicy:cedar-java
maven
4.0.0, 4.1.0, 4.2.1, 4.2.2 (+5 more)4.9.0
com.cedarpolicy:cedar-java
maven
2.3, 2.3.3, 2.3.4, 2.3.52.3.6

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.8 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Frequently Asked Questions

What is CVE-2026-55772?
CedarJava has type confusion vulnerability This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.8/10).
How do I check if my project is affected by CVE-2026-55772?
CVE-2026-55772 affects com.cedarpolicy:cedar-java. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-55772 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.8

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-93g4-m6xv-cmvr

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies