OpenTelemetry Javaagent RMI context propagation allows resource exhaustion

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2026-54712: 0.46% estimated exploitation activity in the next 30 days; percentile 39.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

29 Jul 2026, 17:16 UTC

Last modified by the source

29 Jul 2026, 17:30 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fq3f-m5qm-99f5

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-fq3f-m5qm-99f5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54712

Advisory: OpenTelemetry Javaagent RMI context propagation allows resource exhaustion
IDs: CVE-2026-54712, GHSA-fq3f-m5qm-99f5
Record: https://patchnext.com/advisories/cve-2026-54712 (revision 2, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.opentelemetry.javaagent:opentelemetry-javaagent 2.27.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.opentelemetry.javaagent:opentelemetry-javaagent: affected < 2.27.0; fixed in 2.27.0

## Suggested inspection (read-only)
- Maven io.opentelemetry.javaagent:opentelemetry-javaagent: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.opentelemetry.javaagent:opentelemetry-javaagent.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-fq3f-m5qm-99f5 (OSV record GHSA-fq3f-m5qm-99f5 lists affected ranges: Maven io.opentelemetry.javaagent:opentelemetry-javaagent >=0 <2.27.0 (fixed))
- Verified: https://github.com/advisories/GHSA-fq3f-m5qm-99f5 (GitHub-reviewed advisory GHSA-fq3f-m5qm-99f5 lists affected ranges: Maven io.opentelemetry.javaagent:opentelemetry-javaagent >=0 <2.27.0)

Commands are suggestions: review each one before running it.