CVE-2026-55772

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 21, 2026

Advisory Details (1)

Auto-updated Jul 13, 2026
Patch available. Sources: github.
github Patch Available

CedarJava has type confusion vulnerability · Advisory · cedar-policy/cedar-java · GitHub

https://github.com/cedar-policy/cedar-java/security/advisories/GHSA-93g4-m6xv-cmvr

Vendor Advisories for CVE-2026-55772(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
com.cedarpolicy:cedar-java4.0.0 ... 4.8.0 (9 versions)4.9.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-24 22:18 UTCEG score recompute
  2. 2026-08-23 13:28 UTCEG score recompute
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-22 23:56 UTCEG score recompute
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 10:06 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 08:06 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 07:19 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 20:33 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 04:37 UTCEG score recompute
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 02:38 UTCEG score recompute
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 00:39 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 22:40 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 20:42 UTCEG score recompute
  24. 2026-08-11 07:43 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 42 more
  1. 2026-08-09 16:45 UTCEG score recompute
  2. 2026-08-09 13:46 UTCEPSS rescore
  3. 2026-08-09 03:46 UTCEG score recompute
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-08 01:47 UTCEG score recompute
  6. 2026-08-06 23:50 UTCEG score recompute
  7. 2026-08-06 13:47 UTCEPSS rescore
  8. 2026-08-05 21:50 UTCEG score recompute
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-04 15:21 UTCEG score recompute
  11. 2026-08-04 15:10 UTCEPSS rescore
  12. 2026-08-04 10:39 UTCEPSS rescore
  13. 2026-08-03 22:02 UTCEG score recompute
  14. 2026-08-03 10:36 UTCEPSS rescore
  15. 2026-08-01 05:04 UTCEG score recompute
  16. 2026-08-01 04:16 UTCEPSS rescore
  17. 2026-07-30 22:23 UTCEG score recompute
  18. 2026-07-30 16:28 UTCEPSS rescore
  19. 2026-07-30 09:02 UTCEG score recompute
  20. 2026-07-30 01:30 UTCEPSS rescore
  21. 2026-07-29 04:36 UTCEG score recompute
  22. 2026-07-28 15:37 UTCEPSS rescore
  23. 2026-07-27 22:05 UTCEG score recompute
  24. 2026-07-26 16:57 UTCEG score recompute
  25. 2026-07-26 14:54 UTCEPSS rescore
  26. 2026-07-25 14:18 UTCEPSS rescore
  27. 2026-07-24 14:18 UTCEPSS rescore
  28. 2026-07-23 14:18 UTCEPSS rescore
  29. 2026-07-23 03:20 UTCEG score recompute
  30. 2026-07-22 14:08 UTCEPSS rescore
  31. 2026-07-21 15:25 UTCEPSS rescore
  32. 2026-07-20 17:08 UTCEPSS rescore
  33. 2026-07-19 14:31 UTCEPSS rescore
  34. 2026-07-19 14:31 UTCEPSS rescore
  35. 2026-07-19 02:29 UTCEPSS rescore
  36. 2026-07-18 10:04 UTCEPSS rescore
  37. 2026-07-16 17:03 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 16:57 UTCEPSS rescore
  40. 2026-07-15 02:00 UTCEPSS rescore
  41. 2026-07-15 02:00 UTCEPSS rescore
  42. 2026-06-19 14:56 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55772?
CVE-2026-55772 is a high vulnerability published on June 19, 2026. 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…
When was CVE-2026-55772 disclosed?
CVE-2026-55772 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55772 actively exploited?
CVE-2026-55772 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.8% of all scored CVEs.
What is the CVSS score of CVE-2026-55772?
CVE-2026-55772 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-55772?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55772, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55772

Explore →

Is Your Infrastructure Affected by CVE-2026-55772?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs