{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-55772","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","state":"PUBLISHED","assignerShortName":"GitHub_M","dateReserved":"2026-06-17T14:34:51.881Z","datePublished":"2026-07-13T18:44:47.577Z","dateUpdated":"2026-07-21T19:02:48.982Z"},"containers":{"cna":{"title":"CedarJava has a type confusion vulnerability","problemTypes":[{"descriptions":[{"cweId":"CWE-843","lang":"en","description":"CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')","type":"CWE"}]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":8.8,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"name":"https://github.com/cedar-policy/cedar-java/security/advisories/GHSA-93g4-m6xv-cmvr","tags":["x_refsource_CONFIRM"],"url":"https://github.com/cedar-policy/cedar-java/security/advisories/GHSA-93g4-m6xv-cmvr"}],"affected":[{"vendor":"cedar-policy","product":"cedar-java","versions":[{"version":"< 2.3.6","status":"affected"},{"version":">= 3.1.2, < 3.4.1","status":"affected"},{"version":">= 4.0.0, < 4.9.0","status":"affected"}]}],"providerMetadata":{"orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M","dateUpdated":"2026-07-13T18:44:47.577Z"},"descriptions":[{"lang":"en","value":"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."}],"source":{"advisory":"GHSA-93g4-m6xv-cmvr","discovery":"UNKNOWN"}},"adp":[{"metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-07-21T19:02:38.661180Z","id":"CVE-2026-55772","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"title":"CISA ADP Vulnrichment","providerMetadata":{"orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP","dateUpdated":"2026-07-21T19:02:48.982Z"}}]}}