How severe is CVE-2026-3911?

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

Is CVE-2026-3911 being actively exploited?

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

What products are affected by CVE-2026-3911?

CVE-2026-3911 primarily affects Redhat Build Of Keycloak. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-3911?

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

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

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

When was CVE-2026-3911 published?

CVE-2026-3911 was published on 2026-03-11 and last updated on 2026-06-17.

CVE-2026-3911

CVE-2026-3911 is a low-severity vulnerability in Redhat Build Of Keycloak with a CVSS 3.x base score of 2.7. 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-359.

Key facts

Severity: Low (CVSS 3.x base score 2.7)
EPSS exploit prediction: 0% (25th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-11107
Weakness: CWE-359
Affected product: Redhat Build Of Keycloak
Published: 2026-03-11
Last modified: 2026-06-17

Description

A flaw was found in Keycloak. An authenticated user with the view-users role could exploit a vulnerability in the UserResource component. By accessing a specific administrative endpoint, this user could improperly retrieve user attributes that were configured to be hidden. This unauthorized information disclosure could expose sensitive user data.

Frequently asked questions

What is CVE-2026-3911?: A flaw was found in Keycloak. An authenticated user with the view-users role could exploit a vulnerability in the UserResource component. By accessing a specific administrative endpoint, this user could improperly retrieve user attributes that were configured to be hidden. This unauthorized information disclosure could expose sensitive user data.
How severe is CVE-2026-3911?: CVE-2026-3911 has a CVSS 3.x base score of 2.7, rated low severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2026-3911 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (25th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-3911?: CVE-2026-3911 primarily affects Redhat Build Of Keycloak. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-3911?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-3911 have an EU (EUVD) identifier?: Yes. CVE-2026-3911 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-11107.
When was CVE-2026-3911 published?: CVE-2026-3911 was published on 2026-03-11 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:text-only:*:*:*
cpe:2.3:a:redhat:build_of_keycloak:26.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:build_of_keycloak:26.4.11:*:*:*:*:*:*:*

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-359 vulnerabilities

CVE-2022-0482 — Critical (CVSS 9.1): Exposure of Private Personal Information to an Unauthorized Actor in GitHub repository alextselegidis/easyappointments…
CVE-2022-2921 — High (CVSS 8.8): Exposure of Private Personal Information to an Unauthorized Actor in GitHub repository notrinos/notrinoserp prior to…
CVE-2025-53625 — High (CVSS 8.7): The DynamicPageList3 extension is a reporting tool for MediaWiki, listing category members and intersections with…
CVE-2025-13008 — High (CVSS 8.6): An information disclosure vulnerability in M-Files Server before versions 25.12.15491.7, 25.8 LTS SR3, 25.2 LTS SR3 and…
CVE-2023-36052 — High (CVSS 8.6): Azure CLI REST Command Information Disclosure Vulnerability
CVE-2024-26192 — High (CVSS 8.2): Microsoft Edge (Chromium-based) Information Disclosure Vulnerability

Browse all CWE-359 vulnerabilities →