CVE-2026-41213 Vulnerability Analysis & Exploit Details

CVE-2026-41213
Vulnerability Scoring

5.9
/10
Significant Risk

Security assessments indicate that CVE-2026-41213 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-41213 Details

Status: Analyzed

Last updated: 🕠 02 Jun 2026, 17:46 UTC
Originally published on: 🕖 23 Apr 2026, 19:17 UTC

Time between publication and last update: 39 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

CVE-2026-41213 Vulnerability Summary

CVE-2026-41213: @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.

Assessing the Risk of CVE-2026-41213

Access Complexity Graph

The exploitability of CVE-2026-41213 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-41213

CVE-2026-41213 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-41213, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-41213, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-41213 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-41213 poses no threat to data integrity.
  • Availability: None
    CVE-2026-41213 does not impact system availability.

CVE-2026-41213 References

External References

CWE Common Weakness Enumeration

CWE-1289

Vulnerable Configurations

  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.2.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.5.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:1.5.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:2.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.0:beta3:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.0:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.0:beta4:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.0:beta4:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.0:beta3.1:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.0:beta3.1:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.1.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.1.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.1.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.1.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:3.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.0.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.0.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.0.0:dev1:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.0.0:dev1:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.0.0:dev2:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.0.0:dev2:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:4.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc1:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc1:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc2:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc2:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc3:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc3:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc4:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc4:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc5:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.0.0:rc5:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.1.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.1.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.1.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.1.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.2.2:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:node-oauth:node-oauth\/oauth2-server:5.2.2:rc0:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2026-41213: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-54518 – jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3....
  • CVE-2026-9073 – A flaw was found in foreman-mcp-server. This component utilizes two distinct logging mechanisms that can expose sensitive session and authenticatio...
  • CVE-2026-56120 – OpenRemote before 1.25.0 contains an insecure direct object reference (IDOR) vulnerability in the bulk alarm deletion endpoint that allows authenti...
  • CVE-2026-54517 – jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3....
  • CVE-2026-54516 – jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3....