# CVE-2019-10219: The SafeHtml annotation in Hibernate-Validator does not properly guard against XSS attacks

> Attackers can execute arbitrary scripts via unsanitized HTML comments in Hibernate Validator, requiring library upgrades to mitigate XSS risks.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2019
- **Updated:** 8 Oct 2026
- **Also known as:** CLSA-2026-1778028250, CLSA-2026-1789376980, DEBIAN-CVE-2019-10219, GHSA-m8p2-495h-ccmh, OESA-2021-1332, UBUNTU-CVE-2019-10219

## What is CVE-2019-10219?

CVE-2019-10219 is a medium-severity cross-site scripting vulnerability in Netapp Active Iq Unified Manager, published on 8 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2019-10219?

8 open source packages ship an affected version, including org.hibernate.validator:hibernate-validator and org.hibernate:hibernate-validator. It affects 187 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.hibernate.validator:hibernate-validator` | Maven | From 6.0.0.Alpha1 | 6.0.18.Final |
| `org.hibernate.validator:hibernate-validator` | Maven | From 6.0.0.Alpha1 | 6.0.18.Final |
| `org.hibernate.validator:hibernate-validator` | Maven | From 6.1.0.Alpha1 | 6.1.0.Alpha6 |
| `org.hibernate.validator:hibernate-validator` | Maven | From 6.1.0.Alpha1 | 6.1.0.Alpha6 |
| `org.hibernate:hibernate-validator` | Maven | From 6.0.0.Alpha1 | 6.0.18.Final |
| `org.hibernate:hibernate-validator` | Maven | From 6.0.0.Alpha1 | 6.0.18.Final |
| `org.hibernate:hibernate-validator` | Maven | From 6.1.0.Alpha1 | 6.1.0.Alpha6 |
| `org.hibernate:hibernate-validator` | Maven | From 6.1.0.Alpha1 | 6.1.0.Alpha6 |

Products: Netapp Active Iq Unified Manager, Netapp Element, Netapp Management Services for Element Software and Netapp Hci, Netapp Snapcenter Plug-In, Oracle Access Manager, Oracle Agile Engineering Data Management, Oracle Agile Product Lifecycle Analytics, Oracle Agile Product Lifecycle Management, Oracle Agile Product Lifecycle Management Integration Pack, Oracle Airlines Data Model, Oracle Application Express, Oracle Application Performance Management, Oracle Application Testing Suite, Oracle Argus Analytics, Oracle Argus Insight, Oracle Argus Safety, Oracle Banking Apis, Oracle Banking Deposits and Lines of Credit Servicing, Oracle Banking Digital Experience, Oracle Banking Enterprise Default Management and 167 more.

## How do I fix CVE-2019-10219?

Upgrade org.hibernate.validator:hibernate-validator to a fixed version for your release line: 6.0.18.Final or 6.1.0.Alpha6.

## Is CVE-2019-10219 being exploited?

There is no known exploitation of CVE-2019-10219 in the wild and no public exploit code.

Public exploit code:

- https://github.com/shoucheng3/hibernate__hibernate-validator_CVE-2019-10219_6-0-17-Final (github_poc): https://github.com/shoucheng3/hibernate__hibernate-validator_CVE-2019-10219_6-0-17-Final
- https://github.com/shoucheng3/hibernate__hibernate-validator_CVE-2019-10219_6_0_18_Final_fixed (github_poc): https://github.com/shoucheng3/hibernate__hibernate-validator_CVE-2019-10219_6_0_18_Final_fixed

## Other vulnerabilities in Netapp Active Iq Unified Manager

- [CVE-2022-31692](https://insights.sbomify.com/CVE-2022-31692/): Spring Security authorization rules can be bypassed via forward or include dispatcher types (critical 9.8)
- [CVE-2022-2526](https://insights.sbomify.com/CVE-2022-2526/): Use after free in systemd-resolved (critical 9.8)
- [CVE-2022-22978](https://insights.sbomify.com/CVE-2022-22978/): Authorization bypass in Spring Security (critical 9.8)
- [CVE-2021-22931](https://insights.sbomify.com/CVE-2021-22931/): Code injection in Node (critical 9.8)
- [CVE-2018-2938](https://insights.sbomify.com/CVE-2018-2938/): Code injection in Java (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10219 and fix it if it is affected.

What it is: CVE-2019-10219 is a medium-severity cross-site scripting vulnerability in Netapp Active Iq Unified Manager, published on 8 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10219 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.hibernate.validator:hibernate-validator (Maven): affected from 6.0.0.Alpha1; fixed in 6.0.18.Final
- org.hibernate.validator:hibernate-validator (Maven): affected from 6.0.0.Alpha1; fixed in 6.0.18.Final
- org.hibernate.validator:hibernate-validator (Maven): affected from 6.1.0.Alpha1; fixed in 6.1.0.Alpha6
- org.hibernate.validator:hibernate-validator (Maven): affected from 6.1.0.Alpha1; fixed in 6.1.0.Alpha6
- org.hibernate:hibernate-validator (Maven): affected from 6.0.0.Alpha1; fixed in 6.0.18.Final
- org.hibernate:hibernate-validator (Maven): affected from 6.0.0.Alpha1; fixed in 6.0.18.Final
- org.hibernate:hibernate-validator (Maven): affected from 6.1.0.Alpha1; fixed in 6.1.0.Alpha6
- org.hibernate:hibernate-validator (Maven): affected from 6.1.0.Alpha1; fixed in 6.1.0.Alpha6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-10219/ (Markdown: https://insights.sbomify.com/CVE-2019-10219/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10219
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10219
- OSV: https://osv.dev/vulnerability/CVE-2019-10219

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-10219/
Summaries are generated and may contain mistakes; the official description above is the record.