CVE-2026-12740

HIGHPre-NVD 8.1Trending — 4 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
0.0(none)
EPSS
3.0%
KEV
Not listed

Published

July 4, 2026

Last Modified

July 6, 2026

Advisory Details (3)

Auto-updated Jul 6, 2026
No patch confirmed yet. Sources: github_pr.
generic

RFC 6749 - The OAuth 2.0 Authorization Framework

https://datatracker.ietf.org/doc/html/rfc6749#section-10.12
github_pr

Add support for OAuth2 state to fix CVE-2026-12740

Upstream fix in progress (PR #13 · c9s/Plack-Middleware-OAuth, state=open)

https://github.com/c9s/Plack-Middleware-OAuth/pull/13

Vendor Advisories for CVE-2026-12740(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 14:21 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-04 20:28 UTCNVD update
  5. 2026-07-04 19:36 UTCMITRE cvelistV5
  6. 2026-07-04 18:28 UTCNVD update
  7. 2026-07-04 18:18 UTCEG score recompute
  8. 2026-07-04 18:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-12740?
CVE-2026-12740 is a high vulnerability published on July 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…
When was CVE-2026-12740 disclosed?
CVE-2026-12740 was first published in the National Vulnerability Database on July 4, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12740 actively exploited?
CVE-2026-12740 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12740?
CVE-2026-12740 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 0.0.
How do I remediate CVE-2026-12740?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12740, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-12740

Explore →

Is Your Infrastructure Affected by CVE-2026-12740?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.