Answer in brief
CVE-2026-12740 records a High severity (CVSS 8.1) vulnerability in Plack::Middleware::OAuth versions through 0.10 for Perl do not support the OAuth 2.0 state parameter. The current sources do not mark it as known exploited. The current feed maps CORNELIUS/Plack::Middleware::OAuth (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps CORNELIUS/Plack::Middleware::OAuth (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| CORNELIUS/Plack::Middleware::OAuthgeneric | 0 | Not reported |
Published upstream
Jul 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 4, 2026
Plack::Middleware::OAuth versions through 0.10 for Perl do not support the OAuth 2.0 state parameter. RequestTokenV2 builds the provider authorization redirect without issuing a state value, and AccessTokenV2 exchanges the callback code and registers the resulting token into the session (register_session) without verifying that the callback corresponds to an authorization request this session initiated. Any application that uses this middleware for OAuth 2.0 login is exposed to login cross-site request forgery: because the callback is not bound to the session that began the flow, an attacker who starts an authorization with their own provider account can deliver the resulting callback to a victim, causing the victim's session to complete the attacker's authorization and associating the attacker's provider identity and access token with that session. Where the application persists this as an account link, the attacker may retain access to the victim's account through their own provider credentials.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-12740 records a High severity (CVSS 8.1) vulnerability in Plack::Middleware::OAuth versions through 0.10 for Perl do not support the OAuth 2.0 state parameter. The current sources do not mark it as known exploited. The current feed maps CORNELIUS/Plack::Middleware::OAuth (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps CORNELIUS/Plack::Middleware::OAuth (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| CORNELIUS/Plack::Middleware::OAuthgeneric | 0 | Not reported |
Published upstream
Jul 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 4, 2026
Plack::Middleware::OAuth versions through 0.10 for Perl do not support the OAuth 2.0 state parameter. RequestTokenV2 builds the provider authorization redirect without issuing a state value, and AccessTokenV2 exchanges the callback code and registers the resulting token into the session (register_session) without verifying that the callback corresponds to an authorization request this session initiated. Any application that uses this middleware for OAuth 2.0 login is exposed to login cross-site request forgery: because the callback is not bound to the session that began the flow, an attacker who starts an authorization with their own provider account can deliver the resulting callback to a victim, causing the victim's session to complete the attacker's authorization and associating the attacker's provider identity and access token with that session. Where the application persists this as an account link, the attacker may retain access to the victim's account through their own provider credentials.
Quoted source text, attributed separately from HOL analysis.