Skip to content
Fencer Intel
medium 5.9

CVE-2026-80179 json

Jwcrypto: jwcrypto: denial of service via malformed jwe tokens

published 2mo ago modified 19h ago also EUVD-2026-67278 , GHSA-96rv-c4vc-h4f4

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository latchset/jwcrypto. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi jwcrypto 1.5.9
  • Red Hat Red Hat Enterprise Linux 10 0:1.6.1-1.el10_3
  • python-jwcrypto SLES 16.0, SLES for SAP applications 16.0 1.5.6-160000.4.1

suse advisories SUSE-SU-2026:23702-1SUSE-SU-2026:23722-1

  • python-jwcrypto openSUSE Leap 16.0 1.5.6-160000.4.1
  • python-jwcrypto openSUSE Tumbleweed 1.6.0-1.1

opensuse advisories openSUSE-SU-2026:21827-1openSUSE-SU-2026:11712-1

Is CVE-2026-80179 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-80179 updated cvss 5.9

jwcrypto: jwcrypto: Denial of Service via malformed JWE tokens

  • Red Hat Ansible Automation Platform 2 python3.11-jwcrypto, python3.12-jwcrypto, automation-controller, ansible-automation-platform-25/gateway-rhel8, ansible-automation-platform-26/gateway-rhel9, ansible-automation-platform-27/gateway-rhel9, +7 more Red Hat Enterprise Linux 9 python-jwcrypto, python3-jwcrypto Red Hat OpenShift AI (RHOAI) rhoai/odh-feature-server-rhel9, rhoai/odh-kserve-storage-initializer-rhel9 Red Hat OpenStack Platform 16.2 rhosp-rhel8/openstack-tempest, rhosp-rhel8/openstack-nova-api, rhosp-rhel8/openstack-novajoin-base, rhosp-rhel8/openstack-tripleoclient, rhosp-rhel8/openstack-novajoin-server, rhosp-rhel8/openstack-mistral-executor, +2 more
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Enterprise Linux AppStream (v. 10) python-jwcrypto 1.6.1-1.el10_3, python3-jwcrypto 1.6.1-1.el10_3
    fixed: vendor fix RHSA-2026:98061

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/latchset/jwcrypto/security/advisories/GHSA-96rv-c4vc-h4f4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi jwcrypto
<=1.5.8
1.5.9

Affected products

  • Red Hat Red Hat Enterprise Linux 10
  • Red Hat Red Hat Ansible Automation Platform 2
  • Red Hat Red Hat Enterprise Linux 9
  • Red Hat Red Hat OpenShift AI (RHOAI)
  • Red Hat Red Hat OpenStack Platform 16.2

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of latchset/jwcrypto published their own advisory on GitHub. Reviewed sources take precedence over it.