CVE-2026-55773 is a high-severity code injection vulnerability in com.cedarpolicy:cedar-java (maven), affecting versions < 2.3.6. It is fixed in 2.3.6, 3.4.1, 4.9.0.
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 policy injection. Impact Cedar-expression injection via unescaped toCedarExpr() The toCedarExpr() method on Cedar Value types does not escape special characters (" or \) when converting values to Cedar source code. If an integrator uses toCedarExpr() to build policy text at runtime from user-controlled values, an actor could inject arbitrary Cedar expressions. For example, injecting || true into a permit ... when { ... } clause could make the permit unconditional, or injecting && false into a forbid clause could prevent the forbid from triggering. This issue requires the integrator to use toCedarExpr() to build policy text at runtime from user-controlled input. 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 Validate and sanitize all user-supplied input before passing it to toCedarExpr(). Avoid building policy text at runtime from user-controlled values. References If you have any questions or comments about this advisory, we ask that you contact us directly via email to [email protected]. Please do not create a public GitHub issue.
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
CVE-2026-55773 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (2.3.6, 3.4.1, 4.9.0). Upgrading removes the vulnerable code path.
maven
com.cedarpolicy:cedar-java (< 2.3.6)com.cedarpolicy:cedar-java (>= 3.1.2, < 3.4.1)com.cedarpolicy:cedar-java (>= 4.0.0, < 4.9.0)com.cedarpolicy:cedar-java → 2.3.6 (maven)com.cedarpolicy:cedar-java → 3.4.1 (maven)com.cedarpolicy:cedar-java → 4.9.0 (maven)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's Application Detection and Response identifies whether CVE-2026-55773 is reachable in your applications. Explore runtime application protection for your team.
See if CVE-2026-55773 is reachable in your applications. Get a demo
Upgrade the following packages to resolve this vulnerability:
com.cedarpolicy:cedar-java to 2.3.6 or latercom.cedarpolicy:cedar-java to 3.4.1 or latercom.cedarpolicy:cedar-java to 4.9.0 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-55773 is a high-severity code injection vulnerability in com.cedarpolicy:cedar-java (maven), affecting versions < 2.3.6. It is fixed in 2.3.6, 3.4.1, 4.9.0. Untrusted input is evaluated as executable code within the application's runtime environment.
CVE-2026-55773 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
com.cedarpolicy:cedar-java (maven) versions < 2.3.6 is affected.
Yes. CVE-2026-55773 is fixed in 2.3.6, 3.4.1, 4.9.0. Upgrade to this version or later.
Whether CVE-2026-55773 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
com.cedarpolicy:cedar-java to 2.3.6 or latercom.cedarpolicy:cedar-java to 3.4.1 or latercom.cedarpolicy:cedar-java to 4.9.0 or later