ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-7500

When Keycloak is started with , the Account REST API is only partially disabled.

Published Apr 30, 2026 · catalog updated Jun 26, 2026 · build of keycloak

Check if you run it

No confirmed exploitation is on record for CVE-2026-7500. EPSS is 0.32%. Act only if a listed version of build of keycloak is installed.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.32%
Remediation
Advisory link
Affected products
cpe redhat/build of keycloak

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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe redhat/build of keycloakversion unspecified

How to fix CVE-2026-7500

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-7500. EPSS is 0.32%. Act only if a listed version of build of keycloak is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-425: Direct Request (Forced Browsing). EPSS 0.32%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 30, 2026 · NIST NVD

    Detected

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

  2. Jun 26, 2026 · NIST NVD

    Updated

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

Sources

  • CVE.orgVulnerability recordCVE-2026-7500

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-7500

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2026-7500

    When Keycloak is started with , the Account REST API is only partially disabled. Five endpoints under the versioned path remain fully functional — including both read and write operations — because they lack the `checkA

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.