CVE-2026-54712

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% 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, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

OpenTelemetry Java Instrumentation provides OpenTelemetry auto-instrumentation and instrumentation libraries for Java. In versions prior to 2.27.0, 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. This issue has been fixed in version 2.27.0.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
17.7%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 6, 2026

Advisory Details (1)

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

OpenTelemetry Javaagent RMI context propagation allows resource exhaustion · Advisory · open-telemetry/opentelemetry-java-instrumentation · GitHub

https://github.com/open-telemetry/opentelemetry-java-instrumentation/security/advisories/GHSA-fq3f-m5qm-99f5

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 41× 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-07-14 11:14 UTCEG score recompute
  2. 2026-07-13 22:31 UTCEPSS rescore
  3. 2026-07-13 22:18 UTCEG score recompute
  4. 2026-07-13 09:21 UTCEG score recompute
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 20:25 UTCEG score recompute
  8. 2026-07-12 07:29 UTCEG score recompute
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 18:32 UTCEG score recompute
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 05:36 UTCEG score recompute
  14. 2026-07-10 16:39 UTCEG score recompute
  15. 2026-07-10 03:43 UTCEG score recompute
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 14:40 UTCEG score recompute
  19. 2026-07-09 01:42 UTCEG score recompute
  20. 2026-07-08 15:16 UTCEPSS rescore
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 12:45 UTCEG score recompute
  23. 2026-07-07 23:47 UTCEG score recompute
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-07 13:46 UTCEPSS rescore
Show 16 more
  1. 2026-07-07 10:51 UTCEG score recompute▲ 2.20
  2. 2026-07-06 18:21 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 08:28 UTCEG score recompute
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 06:08 UTCEG score recompute
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 03:49 UTCEG score recompute
  14. 2026-07-03 01:27 UTCEG score recompute
  15. 2026-07-01 23:09 UTCEG score recompute
  16. 2026-07-01 23:08 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54712?
CVE-2026-54712 is a high vulnerability published on July 1, 2026. OpenTelemetry Java Instrumentation provides OpenTelemetry auto-instrumentation and instrumentation libraries for Java. In versions prior to 2.27.0, 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…
When was CVE-2026-54712 disclosed?
CVE-2026-54712 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54712 actively exploited?
CVE-2026-54712 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54712?
CVE-2026-54712 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-54712?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54712, 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

Explore the affected products and dependency analysis for CVE-2026-54712

Explore →

Is Your Infrastructure Affected by CVE-2026-54712?

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

Start Free Scan →Browse All CVEs