# CVE-2026-37980: Keycloak: Arbitrary code execution via Stored Cross-Site Scripting (XSS) in organization selection login page

> An attacker with admin privileges can inject malicious scripts into the login page, leading to arbitrary code execution and session theft for users.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Apr 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-m32f-8vh9-2hh3, MINI-fmmx-w8vq-95cm, MINI-pq7g-jxv4-r2cf

## What is CVE-2026-37980?

CVE-2026-37980 is a medium-severity cross-site scripting vulnerability in Redhat Build of Keycloak, published on 14 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A flaw was found in Keycloak, specifically in the organization selection login page. A remote attacker with `manage-realm` or `manage-organizations` administrative privileges can exploit a Stored Cross-Site Scripting (XSS) vulnerability. This flaw occurs because the `organization.alias` is placed into an inline JavaScript `onclick` handler, allowing a crafted JavaScript payload to execute in a user's browser when they view the login page. Successful exploitation enables arbitrary JavaScript execution, potentially leading to session theft, unauthorized account actions, or further attacks against users of the affected realm.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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 to 26.5.5 | None |
| `org.keycloak:keycloak-services` | Maven | All versions to 26.5.5 | None |

Products: Redhat Build of Keycloak.

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

Apply the vendor's patch.

## Is CVE-2026-37980 being exploited?

There is no known exploitation of CVE-2026-37980 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-37980 and fix it if it is affected.

What it is: CVE-2026-37980 is a medium-severity cross-site scripting vulnerability in Redhat Build of Keycloak, published on 14 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-37980 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.5; no fix listed
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.5; no fix listed

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

## Sources

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

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