HighGHSA-mh63-6h87-95cpCVE-2025-30204GO-2025-3553

jwt-go allows excessive memory allocation during header parsing

Published 21 Mar 2025 · Updated 10 Sept 2026

Is your project on an affected github.com/golang-jwt/jwt/v5?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=5.0.0-rc.1 <5.2.2
Fixed in
5.2.2
Update to the fixed version for your release line, for example:go get github.com/golang-jwt/jwt/v5@v5.2.2
Affected
<4.5.2
Fixed in
4.5.2
Update to the fixed version for your release line, for example:go get github.com/golang-jwt/jwt/v4@v4.5.2
Affected
>=3.2.0 <=3.2.2
Fixed in
No fix released

Details

Summary

Function `parse.ParseUnverified` currently splits (via a call to strings.Split) its argument (which is untrusted data) on periods.

As a result, in the face of a malicious request whose _Authorization_ header consists of Bearer followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument), with a constant factor of about 16. Relevant weakness: CWE-405: Asymmetric Resource Consumption (Amplification)

Details

See `parse.ParseUnverified`

Impact

Excessive memory allocation

Is GHSA-mh63-6h87-95cp in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/golang-jwt/jwt/v5, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.