How severe is CVE-2026-33551?

CVE-2026-33551 has a CVSS score of 3.5/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-33551?

CVE-2026-33551 affects the following packages: keystone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-33551?

Update keystone to 26.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33551 is resolved across your whole dependency graph.

How do I detect CVE-2026-33551 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-33551 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-33551 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-33551 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-33551?

CVE-2026-33551 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-33551?

CVE-2026-33551 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-33551 published, and has it been updated?

CVE-2026-33551 was published on April 10, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

LOW severity

CVE-2026-33551 — keystone

LOW

CVE-2026-33551 is a low-severity (CVSS 3.5) CWE-863 vulnerability in keystone. A fix is available for keystone — see the affected versions and patch details below.

OpenStack Keystone: Restricted application credentials can create EC2 credentials

Also known asGHSA-4phw-6824-6cfpPYSEC-2026-202

Published

Apr 10, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33551.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍keystone

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in OpenStack Keystone 14 through 26 before 26.1.1, 27.0.0, 28.0.0, and 29.0.0. Restricted application credentials can create EC2 credentials. By using a restricted application credential to call the EC2 credential creation API, an authenticated user with only a reader role may obtain an EC2/S3 credential that carries the full set of the parent user's S3 permissions, effectively bypassing the role restrictions imposed on the application credential. Only deployments that use restricted application credentials in combination with the EC2/S3 compatibility API (swift3 / s3api) are affected.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keystone`	≥ 14.0.0&&< 26.1.1	26.1.1`pip install --upgrade 'keystone==26.1.1'`

Affected Products

1 product · 4 configurations

Application

keystoneopenstack

≥ 14.0.0 && < 26.1.1

3 versions

27.0.028.0.029.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keystone to 26.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33551 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product	Fixed in	Advisory
Red Hat OpenStack Platform 13.0 - ELS	`openstack-keystone-1:13.0.4-10.el7ost`	RHSA-2026:94039
Red Hat OpenStack Platform 16.2	`openstack-keystone-1:16.0.3-2.20260616134936.9d699a7.el8ost`	RHSA-2026:54757
Red Hat OpenStack Platform 17.1 for RHEL 9	`openstack-keystone-1:19.0.2-17.1.20260529190847.54dd95d.el9ost`	RHSA-2026:28044
Red Hat OpenStack Services on OpenShift 18.0	`openstack-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost`	RHSA-2026:39808

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-33551 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N

CWE Classification

CWE-863CWE-863

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Apr 10, 2026

Last updated

Oct 28, 2026

Identifiers

CVE-2026-33551

GHSA-4phw-6824-6cfp

PYSEC-2026-202

References

Advisorygithub.com · CVE 2026 33551.json Advisorynvd.nist.gov · CVE 2026 33551 Webopenwall.com Webbugs.launchpad.net Websecurity.openstack.org · OSSA 2026 005 Webgithub.com · PYSEC 2026 202.yaml Packagegithub.com · keystone

Related vulnerabilities

This CVE is low severity; 8 of 8 other CVEs affecting keystone are rated as high or higher (top: critical).

CVE-2026-42999CVE-2026-42998CVE-2026-43000CVE-2026-44394CVE-2026-43001CVE-2026-40683CVE-2025-65073CVE-2021-3563

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2026-33551 — keystone

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2026-33551 in your dependencies?