Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-44967: opentelemetry-cpp: OTLP HTTP exporters read unbounded HTTP response

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Someone on the same network segment can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: azl3 opentelemetry-cpp 1.14.2-2 on Azure Linux 3.0 1.14.2-3; azl3 opentelemetry-cpp 1.14.2-3 on Azure Linux 3.0 1.14.2-3.

Low priority for now. Upgrade to azl3 opentelemetry-cpp 1.14.2-2 on Azure Linux 3.0 1.14.2-3; azl3 opentelemetry-cpp 1.14.2-3 on Azure Linux 3.0 1.14.2-3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.3 · v3.1—No exploit Fix available
Published
Jun 12, 2026
Updated
Oct 26, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.3
CNA · GitHub_M
5.3
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-44967

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for opentelemetry records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opentelemetryopentelemetry

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • opentelemetry opentelemetrybefore 1.27.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • open-telemetry opentelemetry-cpp

    • < 1.27.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13opentelemetry-cppfrom 0—
Debian:14opentelemetry-cppbefore 1.28.0-11.28.0-1
Gogo.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttpbefore 0.19.00.19.0
Gogo.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttpbefore 1.43.01.43.0
Gogo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttpbefore 1.43.01.43.0

Same product

opentelemetry: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-47108DoS vulnerability in otelgrpc (uncontrolled resource consumption) due to unbound cardinality metrics
    31Monitor
  • CVE-2026-29181OpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)
    30Monitor
  • CVE-2023-45142OpenTelemetry-Go Contrib has DoS vulnerability in otelhttp due to unbound cardinality metrics
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-41078Apr 23, 2026 · OpenTelemetry dotnet: Potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path
    23Monitor
  • ← EarlierCVE-2026-41178Jun 4, 2026 · OpenTelemetry-Go's baggage parsing no longer caps raw header length
    21Monitor
  • Later →CVE-2026-54285Jun 22, 2026 · opentelemetry-js: Unbounded memory allocation in W3C Baggage propagation
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 opentelemetry-cpp 1.14.2-2 on Azure Linux 3.01.14.2-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 opentelemetry-cpp 1.14.2-3 on Azure Linux 3.01.14.2-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:opentelemetry-cpp1.28.0-1 · Debian:14Package registry (OSV)
Go:go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp0.19.0Package registry (OSV)
Go:go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp1.43.0Package registry (OSV)
Go:go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp1.43.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-4018250 days apartOpenTelemetry dotnet: OTLP exporter reads unbounded HTTP response bodies
    23Monitor
  • CVE-2026-411788 days apartOpenTelemetry-Go's baggage parsing no longer caps raw header length
    21Monitor
  • CVE-2026-4089150 days apartOpenTelemetry dotnet: Unbounded `grpc-status-details-bin` parsing in OTLP/gRPC retry handling
    21Monitor
  • CVE-2026-4089450 days apartOpenTelemetry dotnet: Excessive memory allocation when parsing OpenTelemetry propagation headers
    21Monitor
  • CVE-2026-3988265 days apartOpenTelemetry-Go OTLP HTTP exporters read unbounded HTTP response bodies
    21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone on the same network segment can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Adjacent
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-789 · Memory Allocation with Excessive Size Value

CVSS vector

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records