# 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.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **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

## 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.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## 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 | Ecosystem | 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.

## Is CVE-2026-47256 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47256 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47256 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47256 exists.

Affected packages and fixed versions:
- github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go): affected all versions; fixed in 0.154.0
- github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go): affected all versions; fixed in 0.154.0
- github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go): affected all versions; fixed in 0.154.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47256/ (Markdown: https://insights.sbomify.com/CVE-2026-47256/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47256
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47256
- OSV: https://osv.dev/vulnerability/CVE-2026-47256

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47256/
Summaries are generated and may contain mistakes; the official description above is the record.