# CVE-2026-96446: Keycloak-services: keycloak-services: par single-use bypass via prompt=none silent authentication path

> Attackers can bypass single-use restrictions on Pushed Authorization Requests via silent authentication, potentially obtaining multiple authorization codes for logged-in users.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-j24v-wv3r-fjch

## What is CVE-2026-96446?

CVE-2026-96446 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the Pushed Authorization Request PAR implementation of Keycloak. The issue occurs when the silent authentication path prompt=none is used, which allows the authorization process to skip certain steps if a user is already logged in. Due to this bypass, the security rule that ensures a pushed request URI is used only once is not enforced. An attacker could potentially reuse a request URI to obtain multiple authorization codes for a user who is already signed in, violating security standards like FAPI-2.

Weakness: CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-96446 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-96446 being exploited?

There is no known exploitation of CVE-2026-96446 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96446 is a medium-severity vulnerability in Red Hat Build of Keycloak, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96446 in the wild and no public exploit code.

Affected product: Red Hat Build of Keycloak. 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-96446/ (Markdown: https://insights.sbomify.com/CVE-2026-96446/index.md)
```

## Sources

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

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