How severe is GHSA-9cxr-76pm-j3wf?

GHSA-9cxr-76pm-j3wf has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-9cxr-76pm-j3wf?

GHSA-9cxr-76pm-j3wf affects the following packages: org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-9cxr-76pm-j3wf?

Update org.apache.wicket:wicket-core to 8.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9cxr-76pm-j3wf is resolved across your whole dependency graph.

How do I detect GHSA-9cxr-76pm-j3wf in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.wicket:wicket-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-9cxr-76pm-j3wf 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-9cxr-76pm-j3wf?

O3 pinpoints whether GHSA-9cxr-76pm-j3wf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9cxr-76pm-j3wf actively exploited in the wild?

No public exploit code has been indexed for GHSA-9cxr-76pm-j3wf 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 type of vulnerability is GHSA-9cxr-76pm-j3wf?

GHSA-9cxr-76pm-j3wf 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-9cxr-76pm-j3wf published, and has it been updated?

GHSA-9cxr-76pm-j3wf was published on January 23, 2025 and was last updated on March 11, 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

MEDIUM severity

GHSA-9cxr-76pm-j3wf

MEDIUM

GHSA-9cxr-76pm-j3wf is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in org.apache.wicket:wicket-core. O3 Security confirms whether GHSA-9cxr-76pm-j3wf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache Wicket: An attacker can intentionally trigger a memory leak

Also known asCVE-2024-53299

Published

Jan 23, 2025

Updated

Mar 11, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Mar 11, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core

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

The request handling in the core in Apache Wicket 7.0.0 on any platform allows an attacker to create a DOS via multiple requests to server resources. Users are recommended to upgrade to versions 9.19.0 or 10.3.0, which fixes this issue.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.wicket:wicket-core`	≥ 7.0.0&&< 8.17.0	8.17.0
☕Maven	`org.apache.wicket:wicket-core`	≥ 10.0.0&&< 10.3.0	10.3.0
☕Maven	`org.apache.wicket:wicket-core`	≥ 9.0.0-M1&&< 9.19.0	9.19.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.wicket:wicket-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.wicket:wicket-core to 8.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9cxr-76pm-j3wf 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 pinpoints whether GHSA-9cxr-76pm-j3wf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9cxr-76pm-j3wf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-9cxr-76pm-j3wf in your dependencies?

O3 detects GHSA-9cxr-76pm-j3wf across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works