CVE-2026-47256

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

Published

June 18, 2026

Last Modified

September 25, 2026

Advisory Details (3)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v0.154.0

Patch available: open-telemetry/opentelemetry-collector-contrib v0.154.0

https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.154.0
github_commit

commit 3113638f2161 (open-telemetry/opentelemetry-collector-contrib)

Fix landed in open-telemetry/opentelemetry-collector-contrib commit 3113638f2161 — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-collector-contrib/commit/3113638f216143f523b57f447728464337ae4903
githubMentions a patch (unverified)

Path traversal in Sentry exporter via attacker-controlled service.name reaches privileged Sentry API endpoints with operator bearer token · Advisory · open-telemetry/opentelemetry-collector-contrib · GitHub

https://github.com/open-telemetry/opentelemetry-collector-contrib/security/advisories/GHSA-4jvg-4jfx-fmhc

Vendor Advisories for CVE-2026-47256(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopentelemetry-collector-contrib-main-0.160.0-0.1.hum12026-09-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-contrib0.56.0-5, 1.39.0-2, 1.39.0-3, 1.43.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-contrib0.56.0-5, 1.39.0-2, 1.39.0-3, 1.43.0-1
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter—
  • every version up to 0.154.0: fixed in 0.154.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-26 00:27 UTCEPSS rescore
  14. 2026-09-25 14:42 UTCEG score recompute
  15. 2026-09-25 14:42 UTCVendor advisory
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-14 19:24 UTCEG score recompute
  22. 2026-09-14 18:38 UTCEG score recompute
  23. 2026-07-31 04:44 UTCEG score recompute
  24. 2026-07-26 17:43 UTCEG score recompute
  25. 2026-07-23 03:17 UTCEG score recompute
Show 1 more
  1. 2026-06-18 15:08 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Same product

1 shown

Debian:13:golang-opentelemetry-contrib

Same vendor

1 shown

redhat:RHSA-2026:63152

Frequently asked(5)

What is CVE-2026-47256?
CVE-2026-47256 is a medium vulnerability published on June 18, 2026. 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…
When was CVE-2026-47256 disclosed?
CVE-2026-47256 was first published on June 18, 2026, with the most recent update on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47256 actively exploited?
CVE-2026-47256 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47256?
CVE-2026-47256 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47256?
A fix for CVE-2026-47256 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47256 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47256

Explore →

Is Your Infrastructure Affected by CVE-2026-47256?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs