CVE-2019-10219
MEDIUMCVE-2019-10219 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.hibernate.validator:hibernate-validator. O3 Security confirms whether CVE-2019-10219 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
The SafeHtml annotation in Hibernate-Validator does not properly guard against XSS attacks
Blast Radius
org.hibernate.validator:hibernate-validator☕org.hibernate.validator:hibernate-validator☕org.hibernate:hibernate-validator☕org.hibernate:hibernate-validatorReal-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 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.hibernate.validator:hibernate-validator | ≥ 6.1.0.Alpha1&&< 6.1.0.Alpha6 | 6.1.0.Alpha6 |
| ☕Maven | org.hibernate.validator:hibernate-validator | ≥ 6.0.0.Alpha1&&< 6.0.18.Final | 6.0.18.Final |
| ☕Maven | org.hibernate:hibernate-validator | ≥ 6.1.0.Alpha1&&< 6.1.0.Alpha6 | 6.1.0.Alpha6 |
| ☕Maven | org.hibernate:hibernate-validator | ≥ 6.0.0.Alpha1&&< 6.0.18.Final | 6.0.18.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.hibernate.validator:hibernate-validator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.hibernate.validator:hibernate-validator to 6.1.0.Alpha6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10219 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 pinpoints whether CVE-2019-10219 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2019-10219. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-10219 in your dependencies?
O3 detects CVE-2019-10219 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.