How severe is CVE-2026-7500?

CVE-2026-7500 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.

Is CVE-2026-7500 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-7500?

CVE-2026-7500 affects Redhat Build Of Keycloak. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-7500?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-7500 have an EU (EUVD) identifier?

Yes. CVE-2026-7500 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26381.

When was CVE-2026-7500 published?

CVE-2026-7500 was published on 2026-04-30 and last updated on 2026-06-26.

CVE-2026-7500

CVE-2026-7500 is a medium-severity vulnerability in Redhat Build Of Keycloak with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-425.

Key facts

Severity: Medium (CVSS 3.x base score 5.4)
EPSS exploit prediction: 0% (14th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-26381
Weakness: CWE-425
Affected product: Redhat Build Of Keycloak
Published: 2026-04-30
Last modified: 2026-06-26

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.

Frequently asked questions

What is CVE-2026-7500?: 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.
How severe is CVE-2026-7500?: CVE-2026-7500 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2026-7500 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-7500?: CVE-2026-7500 affects Redhat Build Of Keycloak. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-7500?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-7500 have an EU (EUVD) identifier?: Yes. CVE-2026-7500 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26381.
When was CVE-2026-7500 published?: CVE-2026-7500 was published on 2026-04-30 and last updated on 2026-06-26.

References

Affected products (1)

cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:-:*:*:*

More vulnerabilities in Redhat Build Of Keycloak

CVE-2026-3047 — High (CVSS 8.8): A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is…
CVE-2026-11800 — High (CVSS 8.1): A flaw was found in Keycloak. This JWT algorithm confusion vulnerability in the JWT Authorization Grant flow allows an…
CVE-2026-9800 — High (CVSS 8.1): A flaw was found in Keycloak Policy Enforcer. This vulnerability allows any authenticated user to bypass all…
CVE-2026-7504 — High (CVSS 8.1): A flaw was found in Keycloak's URL validation logic during redirect operations. By crafting a malicious request, an…
CVE-2026-4636 — High (CVSS 8.1): A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA)…
CVE-2026-3009 — High (CVSS 8.1): A security flaw in the IdentityBrokerService.performLogin endpoint of Keycloak allows authentication to proceed using…

All CVEs affecting Redhat Build Of Keycloak →

Other CWE-425 vulnerabilities

CVE-2025-26689 — Critical (CVSS 9.8): Direct request ('Forced Browsing') issue exists in CHOCO TEI WATCHER mini (IB-MCT001) all versions. If a remote…
CVE-2024-0204 — Critical (CVSS 9.8): Authentication bypass in Fortra's GoAnywhere MFT prior to 7.4.1 allows an unauthorized user to create an admin user via…
CVE-2022-45276 — Critical (CVSS 9.8): An issue in the /index/user/user_edit.html component of YJCMS v1.0.9 allows unauthenticated attackers to obtain the…
CVE-2022-26279 — Critical (CVSS 9.8): EyouCMS v1.5.5 was discovered to have no access control in the component /data/sqldata.
CVE-2021-36560 — Critical (CVSS 9.8): Phone Shop Sales Managements System using PHP with Source Code 1.0 is vulnerable to authentication bypass which leads…
CVE-2021-36745 — Critical (CVSS 9.8): A vulnerability in Trend Micro ServerProtect for Storage 6.0, ServerProtect for EMC Celerra 5.8, ServerProtect for…

Browse all CWE-425 vulnerabilities →