Skip to content

golang.org/x/oauth2 Improper Validation of Syntactic Correctness of Input vulnerability

High severity GitHub Reviewed Published Jul 18, 2025 to the GitHub Advisory Database • Updated Jul 18, 2025

Package

gomod golang.org/x/oauth2 (Go)

Affected versions

< 0.27.0

Patched versions

0.27.0

Description

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

References

Published by the National Vulnerability Database Feb 26, 2025
Published to the GitHub Advisory Database Jul 18, 2025
Reviewed Jul 18, 2025
Last updated Jul 18, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(23rd percentile)

Weaknesses

Improper Validation of Syntactic Correctness of Input

The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax. Learn more on MITRE.

CVE ID

CVE-2025-22868

GHSA ID

GHSA-6v2p-p543-phr9

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.