Loading story…
OpenStack disclosed CVE-2026-80182 and CVE-2026-80184 in Keystone, in which delegated tokens obtained through OAuth1 access tokens, application credentials, or trusts are subject to inconsistent scope enforcement. An attacker able to use such a token could create persistent credentials or further delegations that outlive the original delegated credential. Token-method reauthentication could also bypass intended project restrictions; in an application-credential case, an unscoped token could receive a token for the credential owner’s default project rather than the initially authorized project.
The flaws affect Keystone versions >=13.0.0 and earlier than 27.0.3, 28.0.3, or 29.0.3, in deployments that permit the affected delegated-authentication mechanisms. OpenStack released interdependent fixes for the 2025.1, 2025.2, 2026.1, and 2026.2 branches; all associated patch sets must be applied together. Administrators using custom or third-party authentication plugins must also add them to the new configuration option introduced by the update to prevent authentication failures.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
OpenStack provided interdependent patch sets for the 2025.1, 2025.2, 2026.1, and development 2026.2 Keystone branches; both patches must be applied together. The fixes add an authentication-method configuration requirement for custom or third-party plugins, which must be listed in [auth] additional_primary_auth_methods to avoid failed authentication flows.
OpenStack issued OSSA-2026-037 for two Keystone flaws in delegated-token scope enforcement, assigned CVE-2026-80182 and CVE-2026-80184. The issues could let delegated tokens create persistent credentials or further delegations, and could allow token reauthentication to escape an intended project boundary in an application-credential scenario.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
seclists.org
Open sourceseclists.org
Open sourcelaunchpad.net
Open sourcelaunchpad.net
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Multiple vendors issued fixes for **high-impact vulnerabilities** that could enable privilege escalation, tenant-wide compromise, security feature bypass, or remote code execution. OpenStack patched **CVE-2026-22797** in *keystonemiddleware* affecting deployments using `external_oauth2_token`, where failure to sanitize incoming identity headers allows authenticated users to forge headers (e.g., `X-Is-Admin-Project`, `X-Roles`, `X-User-Id`) to **escalate privileges or impersonate other users**; fixes were released across supported branches and the issue was reported by a Red Hat researcher. Microsoft patched **CVE-2026-20965** in *Windows Admin Center*’s Azure SSO (fixed in Azure Extension **v0.70.00**), where improper token validation could let an attacker with local admin on a WAC-enabled Azure VM/Arc machine combine a stolen `WAC.CheckAccess` token with a forged PoP token to enable **lateral movement and tenant-wide access** under certain conditions. Separately, Microsoft addressed **CVE-2026-20824** in *Windows Remote Assistance*, an **Important** security feature bypass that can allow attackers to evade **Mark of the Web (MOTW)** protections via social engineering. Progress Software also released patches for **CVE-2025-13444** and **CVE-2025-13447** (CVSS 8.4) affecting *LoadMaster* and *MOVEit WAF*, where crafted UI/API requests can trigger **command injection leading to remote code execution**; the vendor stated it had no evidence of in-the-wild exploitation at the time of release.
Jun 29, 2026
Keycloak disclosed and patched a high-severity privilege escalation flaw, **CVE-2026-9795**, in its Fine-Grained Admin Permissions v2 (`FGAPv2`) feature after researchers reported that a delegated administrator could bypass missing authorization checks in the admin REST API and add arbitrary realm roles to a client’s scope mapping. That weakness allowed limited administrators to inject elevated roles such as `realm-admin` into tokens later issued to users authenticating through the affected client, creating a path to downstream privilege escalation in deployments running Keycloak `26.2.0` and later with `FGAPv2` enabled. The issue was later listed as fixed in Keycloak release `26.6.4`, alongside several other security bugs including **CVE-2026-9099**, **CVE-2026-9083**, **CVE-2026-9086**, **CVE-2026-9705**, **CVE-2026-9799**, **CVE-2026-9800**, and **CVE-2026-11800**. Red Hat also shipped security updates for its Keycloak `26.4.11` images and operator on OpenShift, addressing a broad set of vulnerabilities across the Admin REST API, Account REST API, OIDC dynamic client registration, UMA authorization, token handling, redirect validation, and scope processing, with impacts ranging from information disclosure and SSRF to account takeover, policy bypass, and denial of service.
Jul 12, 2026
OpenStack disclosed **OSSA-2026-036** for two authorization flaws in **Aodh** and **Watcher**, later tracked as **`CVE-2026-76878`** with a **CVSS 4.0 score of 8.4**. In Aodh, versions before **22.0.1** improperly enforced project scope in the alarm listing API, allowing a non-admin user with only the **reader** role to enumerate alarms from other projects by supplying the `all_projects` parameter with a false value. The exposure can reveal alarm metadata including webhook URLs, Heat signal endpoints, project IDs, and user IDs, and can be further narrowed by providing a foreign `project_id`. In Watcher, the webhook trigger endpoint lacked authorization checks, allowing any authenticated user who knows an audit webhook URL to start an **EVENT** audit and its associated action plan regardless of project or role. The advisory said affected Watcher deployments have carried the missing policy enforcement since the **Ussuri** release line, identified as **Watcher 4.0.0**, and that patches were issued across multiple OpenStack branches. The issues were reported by **Chen YuXiang** of the Institute of Computing Technology, Chinese Academy of Sciences.
Aug 21, 2026