CVE-2026-41178

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Versions 1.41.0 and 1.43.0 removed raw-length rejection and it causes Parse to process arbitrarily large/invalid baggage headers and log errors, enabling DoS via oversized inputs. Versions 1.42.0 and 1.44.0 fix the issue.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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 (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

May 28, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jun 17, 2026
Patch available. Sources: github_pr, github.
GitHub advisoryMentions a patch (unverified)

Baggage parsing no longer caps raw header length · Advisory · open-telemetry/opentelemetry-go · GitHub

https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-5wrp-cwcj-q835
GitHub pull request

Comply with W3C Baggage specification limits

Fix merged in open-telemetry/opentelemetry-go PR #7880 on 2026-02-28 — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-go/pull/7880

Vendor Advisories for CVE-2026-41178(20)

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

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatosbuild-composer-0:165.1-5.el10_22026-09-11redhat
redhatopenshift-logging/lokistack-gateway-rhel9:17881533562026-09-10redhat
redhatexternal-secrets-operator/external-secrets-rhel9:17889639292026-09-10redhat
redhatosbuild-composer-0:134.1-12.el10_02026-09-10redhat
redhatoadp/oadp-velero-rhel9:17888604612026-09-09redhat
redhatrhoai/odh-kueue-controller-rhel9:17883184242026-09-08redhat
redhatignition-0:2.21.0-7.el9_6.12026-09-08redhat
redhatodf4/rook-ceph-rhel9-operator:17881648572026-09-08redhat
redhatrhosdt/tempo-rhel9-operator:17883551832026-09-08redhat
redhatopentelemetry-collector-0:0.152.1-2.el9_82026-09-08redhat
redhatopentelemetry-collector-0:0.152.1-2.el10_22026-09-08redhat
redhatrhacm2/subctl-rhel9:17881050722026-09-03redhat
redhatrhdh/rhdh-rhel9-operator:17882787862026-09-02redhat
redhatcluster-observability-operator/prometheus-rhel9:17875937052026-08-31redhat
redhatrhacm2/acm-volsync-addon-controller-rhel9:17872663602026-08-26redhat
redhatrhacm2/acm-volsync-addon-controller-rhel9:17876835602026-08-26redhat
redhatrhacm2/acm-volsync-addon-controller-rhel9:17872665642026-08-26redhat
redhatopenshift-service-mesh/kiali-rhel9:17871656832026-08-25redhat
redhatrhosdt/opentelemetry-rhel9-operator:17866351752026-08-13redhat

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

(6 across 4 ecosystems)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
go.opentelemetry.io/otel—
  • 1.41.0 up to 1.42.0: fixed in 1.42.0
  • 1.43.0 up to 1.44.0: fixed in 1.44.0
—
go.opentelemetry.io/otel/baggage1.43.0
  • 1.41.0 up to 1.42.0: fixed in 1.42.0
  • 1.43.0 up to 1.44.0: fixed in 1.44.0
—
go.opentelemetry.io/otel/propagation1.43.0
  • 1.41.0 up to 1.42.0: fixed in 1.42.0
  • 1.43.0 up to 1.44.0: fixed in 1.44.0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-otel1.1.0-2 ... 1.46.0-2 (21 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-otel1.31.0-4 ... 1.46.0-2 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-otel1.31.0-4 ... 1.46.0-1~exp1 (8 versions)
  • every version up to 1.46.0-2: fixed in 1.46.0-2
—

Weakness Classification(1)

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

All Vendor Advisories

(21)

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 11× in last 7d / 26× 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.

Showing the most recent 100 of 166 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 66 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  3. 2026-10-12 16:08 UTCEG score recompute
  4. 2026-10-11 19:51 UTCEG score recompute
  5. 2026-10-11 17:04 UTCEG score recompute
  6. 2026-10-11 14:30 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-10-03 15:18 UTCOSV refresh
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  22. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  24. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 75 more
  1. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-09-14 06:41 UTCEG score recompute
  3. 2026-09-14 06:41 UTCVendor advisory
  4. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-09-13 02:09 UTCOSV refresh
  6. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  7. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  11. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  12. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  13. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  16. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  19. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  21. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  23. 2026-08-25 04:40 UTCEG score recompute
  24. 2026-08-25 04:40 UTCVendor advisory
  25. 2026-08-23 14:28 UTCEG score recompute
  26. 2026-08-23 14:28 UTCVendor advisory
  27. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  28. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-08-21 15:25 UTCEG score recompute
  30. 2026-08-21 15:25 UTCVendor advisory
  31. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-08-20 10:45 UTCEG score recompute
  33. 2026-08-20 10:45 UTCVendor advisory
  34. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  36. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-08-17 08:00 UTCEG score recompute
  38. 2026-08-17 08:00 UTCVendor advisory
  39. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  40. 2026-08-16 02:33 UTCEG score recompute
  41. 2026-08-16 02:33 UTCVendor advisory
  42. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-08-15 01:22 UTCVendor advisory
  45. 2026-08-14 01:13 UTCEG score recompute
  46. 2026-08-14 01:13 UTCVendor advisory
  47. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-08-13 01:04 UTCEG score recompute
  49. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-08-12 00:55 UTCEG score recompute
  51. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-08-11 00:46 UTCEG score recompute
  53. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  54. 2026-08-10 00:37 UTCEG score recompute
  55. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  56. 2026-08-09 00:28 UTCEG score recompute
  57. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  58. 2026-08-08 00:13 UTCEG score recompute
  59. 2026-08-07 00:04 UTCEG score recompute
  60. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  61. 2026-08-05 23:50 UTCEG score recompute
  62. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  63. 2026-08-04 23:41 UTCEG score recompute
  64. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  65. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  66. 2026-08-02 14:37 UTCEG score recompute
  67. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  68. 2026-08-01 14:28 UTCEG score recompute
  69. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  70. 2026-07-31 06:19 UTCEG score recompute
  71. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  72. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  73. 2026-07-29 12:36 UTCEG score recompute
  74. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  75. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.2% · 14th percentile

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

Frequently asked(5)

What is CVE-2026-41178?
CVE-2026-41178 is a medium-severity vulnerability; its CVE record was published on May 28, 2026. OpenTelemetry-Go is the Go implementation of OpenTelemetry. Versions 1.41.0 and 1.43.0 removed raw-length rejection and it causes Parse to process arbitrarily large/invalid baggage headers and log errors, enabling DoS via oversized inputs. Versions 1.42.0 and 1.44.0 fix the issue.
When was the CVE record for CVE-2026-41178 published?
The CVE record for CVE-2026-41178 was published on May 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-41178 actively exploited?
CVE-2026-41178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41178?
CVE-2026-41178 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-41178?
A fix for CVE-2026-41178 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41178 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-41178

Explore →

Is Your Infrastructure Affected by CVE-2026-41178?

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

Book a Demo →Browse All CVEs