CVE-2026-71257
Received Received - Intake

Unrestricted File Upload in Apache Wicket

Vulnerability report for CVE-2026-71257, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-31

Last updated on: 2026-08-31

Assigner: Apache Software Foundation

Description

Apache Wicket enforces the upload limits configured on a form or upload field while parsing a multipart request with Apache Commons FileUpload. If the request body has already been consumed by another component, Commons FileUpload returns no items and Wicket falls back to reading the upload through HttpServletRequest#getParts(). The per-file size limit (for example Form#setFileMaxSize) and the file count limit (Form#setFileCountMax) are not applied to the parts obtained that way, and no exception is raised, so the upload is processed as though those limits had been satisfied. A remote uploader can therefore submit files that are larger, or more numerous, than the application permits, up to whatever the component that parsed the request allows. A part carrying no Content-Type header is additionally read into memory in full during parsing, so the size of that allocation is determined by the request and bounded only by those same external limits. The total upload size limit (Form#setMaxSize) is not affected. Commons FileUpload compares the declared Content-Length against it before reading the body, so a request declaring an oversized length is rejected before the fallback is reached. The fallback is reached in deployments where a servlet or filter has already parsed the request body β€” for example a servlet annotated with @MultipartConfig, Spring Boot's multipart resolver, or any filter that calls HttpServletRequest#getParameter() on a multipart request. It applies to the Wicket components that accept uploads on that path, including Form with FileUploadField, FileUploadToResourceField and AjaxFileDropBehavior. Applications that configure neither a per-file nor a file-count limit are not affected, as Wicket applies neither by default. This issue affects Apache Wicket: from 8.0.0 through 8.18.0, from 9.0.0 through 9.23.0, from 10.0.0 through 10.10.0. Users are recommended to upgrade to version 8.19.0, 9.24.0 or 10.11.0, which fix the issue. Users of Apache Wicket 7.x or older, which are no longer supported, should upgrade to a supported version. As a workaround, configure equivalent limits in the component that parses the request β€” for example spring.servlet.multipart.max-file-size and max-request-size, or maxFileSize and maxRequestSize in @MultipartConfig or in the web.xml <multipart-config> element.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-31
Last Modified
2026-08-31
Generated
2026-08-31
AI Q&A
2026-08-31
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
apache wicket From 8.0.0 (inc) to 8.18.0 (inc)
apache wicket From 9.0.0 (inc) to 9.23.0 (inc)
apache wicket From 10.0.0 (inc) to 10.10.0 (inc)
apache wicket 8.19.0
apache wicket 9.24.0
apache wicket 10.11.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Apache Wicket fails to enforce file upload size and count limits when another component has already parsed the multipart request body. This allows attackers to bypass configured limits by submitting oversized or excessive files, as Wicket falls back to reading raw parts without validation.

Detection Guidance

Detecting this vulnerability requires checking Apache Wicket versions in use. Inspect your application's dependency files (e.g., pom.xml for Maven or build.gradle for Gradle) for Apache Wicket versions between 8.0.0-8.18.0, 9.0.0-9.23.0, or 10.0.0-10.10.0. If any of these versions are present, the system is vulnerable.

Impact Analysis

An attacker could upload files larger or more numerous than intended, potentially consuming excessive server resources, causing denial of service, or bypassing application restrictions. Sensitive data might be exposed if large files are processed unexpectedly.

Compliance Impact

This vulnerability could lead to unauthorized data storage or processing, violating GDPR principles like data minimization and security. For HIPAA, it may compromise protected health information integrity or availability due to unchecked uploads.

Mitigation Strategies

Upgrade Apache Wicket to version 8.19.0, 9.24.0, or 10.11.0 or later. If using unsupported versions (7.x or older), upgrade to a supported version. As a temporary workaround, configure equivalent upload limits in the component parsing the request (e.g., Spring Boot's multipart settings or @MultipartConfig in web.xml).

Ensure per-file size limits (Form#setFileMaxSize) and file count limits (Form#setFileCountMax) are set. Verify total upload size limits (Form#setMaxSize) are correctly configured to prevent oversized requests.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-71257. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart