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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-43796: 0.38% estimated exploitation activity in the next 30 days; percentile 32.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

12 Sep 2025, 21:32 UTC

Last modified by the source

15 Sep 2025, 13:46 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f3hf-r62c-mfrj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-43796

Advisory: Liferay Portal: Missing Rate Limiting in GraphQL Endpoint Enables Resource Exhaustion Attack
IDs: CVE-2025-43796, GHSA-f3hf-r62c-mfrj
Record: https://patchnext.com/advisories/cve-2025-43796 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.liferay:com.liferay.portal.vulcan.impl 5.0.105; com.liferay:com.liferay.portal.vulcan.api 40.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay:com.liferay.portal.vulcan.impl: affected >= 5.0.7, < 5.0.105; fixed in 5.0.105
- Maven com.liferay:com.liferay.portal.vulcan.api: affected >= 8.0.2, < 40.2.0; fixed in 40.2.0

## Suggested inspection (read-only)
- Maven com.liferay:com.liferay.portal.vulcan.impl: check the installed version with your package manager.
- Maven com.liferay:com.liferay.portal.vulcan.api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.liferay:com.liferay.portal.vulcan.impl, com.liferay:com.liferay.portal.vulcan.api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f3hf-r62c-mfrj (GitHub-reviewed advisory GHSA-f3hf-r62c-mfrj lists affected ranges: Maven com.liferay:com.liferay.portal.vulcan.api >=8.0.2 =5.0.7 <5.0.105)

Commands are suggestions: review each one before running it.