Unknown severity · Source severity not reportedCVE-2025-30204GHSA-MH63-6H87-95CP

Excessive memory allocation during header parsing in github.com/golang-jwt/jwtCVE-2025-30204

Answer in brief

CVE-2025-30204 records a Unknown severity vulnerability in Excessive memory allocation during header parsing in github.com/golang-jwt/jwt. The current sources do not mark it as known exploited. The current feed maps github.com/golang-jwt/jwt (go), github.com/golang-jwt/jwt/v4 (go), github.com/golang-jwt/jwt/v5 (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Mar 26, 2025Updated Nov 14, 2026Source checked Nov 14, 2026First seen by HOL Aug 8, 2026Material review Nov 14, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/golang-jwt/jwt (go), github.com/golang-jwt/jwt/v4 (go), github.com/golang-jwt/jwt/v5 (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
github.com/golang-jwt/jwtgo	>=0	Not reported
github.com/golang-jwt/jwt/v4go	>=0 <4.5.2	4.5.2
github.com/golang-jwt/jwt/v5go	>=5.0.0-rc.1 <5.2.2	5.2.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for github.com/golang-jwt/jwt, github.com/golang-jwt/jwt/v4, github.com/golang-jwt/jwt/v5.
Review the reported fix. Update github.com/golang-jwt/jwt/v4 to 4.5.2; github.com/golang-jwt/jwt/v5 to 5.2.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Mar 26, 2025
Evidence: source:osv:source_dates:source-dates:record
Source modified
Nov 14, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 8, 2026

Sources and claim methodology

Upstream source description

Excessive memory allocation during header parsing in github.com/golang-jwt/jwt

Quoted source text, attributed separately from HOL analysis.

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/golang-jwt/jwt (go), github.com/golang-jwt/jwt/v4 (go), github.com/golang-jwt/jwt/v5 (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
github.com/golang-jwt/jwtgo	>=0	Not reported
github.com/golang-jwt/jwt/v4go	>=0 <4.5.2	4.5.2
github.com/golang-jwt/jwt/v5go	>=5.0.0-rc.1 <5.2.2	5.2.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for github.com/golang-jwt/jwt, github.com/golang-jwt/jwt/v4, github.com/golang-jwt/jwt/v5.

Review the reported fix. Update github.com/golang-jwt/jwt/v4 to 4.5.2; github.com/golang-jwt/jwt/v5 to 5.2.2 if you use the affected versions. Test the change in a non-production environment first.