CVE-2025-22868 | Unexpected memory consumption during token parsing in golang.org/x/oauth2

An attacker can pass a malicious malformed token which causes unexpected memory to be consumed during parsing.

Published: 2025-02-26 Last update: 2025-05-01 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-22868 is rated Moderate Risk (40.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.12%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-22868

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-05 0.17% 0.12% -0.04%
2 2026-04-30 0.11% 0.17% +0.06%
3 2026-04-29 — 0.11% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-22868

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-22868

GitHub Security Advisory for CVE-2025-22868

GHSA-6v2p-p543-phr9 · Severity: high · Ecosystem: go — golang.org/x/oauth2 Improper Validation of Syntactic Correctness of Input vulnerability

OS Trackers for CVE-2025-22868

vendor priority summary link
debian not yet assigned CVE-2025-22868 not yet assigned priority: Debian including 1 source packages (golang-golang-x-oauth2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2025-22868
redhat high — https://access.redhat.com/security/cve/CVE-2025-22868
suse high CVE-2025-22868 severity important: SUSE including 503 source package names (2.2.1-5.22:libaudit1-3.1.1-slfo.1.1_2.1, 2.2.1-5.35:audit-3.1.1-slfo.1.1_2.1, …), 1459 product×package rows across 315 product lines (Container suse/cosign, Container suse/sl-micro/6.0/baremetal-os-container, … (315 product lines)): Fixed 881, Known Not Affected 357, Known Affected 221. https://www.suse.com/security/cve/CVE-2025-22868/
ubuntu medium CVE-2025-22868 medium priority: Ubuntu including 2 source packages (golang-golang-x-oauth2, google-guest-agent), 18 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 8, not-affected 8, ignored 2. https://ubuntu.com/security/CVE-2025-22868

Affected software / configurations for CVE-2025-22868

Vendor Product Version Raw CPE
go jws < 0.27.0 cpe:2.3:a:go:jws:*:*:*:*:*:go:*:*

References for CVE-2025-22868

URL Tags
https://go.dev/cl/652155 Patch
https://go.dev/issue/71490 Issue Tracking Patch
https://pkg.go.dev/vuln/GO-2025-3488 Third Party Advisory
cvelogic Threat Intelligence