CVE-2026-54712

OpenTelemetry Javaagent RMI context propagation allows resource exhaustion

The RMI context propagation payload reader limits the number of context entries but does not limit the aggregate size of the strings read from the stream.

An attacker who can reach an RMI endpoint on an instrumented JVM can send an oversized context propagation payload. This can cause excessive memory allocation while the JVM reads the payload, potentially leading to denial of service.

The issue affects only deployments where RMI instrumentation is enabled and an RMI endpoint is network-reachable.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2026-54712 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no 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.27.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-54712? CVE-2026-54712 is a medium-severity uncontrolled resource consumption vulnerability in io.opentelemetry.javaagent:opentelemetry-javaagent (maven), affecting versions < 2.27.0. It is fixed in 2.27.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2026-54712? CVE-2026-54712 has a CVSS score of 5.3 (Medium). 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.
3. Which versions of io.opentelemetry.javaagent:opentelemetry-javaagent are affected by CVE-2026-54712? io.opentelemetry.javaagent:opentelemetry-javaagent (maven) versions < 2.27.0 is affected.
4. Is there a fix for CVE-2026-54712? Yes. CVE-2026-54712 is fixed in 2.27.0. Upgrade to this version or later.
5. Is CVE-2026-54712 exploitable, and should I be worried? Whether CVE-2026-54712 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
6. What actually determines whether CVE-2026-54712 is exploitable, and how bad it is? 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.
7. How do I fix CVE-2026-54712? Upgrade io.opentelemetry.javaagent:opentelemetry-javaagent to 2.27.0 or later.

Other vulnerabilities in io.opentelemetry.javaagent:opentelemetry-javaagent