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.
CVE-2026-47256
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-06-18. A secondary CVSS source baseline 5.3; sources differ by 0.0.
Also known asEUVD-2026-77692 (ENISA EUVD) · GHSA-4jvg-4jfx-fmhc (GitHub Security Advisories) · GO-2026-5126 (OSV.dev)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 37th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
June 18, 2026
Last Modified
September 25, 2026
Advisory Details (3)
Auto-updated Sep 14, 2026v0.154.0
Patch available: open-telemetry/opentelemetry-collector-contrib v0.154.0
https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.154.0commit 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/3113638f216143f523b57f447728464337ae4903Path 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-fmhcVendor 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(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | opentelemetry-collector-contrib-main-0.160.0-0.1.hum1 | 2026-09-03 | redhat |
| go | github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter @ 0.154.0 (fixes < 0.154.0) | — | ghsa |
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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-opentelemetry-contrib | 0.56.0-5, 1.39.0-2, 1.39.0-3, 1.43.0-1 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-opentelemetry-contrib | 0.56.0-5, 1.39.0-2, 1.39.0-3, 1.43.0-1 |
| — |
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter | — |
| — |
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 10× in last 7d / 42× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-01 07:47 UTCGHSA enrichmentGHSA-4jvg-4jfx-fmhc · GitHub severity MODERATE · GitHub CVSS 5.3
- 2026-11-01 07:47 UTCEG score recompute
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-30 14:55 UTCOSV refresh
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-25 14:24 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-22 23:14 UTCEG score recompute
- 2026-10-22 23:14 UTCVendor advisory
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-18 03:36 UTCEG score recompute
- 2026-10-17 19:55 UTCOSV refresh
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 37 moreShow fewer
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-12 16:02 UTCEG score recompute
- 2026-10-11 19:44 UTCEG score recompute
- 2026-10-11 16:59 UTCEG score recompute
- 2026-10-11 14:24 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-25 14:42 UTCEG score recompute
- 2026-09-25 14:42 UTCVendor advisory
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-14 19:24 UTCEG score recompute
- 2026-09-14 18:38 UTCEG score recompute
- 2026-07-31 04:44 UTCEG score recompute
- 2026-07-26 17:43 UTCEG score recompute
- 2026-07-23 03:17 UTCEG score recompute
- 2026-06-18 15:08 UTCEG score recompute
Related CVEs(same product + same vendor + same CWE)
Frequently asked(5)
What is CVE-2026-47256?
When was the CVE record for CVE-2026-47256 published?
Is CVE-2026-47256 actively exploited?
What is the CVSS score of CVE-2026-47256?
How do I remediate CVE-2026-47256?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47256
Is Your Infrastructure Affected by CVE-2026-47256?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.