How severe is CVE-2024-53299?

CVE-2024-53299 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 CVE-2024-53299?

CVE-2024-53299 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 CVE-2024-53299?

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 CVE-2024-53299 is resolved across your whole dependency graph.

How do I detect CVE-2024-53299 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-53299 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 CVE-2024-53299 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-53299 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 CVE-2024-53299?

CVE-2024-53299 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th 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 CVE-2024-53299?

CVE-2024-53299 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 CVE-2024-53299 published, and has it been updated?

CVE-2024-53299 was published on January 23, 2025 and was last updated on October 28, 2026. 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

CVE-2024-53299 — wicket-core

MEDIUM

CVE-2024-53299 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in org.apache.wicket:wicket-core. A fix is available for org.apache.wicket:wicket-core — see the affected versions and patch details below.

Apache Wicket: An attacker can intentionally trigger a memory leak

Also known asGHSA-9cxr-76pm-j3wf

Published

Jan 23, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 5, 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 CVE-2024-53299.

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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`org.apache.wicket:wicket-core:8.17.0`
☕Maven	`org.apache.wicket:wicket-core`	≥ 10.0.0&&< 10.3.0	10.3.0`org.apache.wicket:wicket-core:10.3.0`
☕Maven	`org.apache.wicket:wicket-core`	≥ 9.0.0-M1&&< 9.19.0	9.19.0`org.apache.wicket:wicket-core:9.19.0`

Affected Products

1 product · 4 configurations

Application

wicketapache

≥ 10.0.0 && ≤ 8.16.0

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2024-53299 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 CVE-2024-53299 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-400Uncontrolled Resource Consumption

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jan 23, 2025

Last updated

Oct 28, 2026

Identifiers

CVE-2024-53299

GHSA-9cxr-76pm-j3wf

References

Advisorygithub.com · CVE 2024 53299.json Advisorylists.apache.org · gyp2ht00c62827y0379lxh5dbx3hhho5 Advisorynvd.nist.gov · CVE 2024 53299 Webopenwall.com Webwicket.apache.org · wicket 8.17.0 released Packagegithub.com · wicket

Related vulnerabilities

Also affects wicket-core

This CVE is medium severity; 7 of 7 other CVEs affecting wicket-core are rated as high or higher (top: high).

CVE-2026-43975CVE-2021-23937CVE-2014-0043CVE-2016-6806CVE-2014-3526CVE-2014-7808CVE-2020-11976

Same weakness: CWE-400

This CVE is medium severity, in line with the other 1 CVE with CWE-400.

CVE-2026-62300Browse all CWE-400

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2024-53299 — wicket-core

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2024-53299 in your dependencies?