CVE-2026-80179

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Elevated
5.9EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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.4%CVSS: 5.9Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A flaw was found in jwcrypto. A remote attacker can send a specially crafted JSON Web Encryption (JWE) token containing numerous period delimiters. This malformed token can force the JWE.deserialize() function to allocate excessive memory, leading to a MemoryError. This issue results in a denial of service (DoS) for services that process untrusted JWE values.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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)
Severity59% × 45%
The EG Score, 5.9 of 10.
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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

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.

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

August 27, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 27, 2026
No fix on record yet. Sources: redhat, github.
GitHub advisoryMentions a patch (unverified)

jwcrypto exhausts memory on compact JWE inputs with many period delimiters · Advisory · latchset/jwcrypto · GitHub

https://github.com/latchset/jwcrypto/security/advisories/GHSA-96rv-c4vc-h4f4
Red Hat

2524147 – (CVE-2026-80179) CVE-2026-80179 jwcrypto: jwcrypto: Denial of Service via malformed JWE tokens

https://bugzilla.redhat.com/show_bug.cgi?id=2524147
Red HatMentions a patch (unverified)

CVE-2026-80179 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-80179

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-jwcrypto1.1.0-1 ... 1.5.6-1.2 (7 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-jwcrypto1.5.6-1, 1.5.6-1.1, 1.5.6-1.1~deb13u1, 1.5.6-1.2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-jwcrypto1.5.6-1, 1.5.6-1.1, 1.5.6-1.1~deb13u1, 1.5.6-1.2
  • 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 14× in last 7d / 56× 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.

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. 4 repeat rows among the latest 88 are merged into the row they repeat.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-12 14:57 UTCEG score recompute
  4. 2026-10-11 19:21 UTCEG score recompute
  5. 2026-10-11 16:37 UTCEG score recompute
  6. 2026-10-11 13:56 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-10 01:55 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-09 02:55 UTCEG score recompute
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-08 01:13 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-06 17:36 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-05 18:37 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-03 17:51 UTCEG score recompute
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-10-02 18:52 UTCEG score recompute
  23. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-10-01 19:52 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 59 more
  1. 2026-09-30 19:53 UTCEG score recompute
  2. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-09-29 15:30 UTCEG score recompute
  4. 2026-09-28 16:24 UTCEG score recompute
  5. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-09-27 17:23 UTCEG score recompute
  7. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-09-26 18:22 UTCEG score recompute
  9. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-09-25 03:33 UTCEG score recompute
  12. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-09-24 04:33 UTCEG score recompute
  14. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-09-23 05:33 UTCEG score recompute
  16. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-09-22 06:33 UTCEG score recompute
  18. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-09-21 07:34 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  21. 2026-09-20 08:18 UTCEG score recompute
  22. 2026-09-19 07:46 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  24. 2026-09-18 08:44 UTCEG score recompute
  25. 2026-09-17 09:44 UTCEG score recompute
  26. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  27. 2026-09-16 10:45 UTCEG score recompute
  28. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  29. 2026-09-15 11:40 UTCEG score recompute
  30. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  31. 2026-09-14 12:40 UTCEG score recompute
  32. 2026-09-13 13:26 UTCEG score recompute
  33. 2026-09-11 15:27 UTCEG score recompute
  34. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  35. 2026-09-10 16:27 UTCEG score recompute
  36. 2026-09-09 17:20 UTCEG score recompute
  37. 2026-09-09 00:37 UTCEG score recompute
  38. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  39. 2026-09-06 16:43 UTCEG score recompute
  40. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  41. 2026-09-05 17:43 UTCEG score recompute
  42. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  43. 2026-09-04 18:44 UTCEG score recompute
  44. 2026-09-02 20:27 UTCEG score recompute
  45. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  46. 2026-09-01 20:22 UTCEG score recompute
  47. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  48. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  49. 2026-08-31 21:22 UTCEG score recompute
  50. 2026-08-31 20:55 UTCEG score recompute
  51. 2026-08-31 17:41 UTCEG score recompute
  52. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  53. 2026-08-30 18:39 UTCEG score recompute
  54. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  55. 2026-08-29 19:39 UTCEG score recompute
  56. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  57. 2026-08-28 00:31 UTCEG score recompute
  58. 2026-08-27 23:23 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  59. 2026-08-27 23:23 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-80179?
CVE-2026-80179 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. A flaw was found in jwcrypto. A remote attacker can send a specially crafted JSON Web Encryption (JWE) token containing numerous period delimiters. This malformed token can force the JWE.deserialize() function to allocate excessive memory, leading to a MemoryError. This issue results in a denial of…
When was CVE-2026-80179 made public?
CVE-2026-80179 was made public on August 26, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-80179 actively exploited?
CVE-2026-80179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80179?
CVE-2026-80179 has a CVSS base score of 5.9 (the CNA's own assessment, by redhat; NVD's own analysis pending).
How do I remediate CVE-2026-80179?
No fix for CVE-2026-80179 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-80179?

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

Book a Demo →Browse All CVEs