Answer in brief
CVE-2026-55701 records a Medium severity vulnerability in OpenTelemetry githubreceiver silently ignores configured required_headers authentication. The current sources do not mark it as known exploited. The current feed maps open-telemetry/github.com/open-telemetry/opentelemetry-collector-contrib/receiver/githubreceiver (generic), open-telemetry/opentelemetry-collector-contrib (generic), github.com/open-telemetry/opentelemetry-collector-contrib/receiver/githubreceiver (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps open-telemetry/github.com/open-telemetry/opentelemetry-collector-contrib/receiver/githubreceiver (generic), open-telemetry/opentelemetry-collector-contrib (generic), github.com/open-telemetry/opentelemetry-collector-contrib/receiver/githubreceiver (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| open-telemetry/github.com/open-telemetry/opentelemetry-collector-contrib/receiver/githubreceivergeneric | < 0.151.0 | Not reported |
| open-telemetry/opentelemetry-collector-contribgeneric | < 0.151.0 | Not reported |
| github.com/open-telemetry/opentelemetry-collector-contrib/receiver/githubreceivergo | <=0.150.0 | 0.151.0 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.