How severe is CVE-2022-0225?

No CVSS score has been assigned to CVE-2022-0225 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-0225?

CVE-2022-0225 affects the following packages: org.keycloak:keycloak-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-0225?

Update org.keycloak:keycloak-core to 20.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0225 is resolved across your whole dependency graph.

How do I detect CVE-2022-0225 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-0225 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2022-0225?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-0225 can be triaged on real exposure rather than presence alone.

Is CVE-2022-0225 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-0225, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-0225?

CVE-2022-0225 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-0225?

CVE-2022-0225 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-0225 published, and has it been updated?

CVE-2022-0225 was published on August 26, 2022 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2022-0225 — keycloak-core

CVE-2022-0225 is a Cross-site Scripting (XSS) vulnerability in org.keycloak:keycloak-core. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.keycloak:keycloak-core — see the affected versions and patch details below.

Stored Cross-Site Scripting (XSS) in Keycloak via groups dropdown

Also known asGHSA-755v-r4x4-qf7m GHSA-fqc7-5xxc-ph7r

Published

Aug 26, 2022

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕org.keycloak:keycloak-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Keycloak. This flaw allows a privileged attacker to use the malicious payload as the group name while creating a new group from the admin console, leading to a stored Cross-site scripting (XSS) attack.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.keycloak:keycloak-core`	all versions	20.0.0`org.keycloak:keycloak-core:20.0.0`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A flaw was found in Keycloak. This flaw allows a privileged attacker to …

bugzilla.redhat.comNVDSep 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-core to 20.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0225 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-0225 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2022-0225. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Single Sign-On 7	`rh-sso7-keycloak`	RHSA-2022:6787
Red Hat Single Sign-On 7.5 for RHEL 7	`rh-sso7-keycloak-0:15.0.8-1.redhat_00001.1.el7sso`	RHSA-2022:6782
Red Hat Single Sign-On 7.5 for RHEL 8	`rh-sso7-keycloak-0:15.0.8-1.redhat_00001.1.el8sso`	RHSA-2022:6783
Red Hat Single Sign-On 7.6.1	`rh-sso7-keycloak`	RHSA-2022:7417
Red Hat Single Sign-On 7.6 for RHEL 7	`rh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el7sso`	RHSA-2022:7409
Red Hat Single Sign-On 7.6 for RHEL 8	`rh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el8sso`	RHSA-2022:7410
Red Hat Single Sign-On 7.6 for RHEL 9	`rh-sso7-0:1-5.el9sso`	RHSA-2022:7411

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-0225 in your dependencies?

O3 Security finds CVE-2022-0225 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works