Skip to main content
VulnerabilityPublished Updated

CVE-2025-61920: Mcpm · Authlib is vulnerable to Denial of Service via Oversized JOSE Segments

Affects mcpmSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.9.0 soon.

Data as of 1 Nov 2026, 11:02 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.9.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade mcpm to 2.9.0.

Affected software

ProductAffectedFixed in
Homebrewmcpmpkg:brew/mcpmOther threatsAffected
  • >=2.1.0 <2.9.0
Fixed in
  • 2.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available that enforces maximum decoded size limits of 256 KB on JWS/JWT header and signature segments in Authlib. Users should upgrade to a patched release immediately. As additional defense, inputs exceeding a few kilobytes should be rejected at proxy or WAF layers, and rate limiting should be applied to verification endpoints. Temporary workarounds include enforcing input size limits before token processing and applying application-level throttling to reduce amplification risk.

Description

Authlib versions up to 1.6.3 have a vulnerability in their JOSE implementation where oversized JWS/JWT header or signature segments can cause excessive CPU and memory consumption during verification, leading to denial of service. The vulnerability arises because the library accepts unbounded base64url-encoded segments, which can be crafted to span hundreds of megabytes. Later versions with limits on header and signature segment sizes are not affected.

References

Community reviews

Loading reviews…