CVE-2026-557016.9MediumCWE-863

CVE-2026-55701: OpenTelemetry githubreceiver silently ignores configured required_headers authentication

open-telemetry · opentelemetry-collector-contrib

Affected: open-telemetry opentelemetry-collector-contrib · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.7%probability of exploitation in the next 30 days

53rd percentile

050100

Higher than 53% of scored CVEs

6.9MediumCVSS 4.0

LowMediumHighCrit.

DescriptionCVE.org

The OpenTelemetry Collector Contrib repository contains components for the OpenTelemetry Collector. Prior to 0.151.0, the githubreceiver validates the receiver/githubreceiver/config.go RequiredHeaders configuration at startup, but receiver/githubreceiver/trace_receiver.go handleReq() does not check those headers on incoming webhook requests. An unauthenticated sender can therefore bypass an operator's required_headers authentication control and submit arbitrary webhook payloads. When the Secret field is empty, github.ValidatePayload also skips HMAC validation, leaving the webhook endpoint without either configured authentication mechanism. Successful exploitation can inject fabricated CI/CD trace data into the observability pipeline. This issue is fixed in version 0.151.0.

Affected products2

From the CVE record. A product or version that is not listed is unknown, not unaffected.

open-telemetry · opentelemetry-collector-contrib< 0.151.0
open-telemetry · github.com/open-telemetry/opentelemetry-collector-contrib/receiver/githubreceiver< 0.151.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Incorrect Authorization · Access Control
Vendor: open-telemetry
Published: September 2026
Band: Unlikely (under 1%), September 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-55701 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.