# CVE-2026-131922: In OpenStack keystonemiddleware before 13.0.3, by supplying a malicious regular expression when creating an application credential (aka AppC


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-131922, GHSA-98hp-mqh6-77pj, UBUNTU-CVE-2026-131922

## What is CVE-2026-131922?

CVE-2026-131922 is a medium-severity vulnerability in OpenStack keystonemiddleware, published on 18 Nov 2026. 

### Official description

In OpenStack keystonemiddleware before 13.0.3, by supplying a malicious regular expression when creating an application credential (aka AppCred) access_rules entry, an authenticated user may consume resources in the consuming process making a service unresponsive.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-131922?


## How do I fix CVE-2026-131922?

Upgrade OpenStack keystonemiddleware to 13.0.3 or later. The advisory says that version fixes it.

## Is CVE-2026-131922 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-131922 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-131922 and fix it if it is affected.

What it is: CVE-2026-131922 is a medium-severity vulnerability in OpenStack keystonemiddleware, published on 18 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-131922 exists.

Affected product: OpenStack keystonemiddleware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-131922/ (Markdown: https://insights.sbomify.com/CVE-2026-131922/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-131922
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-131922
- OSV: https://osv.dev/vulnerability/CVE-2026-131922

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-131922/
Summaries are generated and may contain mistakes; the official description above is the record.
