{"items":[{"id":"NVI-00015181","kind":"vulnerability","title":"CedarJava has type confusion vulnerability ","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-93g4-m6xv-cmvr","CVE-2026-55772"],"plain_summary":"GitHub lists this reviewed advisory for com.cedarpolicy:cedar-java, com.cedarpolicy:cedar-java, com.cedarpolicy:cedar-java. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-46a705ae8d8d5d369ab8c79cf3fa9e31"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-28T01:55:32.000Z","value":"8.8 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-37fb80096830b2fdda06eece80c479a2"},{"kind":"CVSS","as_of":"2026-10-24T22:10:00.210Z","value":"8.8 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-46a705ae8d8d5d369ab8c79cf3fa9e31"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-37fb80096830b2fdda06eece80c479a2","url":"https://github.com/advisories/GHSA-93g4-m6xv-cmvr","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-93g4-m6xv-cmvr","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:59:04.660Z"},{"id":"sr-46a705ae8d8d5d369ab8c79cf3fa9e31","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55772","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55772","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T01:48:33.286Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-37fb80096830b2fdda06eece80c479a2"],"technology":"com.cedarpolicy:cedar-java","known_exclusions":[],"conditions_summary":"### Summary\n\nCedarJava 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.\n\n### Impact\n\n**Record-to-Entity type confusion across the Java-Rust FFI boundary**\n\nCedarJava 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.\n\nThis 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.\n\n### Impacted versions: \n< 4.9\n\n### Patches\nAddressed in CedarJava version 2.3.6, 3.4.1, and 4.9 and above. We recommend ","public_affected_ranges":["< 2.3.6"]},{"certainty":"source_listed","source_ids":["sr-37fb80096830b2fdda06eece80c479a2"],"technology":"com.cedarpolicy:cedar-java","known_exclusions":[],"conditions_summary":"### Summary\n\nCedarJava 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.\n\n### Impact\n\n**Record-to-Entity type confusion across the Java-Rust FFI boundary**\n\nCedarJava 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.\n\nThis 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.\n\n### Impacted versions: \n< 4.9\n\n### Patches\nAddressed in CedarJava version 2.3.6, 3.4.1, and 4.9 and above. We recommend ","public_affected_ranges":[">= 3.1.2, < 3.4.1"]},{"certainty":"source_listed","source_ids":["sr-37fb80096830b2fdda06eece80c479a2"],"technology":"com.cedarpolicy:cedar-java","known_exclusions":[],"conditions_summary":"### Summary\n\nCedarJava 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.\n\n### Impact\n\n**Record-to-Entity type confusion across the Java-Rust FFI boundary**\n\nCedarJava 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.\n\nThis 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.\n\n### Impacted versions: \n< 4.9\n\n### Patches\nAddressed in CedarJava version 2.3.6, 3.4.1, and 4.9 and above. We recommend ","public_affected_ranges":[">= 4.0.0, < 4.9.0"]}],"null_published_at":"2026-11-08T19:53:44.054Z","source_updated_at":"2026-07-28T01:55:32.000Z","source_disclosed_at":"2026-06-19T14:38:43.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-03T09:59:04.660Z"},{"id":"NVI-00015181","kind":"vulnerability","title":"CedarJava has type confusion vulnerability ","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-93g4-m6xv-cmvr","CVE-2026-55772"],"plain_summary":"GitHub lists this reviewed advisory for com.cedarpolicy:cedar-java, com.cedarpolicy:cedar-java, com.cedarpolicy:cedar-java. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-37fb80096830b2fdda06eece80c479a2"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-28T01:55:32.000Z","value":"8.8 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-37fb80096830b2fdda06eece80c479a2"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-37fb80096830b2fdda06eece80c479a2","url":"https://github.com/advisories/GHSA-93g4-m6xv-cmvr","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-93g4-m6xv-cmvr","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:59:04.660Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-37fb80096830b2fdda06eece80c479a2"],"technology":"com.cedarpolicy:cedar-java","known_exclusions":[],"conditions_summary":"### Summary\n\nCedarJava 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.\n\n### Impact\n\n**Record-to-Entity type confusion across the Java-Rust FFI boundary**\n\nCedarJava 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.\n\nThis 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.\n\n### Impacted versions: \n< 4.9\n\n### Patches\nAddressed in CedarJava version 2.3.6, 3.4.1, and 4.9 and above. We recommend ","public_affected_ranges":["< 2.3.6"]},{"certainty":"source_listed","source_ids":["sr-37fb80096830b2fdda06eece80c479a2"],"technology":"com.cedarpolicy:cedar-java","known_exclusions":[],"conditions_summary":"### Summary\n\nCedarJava 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.\n\n### Impact\n\n**Record-to-Entity type confusion across the Java-Rust FFI boundary**\n\nCedarJava 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.\n\nThis 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.\n\n### Impacted versions: \n< 4.9\n\n### Patches\nAddressed in CedarJava version 2.3.6, 3.4.1, and 4.9 and above. We recommend ","public_affected_ranges":[">= 3.1.2, < 3.4.1"]},{"certainty":"source_listed","source_ids":["sr-37fb80096830b2fdda06eece80c479a2"],"technology":"com.cedarpolicy:cedar-java","known_exclusions":[],"conditions_summary":"### Summary\n\nCedarJava 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.\n\n### Impact\n\n**Record-to-Entity type confusion across the Java-Rust FFI boundary**\n\nCedarJava 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.\n\nThis 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.\n\n### Impacted versions: \n< 4.9\n\n### Patches\nAddressed in CedarJava version 2.3.6, 3.4.1, and 4.9 and above. We recommend ","public_affected_ranges":[">= 4.0.0, < 4.9.0"]}],"null_published_at":"2026-11-03T10:03:26.557Z","source_updated_at":"2026-07-28T01:55:32.000Z","source_disclosed_at":"2026-06-19T14:38:43.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-03T09:59:04.660Z"}],"next_cursor":null,"snapshot_revision":"42594"}