Quick answers
- Is CVE-2026-48990 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48990 being exploited in the wild.
- How severe is CVE-2026-48990?
- Medium severity, with a CVSS score of 5.3, published 17 June 2026.
- Which products and versions are affected?
- Authlib Joserfc >= 1.3.4, < 1.6.7, >= 1.3.4, <= 1.6.5; joserfc (PyPI) ECOSYSTEM:introduced=1.3.4,fixed=1.6.7.
- Is there a fix for CVE-2026-48990?
- Yes. joserfc (PyPI): upgrade to 1.6.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48990 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-48990?
- Check whether you run Authlib Joserfc or joserfc (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- joserfc (PyPI): upgrade to 1.6.7 or later
pip install "joserfc>=1.6.7"
Technical details
A vulnerability in joserfc's deserialization logic allows RFC7797 JWS payloads with the 'b64=false' header to bypass configured size limits. While standard JWS paths correctly invoke validate_payload_size() before decoding, the unencoded payload paths in both compact and flattened JSON deserialization assign the payload segment directly without validation. An unauthenticated remote attacker can exploit this by providing oversized payloads to trigger resource exhaustion or DoS. The issue is fixed in version 1.6.7 by ensuring registry.validate_payload_size() is called for unencoded payload segments.
Affected products
- authlib joserfc >= 1.3.4, < 1.6.7
Identifiers
- CVE-2026-48990
- GHSA-wphv-vfrh-23q5
- PYSEC-2026-2530
Timeline
- 2026-05-24: disclosed
- 2026-06-26: advisory: GitHub Advisory published
- 1.6.7: patched