# Improper Restriction of XML External Entity Reference in Liquibase

Advisory record · `GHSA-jvfv-hrrc-6q72`

- **Identifiers:** `GHSA-jvfv-hrrc-6q72` · `CVE-2022-0839`
- **State:** Confirmed
- **Severity:** CVSS 7.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-611](https://cwe.mitre.org/data/definitions/611.html)
- **Tags:** [XML external entities (XXE)](https://agentprime.io/advisories/tag/xxe.md)
- **Published:** 5 Mar 2022
- **Updated:** 3 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Mar 2022, 00:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.liquibase:liquibase-core` (Maven): affected `<4.8.0`; fixed in `4.8.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Liquibase (org.liquibase:liquibase-core) versions before 4.8.0 are affected by an XML external entity reference issue in the XMLChangeLogSAXParser function. The source gives few details about the attack conditions or impact. Upgrade liquibase-core to version 4.8.0 or later.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.3 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`, from CNA (@huntrdev)

- **CISA KEV:** Not listed.
- **EPSS:** 0.030, the 87th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jvfv-hrrc-6q72)

## Sources

- [GitHub Advisory Database: GHSA-jvfv-hrrc-6q72](https://github.com/advisories/GHSA-jvfv-hrrc-6q72)
- [OSV: GHSA-jvfv-hrrc-6q72](https://osv.dev/vulnerability/GHSA-jvfv-hrrc-6q72)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-0839>
- <https://github.com/liquibase/liquibase/commit/33d9d925082097fb1a3d2fc8e44423d964cd9381>
- <https://github.com/liquibase/liquibase>
- <https://huntr.dev/bounties/f1ae5779-b406-4594-a8a3-d089c68d6e70>
- <https://www.oracle.com/security-alerts/cpujul2022.html>
- <http://seclists.org/fulldisclosure/2025/Apr/14>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jvfv-hrrc-6q72>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jvfv-hrrc-6q72/>. Everything for agents: <https://agentprime.io/llms.txt>.