Advisory record · GHSA-frfh-8v73-gjg4

joserfc has Possible Uncontrolled Resource Consumption Vulnerability Triggered by Logging Arbitrarily Large JWT Token Payloads

CVSS 9.2 CriticalCriticalEPSS 0.0044 · 38th percentile

Critical, because:

  • CVSS score 9.2: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 18 Nov 2025, 18:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
joserfcPyPI>=1.3.3, <1.3.5 || >=1.4.0, <1.4.21.3.5, 1.4.2
Identifiers
GHSA-frfh-8v73-gjg4 · CVE-2025-65015 · PYSEC-2026-361
Weakness (CWE)
CWE-770
Published
18 Nov 2025
Updated
27 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The joserfc Python package, versions 1.3.3 to before 1.3.5 and 1.4.0 to before 1.4.2, embeds full JWT token parts into ExceededSizeError exception messages, so logging or diagnostic tools can record very large token contents. An attacker who can send bearer tokens in HTTP request headers could trigger this when no proper header size limit is enforced upstream, leading to resource consumption on the host and in log pipelines. Upgrade to joserfc 1.3.5 or 1.4.2, which are the fixed versions listed.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.2 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0044, the 38th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.