{}

{}

{}

{"acknowledgement": "Upstream acknowledges Grzegorz Grasza (Red Hat) and Tim Shephard (roiai.ca) as the original reporters.", "bugzilla": {"description": "keystone: keystone: Application credential tokens can escape project scope via token-method reauthentication", "id": "2517802", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2517802"}, "csaw": false, "cvss3": {"cvss3_base_score": "7.1", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N", "status": "draft"}, "cwe": "CWE-863", "details": ["A flaw was found in OpenStack Keystone where an application credential token can escape its intended project scope through token-method reauthentication. Keystone rejects an explicit scope change for an application credential token, but an omitted scope falls through to the owner's default project. If the owner has roles on that default project, Keystone issues a new token scoped there while still carrying the original application credential identity. Custom Keystone authentication plugins are subject to the same incomplete rescope guard. This allows a limited-scope application credential for one project to access another project within the owner's role assignments."], "mitigation": {"lang": "en:us", "value": "Set the following in keystone.conf to prevent exchanging a scoped token for a token with a different project scope:\n[token]\nallow_rescope_scoped_token = False\nThis blocks the application-credential default-project fallback. It also prevents Horizon project switching for users who authenticate with a scoped token. This setting does not disable application credentials themselves."}, "name": "CVE-2026-2035366", "package_state": [{"cpe": "cpe:/a:redhat:openstack:16.2", "fix_state": "Not affected", "package_name": "openstack-keystone", "product_name": "Red Hat OpenStack Platform 16.2"}, {"cpe": "cpe:/a:redhat:openstack:17.1", "fix_state": "Not affected", "package_name": "openstack-keystone", "product_name": "Red Hat OpenStack Platform 17.1"}, {"cpe": "cpe:/a:redhat:openstack:18.0", "fix_state": "Not affected", "package_name": "openstack-keystone", "product_name": "Red Hat OpenStack Platform 18.0"}], "public_date": "2026-08-25T15:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-2035366\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-2035366\nhttps://launchpad.net/bugs/2158538\nhttps://review.opendev.org/c/openstack/keystone/+/1002302"], "statement": "This vulnerability is rated as Important because an authenticated user with an application credential can escape the credential's project binding through token reauthentication and access the owner's default project. Custom Keystone authentication plugins can be affected in the same way. Exploitation requires a valid application credential and a different default project where the owner also has roles. Application credential reauthentication only becomes practically exploitable from Keystone 27.0.1 on the 27.x stable line, and from 28.0.0 on the 28.x line. On earlier versions, exchanging an application credential token fails before a new token is issued. Red Hat OpenStack Platform 16.2, 17.1, and 18.0 (including RHOSO) ship openstack-keystone versions below 27.0.1 and are not affected. A separately identified weakness in EC2 credential reauthentication is outside the scope of this CVE and is being documented by upstream as residual exposure. Client libraries such as python-keystoneclient, python-keystoneauth1, and python-keystonemiddleware do not contain the vulnerable Keystone server code and are not affected.", "threat_severity": "Important"}

{"created": "2026-08-26T01:45:03.409657+00:00", "updated": "2026-08-26T01:45:03.409664+00:00", "vendors": []}