How severe is GHSA-hrqm-qpw9-w8rv?

No CVSS score has been assigned to GHSA-hrqm-qpw9-w8rv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hrqm-qpw9-w8rv?

GHSA-hrqm-qpw9-w8rv affects the following packages: com.liferay:com.liferay.portal.vulcan.impl (Maven). Ecosystems affected: Maven.

How do I fix GHSA-hrqm-qpw9-w8rv?

Update com.liferay:com.liferay.portal.vulcan.impl to 5.0.115 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrqm-qpw9-w8rv is resolved across your whole dependency graph.

How do I detect GHSA-hrqm-qpw9-w8rv in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.portal.vulcan.impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hrqm-qpw9-w8rv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hrqm-qpw9-w8rv?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hrqm-qpw9-w8rv can be triaged on real exposure rather than presence alone.

Is GHSA-hrqm-qpw9-w8rv actively exploited in the wild?

No public exploit code has been indexed for GHSA-hrqm-qpw9-w8rv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hrqm-qpw9-w8rv?

GHSA-hrqm-qpw9-w8rv has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hrqm-qpw9-w8rv?

GHSA-hrqm-qpw9-w8rv is classified as CWE-401 (CWE-401). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hrqm-qpw9-w8rv published, and has it been updated?

GHSA-hrqm-qpw9-w8rv was published on September 25, 2025 and was last updated on December 17, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-hrqm-qpw9-w8rv: com.liferay.portal

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hrqm-qpw9-w8rv.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕com.liferay:com.liferay.portal.vulcan.impl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.portal.vulcan.impl`	all versions	5.0.115`com.liferay:com.liferay.portal.vulcan.impl:5.0.115`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.portal.vulcan.impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.portal.vulcan.impl to 5.0.115 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrqm-qpw9-w8rv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hrqm-qpw9-w8rv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hrqm-qpw9-w8rv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-hrqm-qpw9-w8rv in your dependencies?

O3 Security finds GHSA-hrqm-qpw9-w8rv across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

GHSA-hrqm-qpw9-w8rv — com.liferay.portal.vulcan…