What is CVE-2025-43796?

CVE-2025-43796 is a high-severity uncontrolled resource consumption vulnerability in com.liferay:com.liferay.portal.vulcan.api (maven), affecting versions >= 8.0.2, < 40.2.0. It is fixed in 40.2.0, 5.0.105. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

Which packages are affected by CVE-2025-43796?

com.liferay:com.liferay.portal.vulcan.api (maven) versions >= 8.0.2, = 5.0.7, < 5.0.105.

Is there a fix for CVE-2025-43796?

Yes. CVE-2025-43796 is fixed in 40.2.0, 5.0.105. Upgrade to this version or later.

Is CVE-2025-43796 exploitable, and should I be worried?

Whether CVE-2025-43796 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-43796 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-43796

Q: Which packages are affected by CVE-2025-43796?

com.liferay:com.liferay.portal.vulcan.api (maven) versions >= 8.0.2, = 5.0.7, < 5.0.105.

Q: Is there a fix for CVE-2025-43796?

Yes. CVE-2025-43796 is fixed in 40.2.0, 5.0.105. Upgrade to this version or later.

Q: Is CVE-2025-43796 exploitable, and should I be worried?

Whether CVE-2025-43796 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-43796 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-43796?

Upgrade: com.liferay:com.liferay.portal.vulcan.api to 40.2.0 or later, com.liferay:com.liferay.portal.vulcan.impl to 5.0.105 or later.

Summary

Liferay Portal: Missing Rate Limiting in GraphQL Endpoint Enables Resource Exhaustion Attack

Liferay Portal 7.4.0 through 7.4.3.101, and Liferay DXP 2023.Q3.0 through 2023.Q3.4, 7.4 GA through update 92 and 7.3 GA though update 35 does not limit the number of objects returned from a GraphQL queries, which allows remote attackers to perform denial-of-service (DoS) attacks on the application by executing queries that return a large number of objects.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

com.liferay:com.liferay.portal.vulcan.api (>= 8.0.2, < 40.2.0) com.liferay:com.liferay.portal.vulcan.impl (>= 5.0.7, < 5.0.105)

Security releases

com.liferay:com.liferay.portal.vulcan.api → 40.2.0 (maven) com.liferay:com.liferay.portal.vulcan.impl → 5.0.105 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

com.liferay:com.liferay.portal.vulcan.api to 40.2.0 or later; com.liferay:com.liferay.portal.vulcan.impl to 5.0.105 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-43796? CVE-2025-43796 is a high-severity uncontrolled resource consumption vulnerability in com.liferay:com.liferay.portal.vulcan.api (maven), affecting versions >= 8.0.2, < 40.2.0. It is fixed in 40.2.0, 5.0.105. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
Which packages are affected by CVE-2025-43796?
- com.liferay:com.liferay.portal.vulcan.api (maven) (versions >= 8.0.2, < 40.2.0)
- com.liferay:com.liferay.portal.vulcan.impl (maven) (versions >= 5.0.7, < 5.0.105)
Is there a fix for CVE-2025-43796? Yes. CVE-2025-43796 is fixed in 40.2.0, 5.0.105. Upgrade to this version or later.
Is CVE-2025-43796 exploitable, and should I be worried? Whether CVE-2025-43796 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-43796 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-43796?
- Upgrade com.liferay:com.liferay.portal.vulcan.api to 40.2.0 or later
- Upgrade com.liferay:com.liferay.portal.vulcan.impl to 5.0.105 or later