Skip to main content
VulnerabilityPublished Updated

CVE-2026-7500: Red Hat build of Keycloak 26.4 · Forced Browsing

Affects Red Hat build of Keycloak 26.4Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat build of Keycloak 26.4Affected–Fixed in–
Red HatRed Hat build of Keycloak 26.4Affected–Fixed in–
Red HatRed Hat build of Keycloak 26.4.13Affected–Fixed in–
Red HatRed Hat build of Keycloak 26.6Affected–Fixed in–
Red HatRed Hat build of Keycloak 26.6Affected–Fixed in–
Red HatRed Hat build of Keycloak 26.6.3Affected–Fixed in–

AI-suggested

Red Hat has released updated Red Hat build of Keycloak 26.6.3 images that address this and other vulnerabilities. Users should upgrade to these newer versions to mitigate the issue. Before applying updates, back up existing installations including configurations and databases. Since no separate patch specifically for CVE-2026-7500 is listed, upgrading to the latest fixed version is the recommended remediation. Monitor Red Hat advisories for any further updates or patches. No vendor advisory states that no action is required or that the issue is already mitigated without upgrade.

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.

References

Community reviews

Loading reviews…