Is CVE-2026-47256 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47256 being exploited in the wild.

How severe is CVE-2026-47256?

Medium severity, with a CVSS score of 5.3, published 14 September 2026.

Which products and versions are affected?

github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go) < 0.154.0, SEMVER:introduced=0,fixed=0.154.0; Opentelemetry Collector Contrib < 0.154.0.

Is there a fix for CVE-2026-47256?

Yes. github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go): upgrade to 0.154.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47256 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-47256?

Check whether you run github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go) or Opentelemetry Collector Contrib at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47256: OpenTelemetry Sentry Exporter path traversal via service.name

Q: Is there a fix for CVE-2026-47256?

Yes. github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go): upgrade to 0.154.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-47256 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-47256?

Check whether you run github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go) or Opentelemetry Collector Contrib at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47256 · Severity: medium · CVSS 5.3 · Published 2026-09-14

The OpenTelemetry Sentry exporter, which sends monitoring data to Sentry, contains a flaw that allows an attacker to manipulate the destination of that data. By sending specially crafted application names, an attacker can trick the exporter into accessing unauthorized parts of the Sentry management interface or redirecting sensitive monitoring information to an attacker-controlled project. This could lead to the exposure of internal operational data or unauthorized access to organization settings within Sentry.

Vendors: Go, Opentelemetry.

Quick answers

Is CVE-2026-47256 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47256 being exploited in the wild.
How severe is CVE-2026-47256?: Medium severity, with a CVSS score of 5.3, published 14 September 2026.
Which products and versions are affected?: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go) < 0.154.0, SEMVER:introduced=0,fixed=0.154.0; Opentelemetry Collector Contrib < 0.154.0.
Is there a fix for CVE-2026-47256?: Yes. github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go): upgrade to 0.154.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47256 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-47256?: Check whether you run github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go) or Opentelemetry Collector Contrib at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go): upgrade to 0.154.0 or later
```
go get github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter@v0.154.0
```

Technical details

The Sentry exporter in OpenTelemetry Collector Contrib fails to sanitize the 'service.name' resource attribute before interpolating it into Sentry API URLs via fmt.Sprintf. Because 'service.name' is controlled by remote OTLP senders, an attacker can inject path traversal sequences (e.g., '../') or query parameters (e.g., '?') into the URL. Since the exporter attaches a privileged operator bearer token to every request, this allows the attacker to reach arbitrary GET-based Sentry API endpoints, such as organization member lists or administrative settings. Additionally, an attacker can redirect telemetry data to their own Sentry project by manipulating the project slug. The vulnerability is fixed in version 0.154.0 by applying regex validation to runtime-derived slugs.

Affected products

OpenTelemetry opentelemetry-collector-contrib/exporter/sentryexporter < 0.154.0

Identifiers

CVE-2026-47256
GHSA-4jvg-4jfx-fmhc
GO-2026-5126

Timeline

2026-06-17: disclosed
2026-06-18: advisory: GitHub Advisory published
2026-06-18: patched: Version 0.154.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.