CVE-2026-49158

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-27. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Apache Thrift Ruby bindings.

This issue affects Apache Thrift: before 0.24.0.

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

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation1.0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
1.0%
EPSS %ILE
62nd
KEV
Not listed

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 none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

July 27, 2026

Last Modified

July 27, 2026

Advisory Details (2)

Auto-updated Jul 27, 2026
Patch available.
Web page
https://lists.apache.org/thread/fmjl8l415tj9zwlob8v2dr5hq1d0hts7
Web page
https://lists.apache.org/thread/7v3jhgwfbmhx42424phydlnzb109g8b9

Vendor Advisories for CVE-2026-49158(2)

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
redhatthrift-main-0.24.0-0.1.hum12026-08-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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
thrift0.13.0-6 ... 0.23.0-3 (29 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
thrift0.17.0-2 ... 0.24.0-2 (21 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
thrift0.19.0-4 ... 0.24.0-2 (11 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
thrift0.19.0-4 ... 0.24.0-2 (11 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 87× 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 262 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 162 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-49158?
CVE-2026-49158 is a high-severity vulnerability; its CVE record was published on July 27, 2026. Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Apache Thrift Ruby bindings. This issue affects Apache Thrift: before 0.24.0. Users are recommended to upgrade to version 0.24.0, which fixes the issue.
When was the CVE record for CVE-2026-49158 published?
The CVE record for CVE-2026-49158 was published on July 27, 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 27, 2026; the record at its source may have been updated since.
Is CVE-2026-49158 actively exploited?
CVE-2026-49158 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49158?
CVE-2026-49158 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-49158?
A fix for CVE-2026-49158 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49158 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-49158

Explore →

Is Your Infrastructure Affected by CVE-2026-49158?

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

Book a Demo →Browse All CVEs