Allocation of Resources Without Limits or Throttling Affecting org.apache.wicket:wicket-core package, versions [,8.19.0)[9.0.0-M1,9.24.0)[10.0.0-M1,10.11.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-19477222
- published1 Sept 2026
- disclosed31 Aug 2026
- creditdeprrous
Introduced: 31 Aug 2026
NewCVE-2026-71257 (opens in a new tab)How to fix?
Upgrade org.apache.wicket:wicket-core to version 8.19.0, 9.24.0, 10.11.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 in the MultipartServletWebRequestImpl servlet-part fallback via readServlet3Parts() in the wicket-core multipart upload path. An attacker can upload files larger than the configured per-file limit or submit more files than allowed by sending a multipart request that reaches HttpServletRequest#getParts() after another component has already consumed the body. In that fallback path, Wicket wrapped the servlet Part objects without reapplying Form#setFileMaxSize or Form#setFileCountMax, so uploads were processed as if those limits had been satisfied. Applications using Wicket upload forms, FileUploadToResourceField, or AjaxFileDropBehavior on deployments where a servlet or filter pre-parses multipart requests are affected.