CVE-2022-0839 is a high-severity (CVSS 7.3) XML External Entity (XXE) vulnerability in org.liquibase:liquibase-core. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.liquibase:liquibase-core — see the affected versions and patch details below.
Improper Restriction of XML External Entity Reference in liquibase/liquibase
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-0839 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.liquibase:liquibase-coreReal-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
The XMLChangeLogSAXParser() function in Liquibase prior to version 4.8.0 contains an issue that may lead to to Improper Restriction of XML External Entity Reference.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.liquibase:liquibase-core | all versions | 4.8.0org.liquibase:liquibase-core:4.8.0 |
Affected Products
liquibaseliquibasesqlcloracleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.liquibase:liquibase-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.liquibase:liquibase-core to 4.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0839 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.
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.
The impact to Satellite up to 6.11 is very low, as it does not use custom or external XSD in Candlepin's liquibase changelog files. Satellite 6.12 and later versions are not affected by this flaw.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Single Sign-On 7 | see advisory | RHEA-2022:5463 |
| Red Hat Single Sign-On 7.6 for RHEL 7 | rh-sso7-0:1-4.el7sso | RHBA-2022:5452 |
| Red Hat Single Sign-On 7.6 for RHEL 8 | rh-sso7-0:1-4.el8sso | RHBA-2022:5454 |
Frequently Asked Questions
Is CVE-2022-0839 in your dependencies?
Find it across Maven, including transitive dependencies.