CVE-2026-7500 Keycloak has a Forced Browsing issue

Medium 5.4 Published Updated

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

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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

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.

PackageAffectedFixed in
org.keycloak:keycloak-services MavenAll versions to 26.6.1None
org.keycloak:keycloak-services MavenAll versions to 26.6.1None

Products include Redhat Build of Keycloak.

How do I fix CVE-2026-7500?

Apply the vendor's patch.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-7500 being exploited?

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

All Redhat Build of Keycloak vulnerabilities

Sources

Also known as ECHO-69cc-b026-014f, GHSA-hm32-hfmw-rhvg, MINI-4wph-75wx-fjpq, MINI-8rg5-9gr6-p585.

Is CVE-2026-7500 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free