Allocation of Resources Without Limits or Throttling Affecting org.apache.wicket:wicket-core package, versions [9.14.0,9.25.0)[10.0.0-M1,10.12.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGAPACHEWICKET-22150205
- published3 Nov 2026
- disclosed1 Nov 2026
- creditEmond Papegaaij
Introduced: 1 Nov 2026
NewCVE-2026-84170 (opens in a new tab)How to fix?
Upgrade org.apache.wicket:wicket-core to version 9.25.0, 10.12.0 or higher.
Overview
org.apache.wicket:wicket-core is a Java web application framework that takes simplicity, separation of concerns and ease of development to a whole new level. Wicket pages can be mocked up, previewed and later revised using standard WYSIWYG HTML design tools. Dynamic content processing and form handling is all handled in Java code using a first-class component model backed by POJO data beans that can easily be persisted using your favorite technology.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the newResourceResponse() method in AbstractFileUploadResource. An attacker can consume server disk space or heap and deny service by submitting a multipart upload with an oversized maxSize and omitting fileMaxSize and fileCountMax; the server trusts these request parameters instead of enforcing the limits configured on FileUploadToResourceField. Unless the application explicitly authorizes the separately mounted upload resource, the request requires no authentication or prior page view.