CVE-2026-41602

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 1.2%, top 35% 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: cisa-adp, epss
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Integer Overflow or Wraparound vulnerability in Apache Thrift TFramedTransport Go language implementation

This issue affects Apache Thrift: before 0.23.0.

Users are recommended to upgrade to version 0.23.0, which fixes the issue.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
66%
KEV
Not listed

Published

April 28, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-41602: Apache Thrift: Go TFramedTransport uint32 overflow

http://www.openwall.com/lists/oss-security/2026/04/28/6
generic
https://lists.apache.org/thread/lb4j0zyd5f3g36cos0wql925przpnwql

Vendor Advisories for CVE-2026-41602(11)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/acm-grafana-rhel9:17826933862026-07-08redhat
redhatrhacm2/acm-grafana-rhel9:17809268052026-06-11redhat
redhatrhacm2/acm-grafana-rhel9:17806770032026-06-08redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17799252732026-06-08redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17801671182026-06-04redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17792122592026-06-02redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17795794392026-06-01redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17788677532026-05-28redhat
redhatrhosdt/tempo-rhel9:17781583742026-05-07redhat
redhatrhosdt/opentelemetry-collector-rhel9:17780562672026-05-06redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
thrift0.13.0-6 ... 0.23.0-3 (29 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
thrift0.17.0-2 ... 0.24.0-2 (21 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
thrift0.19.0-4 ... 0.24.0-2 (11 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
thrift0.19.0-4 ... 0.23.0-2 (8 versions)0.23.0-3—
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/apache/thrift—0.23.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 44× 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.

Showing the most recent 100 of 244 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41602?
CVE-2026-41602 is a high vulnerability published on April 28, 2026. Integer Overflow or Wraparound vulnerability in Apache Thrift TFramedTransport Go language implementation This issue affects Apache Thrift: before 0.23.0. Users are recommended to upgrade to version 0.23.0, which fixes the issue.
When was CVE-2026-41602 disclosed?
CVE-2026-41602 was first published in the National Vulnerability Database on April 28, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41602 actively exploited?
CVE-2026-41602 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 34.2% of all scored CVEs.
What is the CVSS score of CVE-2026-41602?
CVE-2026-41602 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-41602?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41602, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41602?

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

Start Free Scan →Browse All CVEs