NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Improper Input Validation in Hibernate ValidatorGHSA-rmrm-75hp-phr2

MEDIUM

GHSA-rmrm-75hp-phr2 is a medium-severity (CVSS 5.3) Improper Input Validation vulnerability in org.hibernate.validator:hibernate-validator. A fix is available for org.hibernate.validator:hibernate-validator — see the affected versions and patch details below.

Also known asCVE-2020-10693
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk
0.00%1.01%2.02%3.03%0.3%2.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
☕org.hibernate.validator:hibernate-validator☕org.hibernate.validator:hibernate-validator☕org.hibernate:hibernate-validator☕org.hibernate:hibernate-validator

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 Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.hibernate.validator:hibernate-validator≥ 6.1.0.Final&&< 6.1.5.Final6.1.5.Finalorg.hibernate.validator:hibernate-validator:6.1.5.Final
☕Mavenorg.hibernate.validator:hibernate-validatorall versions6.0.20.Finalorg.hibernate.validator:hibernate-validator:6.0.20.Final
☕Mavenorg.hibernate:hibernate-validator≥ 6.1.0.Final&&< 6.1.5.Final6.1.5.Finalorg.hibernate:hibernate-validator:6.1.5.Final
☕Mavenorg.hibernate:hibernate-validatorall versions6.0.20.Finalorg.hibernate:hibernate-validator:6.0.20.Final

Affected Products

7 products · 10 configurations
Application
websphere application serveribm
≥ 17.0.0.3 && ≤ 20.0.0.10
range
Application
weblogic serveroracle
1 version
14.1.1.0.0
Application
quarkusquarkus
≤ 1.4.2
range
Application
hibernate validatorredhat
≥ 6.1.2 && < 6.1.5
1 version
7.0.0
Application
jboss enterprise application platformredhat
2 versions
7.2.07.3.0
Application
satelliteredhat
1 version
6.8

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update org.hibernate.validator:hibernate-validator to 6.1.5.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rmrm-75hp-phr2 is resolved across your whole dependency graph.

  3. 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.

Red HatModerate

hibernate-validator is packaged with Red Hat OpenStack Platform 13.0's OpenDaylight (ODL). However, because ODL is technical preview in this version and the flaw is moderate, Red Hat will not be releasing a fix for the OpenStack package at this time.

Workaround published by Red Hat
You can pass user input as an expression variable by unwrapping the context to HibernateConstraintValidatorContext. Please refer to the https://in.relation.to/2020/05/07/hibernate-validator-615-6020-released/ and https://docs.jboss.org/hibernate/stable/validator/reference/en-US/html_single/#_the_code_constraintvalidatorcontext_code.
Source: Red Hat security advisory for GHSA-rmrm-75hp-phr2 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Quarkus 1.7.5hibernate-validatorRHSA-2020:4252
Red Hat Fuse 7.9hibernate-validatorRHSA-2021:3140
Red Hat JBoss Enterprise Application Platform 7hibernate-validatorRHSA-2020:3642
Red Hat JBoss Enterprise Application Platform 7hibernate-validatorRHSA-2020:3464
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 6eap7-dom4j-0:2.1.3-1.redhat_00001.1.el6eapRHSA-2020:3637
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 7eap7-dom4j-0:2.1.3-1.redhat_00001.1.el7eapRHSA-2020:3638
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 8eap7-dom4j-0:2.1.3-1.redhat_00001.1.el8eapRHSA-2020:3639
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 6eap7-dom4j-0:2.1.3-1.redhat_00001.1.el6eapRHSA-2020:3461

Frequently Asked Questions

A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.
O3 Security · Impact-Aware SCA

Is GHSA-rmrm-75hp-phr2 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Input Validation in Hibernate Validator