CVE-2026-41213: @node-oauth/oauth2-server is a module for implementing an OAuth2 server in Node.js
CVE-2026-41213 is a medium-severity flaw (CVSS 5.9) affecting node-oauth\/oauth2-server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
@node-oauth/oauth2-server is a module for implementing an OAuth2 server in Node.js. The token exchange path accepts RFC7636-invalid code_verifier values (including one-character strings) for S256 PKCE flows. Because short/weak verifiers are accepted and failed verifier attempts do not consume the authorization code, an attacker who intercepts an authorization code can brute-force code_verifier guesses online until token issuance succeeds.
Why this priority
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-41213?
node-oauth\/oauth2-server: upgrade to 5.3.0. Exact commands for each OS are on this page.
Is CVE-2026-41213 being exploited?
CVE-2026-41213 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-41213 affect?
CVE-2026-41213 affects node-oauth\/oauth2-server. Severity is medium (CVSS 5.9). @node-oauth/oauth2-server is a module for implementing an OAuth2 server in Node.js. The token exchange path accepts RFC7636-invalid code_verifier values (including one-character strings) for S256 PKCE flows. Because short/weak verifiers are
How urgent is CVE-2026-41213?
Priority 35/100. Public exploit reference; Remotely exploitable, no login, no user action