# CVE-2026-8830: Keycloak: Policy bypass during WebAuthn credential registration via client-side JavaScript manipulation

> Authenticated users can bypass WebAuthn security policies by manipulating client-side JavaScript, allowing non-compliant credential registration.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** Yes
- **Published:** 19 May 2026
- **Updated:** 26 Jun 2026
- **Also known as:** ECHO-6007-5dc2-524b, GHSA-g8vr-x4qh-25qg, MINI-4953-529j-crv9, MINI-fm86-vx82-x4fh

## What is CVE-2026-8830?

CVE-2026-8830 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in Keycloak. An authenticated user can bypass configured WebAuthn policies during credential registration by manipulating client-side JavaScript. This occurs because the server-side processAction() fails to validate that the newly created credential's parameters, such as public key algorithms, match the realm's configured WebAuthn policies. This could lead to the creation of credentials that do not adhere to administrative security requirements, potentially weakening the overall security posture of the system by allowing non-compliant authentication methods.

Weakness: CWE-603 (Use of Client-Side Authentication)

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

2 open source packages ship an affected version, including org.keycloak:keycloak-services. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.6.3 |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.6.3 |

Products: Redhat Build of Keycloak.

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

Upgrade org.keycloak:keycloak-services to 26.6.3 or later.

## Is CVE-2026-8830 being exploited?

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

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8)
- [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8)
- [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1)
- [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1)
- [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8830 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 19 May 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-8830 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.6.3
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.6.3

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-8830/ (Markdown: https://insights.sbomify.com/CVE-2026-8830/index.md)
```

## Sources

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

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