CVE-2025-22868
Go Jws ≤ 0.27.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2025-22868 is a high-severity Improper Validation of Syntactic Correctness of Input (CWE-1286) vulnerability in Go Jws. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 45% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-22868 is a vulnerability in the Go programming language that allows an attacker to pass a malicious malformed token, resulting in unexpected memory consumption during parsing. This issue, associated with CWE-1286, carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating a high-severity denial-of-service risk with no impact on confidentiality or integrity.
Remote attackers require only network access and no privileges or user interaction to exploit the vulnerability. Successful exploitation causes significant memory exhaustion in the affected Go component during token parsing, leading to denial of service through resource depletion.
Mitigation details are outlined in the Go security advisory GO-2025-3488 at https://pkg.go.dev/vuln/GO-2025-3488, with a related issue tracked at https://go.dev/issue/71490 and a fix submitted in code review CL 652155 at https://go.dev/cl/652155. Security practitioners should update to patched Go versions as recommended in these resources.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-5341
Vulnerability Data
An attacker can pass a malicious malformed token which causes unexpected memory to be consumed during parsing.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.1V1.4.2V2.1.1V2.2.2
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validation of information inputs for correctness, directly stopping syntactic validation failures from being introduced or exploitable.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require syntactic input validation to prevent malformed data handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches missing or incorrect syntax validation.
Secure development life cycle mandates input validation to ensure syntactic correctness.
Application security requirements explicitly call for validation of input syntax.
Secure architecture principles reduce the likelihood of missing syntactic checks.
Secure coding standards directly require proper syntactic validation of all inputs.