Description
CedarJava is an open source Java implementation of the Cedar policy language, used for fine-grained authorization decisions. In versions prior to 2.3.6, 3.4.1 and 4.9.0, under certain circumstances, improper input handling could allow 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. This vulnerability has been fixed in versions 2.3.6, 3.4.1, and 4.9.
Published: 2026-07-13
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

CedarJava is an open‑source Java implementation of the Cedar policy language used for fine‑grained authorization decisions. In versions prior to 2.3.6, 3.4.1 and 4.9.0, improper input handling can allow Record‑to‑Entity type confusion across the Java‑Rust FFI boundary. CedarJava sends authorization requests to the Rust cedar‑policy evaluator as JSON, and the protocol reserves magic single‑key object shapes (__entity and __extn) for entity references and extension values. When serializing a CedarMap, no validation prevents 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. The issue requires that a policy reference the controlled value in a when/unless clause, allowing an attacker who controls the keys to trigger type confusion that can grant unauthorized access to protected resources. This vulnerability has been fixed in versions 2.3.6, 3.4.1, and 4.9.

Affected Systems

The product affected is cedar‑policy’s CedarJava library. Versions before 2.3.6, 3.4.1, and 4.9.0 are vulnerable. Applications that integrate CedarJava and marshal caller‑supplied data such as HTTP headers, metadata, or resource tags into CedarMaps without validation are at risk. This vulnerability requires that a policy reference the controlled value in a when/unless clause, so any project using user‑generated keys in policy expressions is potentially impacted.

Risk and Exploitability

The CVSS score of 8.8 indicates a high severity. The EPSS score is less than 1%, indicating a very low exploitation probability, and the vulnerability is not listed in CISA’s KEV catalog. Exploitability is clear for systems whose integration code constructs CedarMaps from external input. An attacker capable of controlling the input keys – for example, through HTTP request headers or other user‑controlled data – can trigger type confusion and obtain unauthorized privileges. Given the high impact, immediate remediation is advisable.

Generated by OpenCVE AI on July 31, 2026 at 11:25 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade CedarJava to version 2.3.6, 3.4.1, or 4.9.0 or newer, which contain the fix for the type confusion flaw.
  • Audit code that builds CedarMaps from external input and remove or sanitize any user‑controlled keys, ensuring that the reserved __entity and __extn keys are not used.
  • Modify policies to eliminate references to untrusted values in when/unless clauses or enforce that only internally generated data can be used in policy decisions.

Generated by OpenCVE AI on July 31, 2026 at 11:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-93g4-m6xv-cmvr CedarJava has type confusion vulnerability
History

Mon, 27 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
First Time appeared Cedar-policy
Cedar-policy cedar-java
Vendors & Products Cedar-policy
Cedar-policy cedar-java

Tue, 21 Jul 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 13 Jul 2026 19:00:00 +0000

Type Values Removed Values Added
Description CedarJava is an open source Java implementation of the Cedar policy language, used for fine-grained authorization decisions. In versions prior to 2.3.6, 3.4.1 and 4.9.0, under certain circumstances, improper input handling could allow 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. This vulnerability has been fixed in versions 2.3.6, 3.4.1, and 4.9.
Title CedarJava has a type confusion vulnerability
Weaknesses CWE-843
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Cedar-policy Cedar-java
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-21T19:02:48.982Z

Reserved: 2026-06-17T14:34:51.881Z

Link: CVE-2026-55772

cve-icon Vulnrichment

Updated: 2026-07-21T19:02:45.599Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T11:30:05Z

Weaknesses
  • CWE-843

    Access of Resource Using Incompatible Type ('Type Confusion')