How severe is CVE-2022-2668?

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

Is CVE-2022-2668 being actively exploited?

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

What products are affected by CVE-2022-2668?

CVE-2022-2668 primarily affects Redhat Keycloak. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2022-2668?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-2668 published?

CVE-2022-2668 was published on 2022-08-05 and last updated on 2026-06-17.

CVE-2022-2668

CVE-2022-2668 is a high-severity vulnerability in Redhat Keycloak with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.2)
EPSS exploit prediction: 1% (53rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Redhat Keycloak
Published: 2022-08-05
Last modified: 2026-06-17

Description

An issue was discovered in Keycloak that allows arbitrary Javascript to be uploaded for the SAML protocol mapper even if the UPLOAD_SCRIPTS feature is disabled

Frequently asked questions

What is CVE-2022-2668?: An issue was discovered in Keycloak that allows arbitrary Javascript to be uploaded for the SAML protocol mapper even if the UPLOAD_SCRIPTS feature is disabled
How severe is CVE-2022-2668?: CVE-2022-2668 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-2668 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-2668?: CVE-2022-2668 primarily affects Redhat Keycloak. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2022-2668?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-2668 published?: CVE-2022-2668 was published on 2022-08-05 and last updated on 2026-06-17.

References

https://access.redhat.com/security/cve/CVE-2022-2668

Affected products (2)

cpe:2.3:a:redhat:keycloak:18.0.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:single_sign-on:7.0:*:*:*:*:*:*:*

More vulnerabilities in Redhat Keycloak

CVE-2022-4361 — Critical (CVSS 10.0): Keycloak, an open-source identity and access management solution, has a cross-site scripting (XSS) vulnerability in the…
CVE-2022-1245 — Critical (CVSS 9.8): A privilege escalation flaw was found in the token exchange feature of keycloak. Missing authorization allows a client…
CVE-2019-14910 — Critical (CVSS 9.8): A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used…
CVE-2021-20195 — Critical (CVSS 9.6): A flaw was found in keycloak in versions before 13.0.0. A Self Stored XSS attack vector escalating to a complete…
CVE-2022-3782 — Critical (CVSS 9.1): keycloak: path traversal via double URL encoding. A flaw was found in Keycloak, where it does not properly validate…
CVE-2019-14837 — Critical (CVSS 9.1): A flaw was found in keycloack before version 8.0.0. The owner of 'placeholder.org' domain can setup mail server on this…

All CVEs affecting Redhat Keycloak →