Skip to main content
VulnerabilityPublished

CVE-2025-43816: Liferay Portal · Memory Leak

Affects Liferay PortalSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Liferay PortalAffected
  • =7.4.0
Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Monitor and limit the rate of API calls to the headless StructuredContents endpoint using web application firewalls (WAFs) or API gateways to prevent abuse through repeated requests. 2) Employ resource usage monitoring and alerting on Liferay Portal servers to detect abnormal memory consumption early. 3) Isolate the Liferay Portal environment in segmented network zones with strict access controls to reduce exposure. 4) Apply any available vendor patches or updates promptly once released; if no patches are available, consider upgrading to unaffected versions or applying vendor-recommended workarounds. 5) Conduct internal penetration testing and fuzzing on the API endpoints to identify and mitigate similar memory management issues proactively. 6) Implement strict user interaction controls and logging to detect suspicious repeated API usage patterns. 7) Engage with Liferay support and subscribe to security advisories for timely updates. These measures go beyond generic advice by focusing on traffic control, monitoring, and network segmentation tailored to the specific API and vulnerability characteristics.

Description

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.

References

Community reviews

Loading reviews…