How severe is GHSA-f3hf-r62c-mfrj?

No CVSS score has been assigned to GHSA-f3hf-r62c-mfrj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f3hf-r62c-mfrj?

GHSA-f3hf-r62c-mfrj affects the following packages: com.liferay:com.liferay.portal.vulcan.api (Maven), com.liferay:com.liferay.portal.vulcan.impl (Maven). Ecosystems affected: Maven.

How do I fix GHSA-f3hf-r62c-mfrj?

Update com.liferay:com.liferay.portal.vulcan.api to 40.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f3hf-r62c-mfrj is resolved across your whole dependency graph.

How do I detect GHSA-f3hf-r62c-mfrj 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.api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-f3hf-r62c-mfrj if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-f3hf-r62c-mfrj actively exploited in the wild?

No public exploit code has been indexed for GHSA-f3hf-r62c-mfrj 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-f3hf-r62c-mfrj?

GHSA-f3hf-r62c-mfrj has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th 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-f3hf-r62c-mfrj?

GHSA-f3hf-r62c-mfrj is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f3hf-r62c-mfrj published, and has it been updated?

GHSA-f3hf-r62c-mfrj was published on September 12, 2025 and was last updated on September 15, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Liferay Portal: Missing Rate Limiting in GraphQL Endpoint Enables Resource Exhaustion AttackGHSA-f3hf-r62c-mfrj

Fix: liferay/liferay-portal@2e4adf0

GHSA-f3hf-r62c-mfrj is a Uncontrolled Resource Consumption vulnerability in com.liferay:com.liferay.portal.vulcan.api. A fix is available for com.liferay:com.liferay.portal.vulcan.api — see the affected versions and patch details below.

Also known asCVE-2025-43796

Published

Sep 12, 2025

Updated

Sep 15, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-f3hf-r62c-mfrj.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕com.liferay:com.liferay.portal.vulcan.api☕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

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.portal.vulcan.api`	≥ 8.0.2&&< 40.2.0	40.2.0`com.liferay:com.liferay.portal.vulcan.api:40.2.0`
☕Maven	`com.liferay:com.liferay.portal.vulcan.impl`	≥ 5.0.7&&< 5.0.105	5.0.105`com.liferay:com.liferay.portal.vulcan.impl:5.0.105`

Affected Products

2 products · 136 configurations

Application

digital experience platformliferay

≥ 2023.Q3.0 && < 2023.Q3.5

2 versions

7.37.4

Application

liferay portalliferay

≥ 7.4.0 && < 7.4.3.102

range

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.api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.portal.vulcan.api to 40.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f3hf-r62c-mfrj is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-f3hf-r62c-mfrj in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works