Skip to content
VulniPulse
Sign in
Advisory severityHigh8.1Red Hat Linux

High [CVE-2026-2035364] Delegated token scope restrictions not consistently enforced across trust, OAuth1, and application credential endpoints

This high-severity Red Hat Linux advisory covers CVE-2026-2035364; related products: Red Hat OpenStack Platform 16.2, Red Hat OpenStack Platform 17.1, Red Hat OpenStack Platform 18.0.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-2035364 Source published Source updated

VulniPulse record published Record updated

CVE-2026-2035364
Related products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

Delegated token scope restrictions not consistently enforced across trust, OAuth1, and application credential endpoints. Red Hat rates this important (CVSS 8.1).

Weakness: CWE-863.

Affected products named by the advisory: Red Hat OpenStack Platform 16.2; Red Hat OpenStack Platform 17.1; Red Hat OpenStack Platform 18.0.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • There is no complete mitigation for this vulnerability. The following measures can reduce risk: 1. If OAuth1 authentication is not required, remove 'oauth1' from the [auth] methods configuration option in keystone.conf. 2. Restrict access to the Keystone API to trusted networks via firewall rules. 3. Review and rotate application credentials, trusts, and OAuth1 access tokens after a suspected compromise.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.