cve.bz

CVE-2026-93879

7.5 highEPSS 0.3%

High (7.5) in ibm hibernate validator. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Hibernate Validator could allow a remote attacker to cause a denial of service due to uncontrolled resource consumption resulting from improper escaping of user-controlled data in Expression Language (EL) expressions.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-93879 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93879?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93879?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-93879 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • ibm:hibernate validator

Versions

From the CNA's record in the CVE List.

ProductAffected
IBM Hibernate Validatorfrom 5.4.1.Final through 6.2.5.Final
IBM Hibernate Validatorfrom 7.0.0.Alpha1 through 7.0.5.Final
IBM Hibernate Validatorfrom 8.0.0.Alpha1 through 8.0.5.Final
IBM Hibernate Validatorfrom 9.0.0.Beta2 through 9.0.1.Final
IBM Hibernate Validatorfrom 9.1.0.Alpha1 through 9.1.4.Final

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libhibernate-validator-java, libhibernate-validator4-javano fix listedDEBIAN-CVE-2026-93879
Ubuntu16.04:LTS, 18.04:LTSlibhibernate-validator-javano fix listedUBUNTU-CVE-2026-93879
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 2 morelibhibernate-validator-java, libhibernate-validator4-javano fix listedUBUNTU-CVE-2026-93879

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat Product Security rates this vulnerability as Moderate because it enables a denial of service through resource exhaustion without compromising data integrity or confidentiality. Applications utilizing Hibernate Validator to process untrusted input may experience thread starvation or high CPU usage when validation message templates re-evaluate duplicate parameters via the expression language engine. Exploitation requires submitting tailored payloads to application endpoints performing Bean Validation, but it cannot be leveraged to achieve code execution or data leakage in typical deployments.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Quarkus 3.27.6.redhatorg.hibernate.validator/hibernate-validator:9.0.1.Final-redhat-00002Fixed 2026-10-15RHSA-2026:83082
Red Hat build of Quarkus 3.33.4.redhatorg.hibernate.validator/hibernate-validator:9.1.3.Final-redhat-00002Fixed 2026-10-15RHSA-2026:83520
Exploit Intelligenceexploit-intelligence/agent-client-rhel9Under investigation
Red Hat build of Apache Camel 4 for Quarkus 3hibernate-validatorUnder investigation
Red Hat build of Apache Camel for Spring Boot 4hibernate-validatorUnder investigation
Red Hat Build of Keycloakhibernate-validatorUnder investigation
Red Hat Build of Keycloakrhbk/keycloak-rhel9Under investigation
Red Hat Build of Keycloakrhbk/keycloak-rhel9-operatorUnder investigation
Red Hat Enterprise Linux 10moditectUnder investigation
Red Hat Fuse 7hibernate-validatorUnder investigation
Red Hat Fuse 7hibernate-validator-cdiUnder investigation
Red Hat Fuse 7hibernate-validator-osgi-karaf-featuresUnder investigation
Red Hat JBoss Enterprise Application Platform 7hibernate-validatorUnder investigation
Red Hat JBoss Enterprise Application Platform 7hibernate-validator-annotation-processorUnder investigation
Red Hat JBoss Enterprise Application Platform 7hibernate-validator-cdiUnder investigation
Red Hat JBoss Enterprise Application Platform 7hibernate-validator-parentUnder investigation
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk11-openshift-rhel8Under investigation
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk17-openshift-rhel8Under investigation
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk8-openshift-rhel8Under investigation
Red Hat JBoss Enterprise Application Platform 8hibernate-validatorUnder investigation
9 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-93879.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON