CVE-2026-44967

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 89% 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
Trending — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

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

OpenTelemetry-cpp is the C++ implementation of OpenTelemetry. Prior to release 1.27.0, the OTLP HTTP exporters (traces/metrics/logs) read the full HTTP response into an in-memory vector of bytes without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can MITM the exporter connection). This vulnerability is fixed in opentelemetry-cpp release 1.27.0.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
10.8%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 16, 2026

Advisory Details (4)

Auto-updated Jun 16, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github.
github Patch Available🟡 PoC Available

OTLP HTTP exporters read unbounded HTTP response bodies · Advisory · open-telemetry/opentelemetry-go · GitHub

https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58
github Patch Available

opentelemetry-cpp: OTLP HTTP exporters read unbounded HTTP response · Advisory · open-telemetry/opentelemetry-cpp · GitHub

https://github.com/open-telemetry/opentelemetry-cpp/security/advisories/GHSA-5qhm-4rfp-qqvj
github_pr

[EXPORTER] OTLP HTTP exporter reads unbounded response

Fix merged in open-telemetry/opentelemetry-cpp PR #4078 on 2026-05-12 — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-cpp/pull/4078
generic

[EXPORTER] OTLP HTTP exporter reads unbounded response · Issue #3958 · open-telemetry/opentelemetry-cpp · GitHub

https://github.com/open-telemetry/opentelemetry-cpp/issues/3958

Vendor Advisories for CVE-2026-44967(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 57× 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-07 05:09 UTCEG score recompute
  2. 2026-07-07 05:09 UTCVendor advisory
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 01:13 UTCEG score recompute
  5. 2026-07-06 01:13 UTCVendor advisory
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 22:46 UTCEG score recompute
  8. 2026-07-04 22:46 UTCVendor advisory
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 20:24 UTCEG score recompute
  11. 2026-07-03 20:24 UTCVendor advisory
  12. 2026-07-02 18:04 UTCEG score recompute
  13. 2026-07-02 18:04 UTCVendor advisory
  14. 2026-07-01 15:42 UTCEG score recompute
  15. 2026-07-01 15:42 UTCVendor advisory
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 13:19 UTCEG score recompute
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 07:47 UTCEG score recompute
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 05:17 UTCEG score recompute
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
Show 32 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-27 02:56 UTCEG score recompute
  3. 2026-06-26 00:36 UTCEG score recompute
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-24 22:13 UTCEG score recompute
  6. 2026-06-24 14:05 UTCEPSS rescore
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-23 19:53 UTCEG score recompute
  9. 2026-06-22 17:32 UTCEG score recompute
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 14:08 UTCEG score recompute
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-20 11:44 UTCEG score recompute
  17. 2026-06-19 19:25 UTCEPSS rescore
  18. 2026-06-19 09:21 UTCEG score recompute
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-18 17:52 UTCEPSS rescore
  21. 2026-06-18 06:59 UTCEG score recompute
  22. 2026-06-17 17:53 UTCEPSS rescore
  23. 2026-06-17 03:38 UTCEG score recompute
  24. 2026-06-16 17:52 UTCEPSS rescore
  25. 2026-06-16 01:17 UTCEG score recompute
  26. 2026-06-15 17:49 UTCEPSS rescore
  27. 2026-06-14 22:56 UTCEG score recompute
  28. 2026-06-13 23:00 UTCEPSS rescore
  29. 2026-06-13 20:36 UTCEG score recompute
  30. 2026-06-12 23:12 UTCEPSS rescore
  31. 2026-06-12 18:15 UTCEG score recompute
  32. 2026-06-12 18:12 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-44967?
CVE-2026-44967 is a medium vulnerability published on June 12, 2026. OpenTelemetry-cpp is the C++ implementation of OpenTelemetry. Prior to release 1.27.0, the OTLP HTTP exporters (traces/metrics/logs) read the full HTTP response into an in-memory vector of bytes without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is…
When was CVE-2026-44967 disclosed?
CVE-2026-44967 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44967 actively exploited?
CVE-2026-44967 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44967?
CVE-2026-44967 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-44967?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44967, 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-44967

Explore →

Is Your Infrastructure Affected by CVE-2026-44967?

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

Start Free Scan →Browse All CVEs