CVE-2026-47256 opentelemetry-collector-contrib sentryexporter: Path traversal in Sentry exporter via attacker-controlled service.name reaches privileged Sentry API endpoints with operator bearer token
Attacker-controlled service.name allows path traversal to access privileged Sentry API endpoints, potentially exposing or modifying telemetry data.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-47256?
CVE-2026-47256 is a medium-severity path traversal vulnerability in github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
OpenTelemetry, also known as OTel, is a vendor-neutral open source Observability framework for instrumenting, generating, collecting, and exporting telemetry data such as traces, metrics, and logs. Prior to 0.154.0, the Sentry exporter reads the remote OTLP sender-controlled service.name resource attribute in exporter/sentryexporter/sentry_exporter.go through extractProjectSlug and getOrCreateProjectEndpoint, passes the raw project slug to GetOTLPEndpoints and GetProjectKeys in exporter/sentryexporter/sentry_client.go, and interpolates it into a Sentry API URL without applying projectSlugRegexp through validateRoutingConfig at runtime in exporter/sentryexporter/config.go. Special characters can turn the expected path suffix into query data in all deployments or introduce slash and dot segments that traverse paths when the Sentry deployment normalizes them, while the Collector attaches its operator-configured bearer token to the request. A successful request can reach token-authorized administrative, organization, member, or key endpoints within the configured Sentry organization, and an attacker-controlled project slug can redirect subsequently exported telemetry. Sentry token middleware prevents cross-organization access. This issue is fixed in version 0.154.0.
Which versions are affected by CVE-2026-47256?
3 open source packages ship an affected version, including github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter.
| Package | Affected | Fixed in |
|---|---|---|
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter Go | All versions | 0.154.0 |
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter Go | All versions | 0.154.0 |
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter Go | All versions | 0.154.0 |
How do I fix CVE-2026-47256?
Upgrade github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter to 0.154.0 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-47256 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47256 exists.
Sources
Also known as DEBIAN-CVE-2026-47256, ECHO-cd26-8af5-522c, GHSA-4jvg-4jfx-fmhc, GO-2026-5126, MINI-5pxr-jmwg-xjmq, MINI-pf9w-679g-mg3m.