Skip to main content
Mallory
UnratedVulnerability

CVE-2026-122058: Consumer configuration access bypass in Drupal Simple OAuth & OpenID Connect

Updated 18 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-122058CWE-863

A critical authorization vulnerability in the Drupal Simple OAuth (OAuth2) & OpenID Connect module allows users with consumer creation or editing permissions to configure malicious OAuth consumers. Insufficient restrictions on consumer access settings can enable these users to obtain tokens with elevated privileges and impersonate another user, potentially including an administrator.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise site confidentiality and integrity through user impersonation and privilege escalation. Depending on the privileges associated with the obtained tokens, an attacker may gain full administrative access.

Mitigation

If you can’t patch tonight, do this now.

Restrict the Add consumer entities and Update own consumer entities permissions to trusted roles. Review existing consumers for unsafe access settings and revoke their tokens when their trustworthiness is uncertain.

Remediation

Patch, then assume compromise.

Upgrade 5.2.x installations to 5.2.6, 6.0.x installations to 6.0.10, and 6.1.x installations to 6.1.4. After updating, grant the new Administer consumer access settings permission only to trusted roles. Review existing consumers because the update does not modify their configurations, and revoke associated tokens if their trustworthiness is uncertain. In the fixed 6.1.x release, Client Credentials tokens are always limited to their scopes.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-122058 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-122058 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-122058?
As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-122058.
Is there a patch for CVE-2026-122058?
Upgrade 5.2.x installations to 5.2.6, 6.0.x installations to 6.0.10, and 6.1.x installations to 6.1.4. After updating, grant the new Administer consumer access settings permission only to trusted roles.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.