Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
MediumPublic exploit

Memory exhaustion in OpenTelemetry-cpp OTLP HTTP exporters

IdentifiersCVE-2026-44967CWE-770

CVE-2026-44967 affects OpenTelemetry-cpp prior to 1.27.0. The OTLP HTTP exporters for traces, metrics, and logs read the entire HTTP response body into an in-memory byte vector without enforcing a maximum size. If the configured collector endpoint is attacker-controlled, or if an attacker can perform a man-in-the-middle attack on the exporter connection, the attacker can return an excessively large HTTP response that causes unbounded memory consumption in the exporting process. The issue is fixed in OpenTelemetry-cpp 1.27.0.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause memory exhaustion in the process using the OpenTelemetry-cpp OTLP HTTP exporters, potentially leading to process instability, degraded performance, or denial of service due to excessive memory consumption or termination by the operating system/runtime.

Mitigation

If you can’t patch tonight, do this now.

Until an upgrade can be applied, restrict exporter connections to trusted collector endpoints only, prevent attacker control over OTLP collector configuration, and protect the exporter transport against man-in-the-middle interception, for example by enforcing authenticated TLS and appropriate certificate validation. Network controls that limit connectivity to approved collectors can also reduce exposure.

Remediation

Patch, then assume compromise.

Upgrade OpenTelemetry-cpp to version 1.27.0 or later, which fixes the issue by addressing the unbounded response-body handling in the OTLP HTTP exporters.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpentelemetryOpentelemetryapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

10 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity10

Community discussion across Reddit, Mastodon, and other social sources.