Liferay Portal and DXP vulnerable to a memory leak

published 2025-09-25 13 mo ago modified 2026-10-18 21 d ago also GHSA-hrqm-qpw9-w8rv , EUVD-2025-31166

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits: 0; none known

A memory leak in the headless API for StructuredContents in Liferay Portal 7.4.0 through 7.4.3.119, and older unsupported versions, and Liferay DXP 2024.Q1.1 through 2024.Q1.5, 2023.Q4.0 through 2024.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions allows an attacker to cause server unavailability (denial of service) via repeatedly calling the API endpoint.

Patch / fix

fixed in 3

maven com.liferay:com.liferay.portal.vulcan.impl 5.0.115
liferay digital_experience_platform 7.4, 2024.Q1.6
liferay liferay_portal 7.4.3.120

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 13 mo ago (2025-09-26)

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	4.0	6.9	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA	4.0	6.9	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	com.liferay:com.liferay.portal.vulcan.impl	<5.0.115	5.0.115

Affected products

Liferay Portal
Liferay DXP

Classification

Weakness

CWE-401 Missing Release of Memory after Effective Lifetime

References

liferay.dev /portal/security/known-vulnerabilities/-/asset_publisher/jekt/content/CVE-2025-43816
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2025-43816
advisory
github.com /liferay/liferay-portal
package
liferay.atlassian.net /browse/LPE-18005
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary