# CVE-2026-7500: Keycloak has a Forced Browsing issue

> Attackers can access and modify account data via unsecured API endpoints when the account feature is explicitly disabled in Keycloak.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/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:** Yes
- **Published:** 30 Apr 2026
- **Updated:** 26 Jun 2026
- **Also known as:** ECHO-69cc-b026-014f, GHSA-hm32-hfmw-rhvg, MINI-4wph-75wx-fjpq, MINI-8rg5-9gr6-p585

## What is CVE-2026-7500?

CVE-2026-7500 is a medium-severity missing authorization vulnerability in Redhat Build of Keycloak, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

When Keycloak is started with `--features-disabled=account,account-api`, the Account REST API is only partially disabled. Five endpoints under the versioned path `/account/v1alpha1` remain fully functional — including both read and write operations — because they lack the `checkAccountApiEnabled()` gate that correctly blocks four other endpoints in the same REST service class. The user needs to have permissions to use the API.

Weakness: CWE-425 (Direct Request)

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

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

Products: Redhat Build of Keycloak.

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

Apply the vendor's patch.

## Is CVE-2026-7500 being exploited?

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

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

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.6.1; no fix listed
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.6.1; 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-7500/ (Markdown: https://insights.sbomify.com/CVE-2026-7500/index.md)
```

## Sources

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

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