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

CVE-2017-7536 — hibernate-validator

HIGHFix: hibernate/hibernate-validator@0886e89

CVE-2017-7536 is a high-severity (CVSS 7) CWE-592 vulnerability in org.hibernate:hibernate-validator. A fix is available for org.hibernate:hibernate-validator — see the affected versions and patch details below.

Privilege Escalation in Hibernate Validator

Also known asGHSA-xxgp-pcfc-3vgc
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk
0.00%0.33%0.65%0.98%0.1%0.5%Jun 26Oct 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

3 pkgs affected
☕org.hibernate: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

In Hibernate Validator 5.2.x before 5.2.5.Final, 5.3.x before 5.3.6.Final, and 5.4.x before 5.4.2.Final, it was found that when the security manager's reflective permissions, which allows it to access the private members of the class, are granted to Hibernate Validator, a potential privilege escalation can occur. By allowing the calling code to access those private members without the permission an attacker may be able to validate an invalid instance and access the private member value via ConstraintViolation#getInvalidValue().

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.hibernate:hibernate-validator≥ 5.2.0&&< 5.2.5.Final5.2.5.Finalorg.hibernate:hibernate-validator:5.2.5.Final
☕Mavenorg.hibernate:hibernate-validator≥ 5.3.0&&< 5.3.6.Final5.3.6.Finalorg.hibernate:hibernate-validator:5.3.6.Final
☕Mavenorg.hibernate:hibernate-validator≥ 5.4.0&&< 5.4.2.Final5.4.2.Finalorg.hibernate:hibernate-validator:5.4.2.Final

Affected Products

6 products · 11 configurations
Application
hibernate validatorredhat
≥ 5.4.0 && < 5.4.2
range
Application
jboss enterprise application platformredhat
4 versions
6.0.06.4.07.07.1
Application
satelliteredhat
1 version
6.4
Application
satellite capsuleredhat
1 version
6.4
Application
virtualizationredhat
1 version
4.0
Application
virtualization hostredhat
1 version
4.0

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:hibernate-validator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.hibernate:hibernate-validator to 5.2.5.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7536 is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

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
ProductFixed inAdvisory
Red Hat JBoss A-MQ 6.3hibernate-validatorRHSA-2018:3817
Red Hat JBoss EAP 7see advisoryRHSA-2017:2810
Red Hat JBoss EAP 7see advisoryRHSA-2017:3456
Red Hat JBoss Enterprise Application Platform 6.4hibernate-validatorRHSA-2018:2740
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5codehaus-jackson-0:1.9.9-14.redhat_7.1.ep6.el5RHSA-2018:2742
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6codehaus-jackson-0:1.9.9-14.redhat_7.1.ep6.el6RHSA-2018:2743
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7codehaus-jackson-0:1.9.9-14.redhat_7.1.ep6.el7RHSA-2018:2741
Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6eap7-artemis-native-0:1.1.0-13.redhat_4.ep7.el6RHSA-2017:2809

Frequently Asked Questions

In Hibernate Validator 5.2.x before 5.2.5.Final, 5.3.x before 5.3.6.Final, and 5.4.x before 5.4.2.Final, it was found that when the security manager's reflective permissions, which allows it to access the private members of the class, are granted to Hibernate Validator, a potential privilege escalation can occur. By allowing the calling code to access those private members without the permission an attacker may be able to validate an invalid instance and access the private member value via ConstraintViolation#getInvalidValue().
O3 Security · Impact-Aware SCA

Is CVE-2017-7536 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2017-7536: hibernate PrivEsc — Fixed in 5.2.5.Final