{}

{}

{}

{"acknowledgement": "Upstream acknowledges Nassim Abbaoui (OVHcloud) as the original reporter.", "bugzilla": {"description": "keystonemiddleware: keystonemiddleware: application credential access_rules bypass via X-Service-Token header presence check", "id": "2559580", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2559580"}, "csaw": false, "cvss3": {"cvss3_base_score": "6.3", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L", "status": "draft"}, "cwe": "CWE-863", "details": ["A flaw was found in OpenStack keystonemiddleware and Keystone. The code incorrectly treats the presence of the X-Service-Token HTTP header as sufficient to skip enforcement of application credential access rules (and can skip related token-binding checks). An attacker who holds an application credential with access_rules can bypass those restrictions by sending any non-empty X-Service-Token value; a valid service token is not required for this bypass when delay_auth_decision is enabled (typical). This allows API calls beyond what the credential was designed to permit within the attacker's existing roles. Only installing fixed keystonemiddleware and Keystone packages remediates the issue."], "mitigation": {"lang": "en:us", "value": "No mitigation is currently available that meets Red Hat Product Security standards for a complete fix."}, "name": "CVE-2026-115642", "package_state": [{"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Affected", "package_name": "openshift4/ose-ironic-rhel9", "product_name": "Red Hat OpenShift Container Platform 4"}, {"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Affected", "package_name": "python-keystonemiddleware", "product_name": "Red Hat OpenShift Container Platform 4"}, {"cpe": "cpe:/a:redhat:openshift:5", "fix_state": "Affected", "package_name": "openshift5/ose-ironic-rhel9", "product_name": "Red Hat OpenShift Container Platform 5"}, {"cpe": "cpe:/a:redhat:openstack:13", "fix_state": "Affected", "package_name": "python-keystonemiddleware", "product_name": "Red Hat OpenStack Platform 13 (Queens)"}, {"cpe": "cpe:/a:redhat:openstack:16.2", "fix_state": "Affected", "package_name": "python-keystonemiddleware", "product_name": "Red Hat OpenStack Platform 16.2"}, {"cpe": "cpe:/a:redhat:openstack:17.1", "fix_state": "Affected", "package_name": "python-keystonemiddleware", "product_name": "Red Hat OpenStack Platform 17.1"}, {"cpe": "cpe:/a:redhat:openstack:18.0", "fix_state": "Affected", "package_name": "python-keystonemiddleware", "product_name": "Red Hat OpenStack Platform 18.0"}], "public_date": "2026-10-29T15:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-115642\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-115642\nhttps://launchpad.net/bugs/2162748"], "statement": "Red Hat OpenStack Platform and Red Hat OpenShift ship python-keystonemiddleware and openstack-keystone in multiple streams. The same access_rules bypass (header presence of X-Service-Token rather than validated service token) exists in keystonemiddleware auth_token middleware and in Keystone's own API code path; both require fixes. Any project member who can create an application credential with access_rules can bypass those rules by sending any non-empty X-Service-Token value on API requests when the service uses delay_auth_decision (common). There is no supported configuration-only workaround; apply upstream patches for keystonemiddleware and Keystone. Keystone may disclose separately from the 2026-10-29 keystonemiddleware coordinated release.", "threat_severity": "Important"}

{}