CVE-2026-128842
Description
A flaw was found in busboy. When processing URL-encoded form data, the parser checks if a field's length strictly equals the configured per-field limit rather than checking if the limit is reached or exceeded. A remote, unauthenticated attacker can supply malformed percent-encoded characters that cause the length check to be bypassed. As a result, the parser continues buffering the field in memory up to the total request size, leading to excessive memory consumption and a potential Denial of Service (DoS).
Statement
This vulnerability is rated as a Moderate impact because while an unauthenticated remote client can bypass configured per-field thresholds to inflate memory consumption, overall allocation remains constrained by the broader HTTP body limits. In typical Red Hat environments, applications running Fastify services usually operate behind reverse proxies or have global request size ceilings configured, preventing complete system memory exhaustion. Furthermore, the issue only affects service availability without compromising data integrity or confidentiality.
Mitigation
Enforce a conservative whole-request body size limit at the application level or at an upstream reverse proxy (such as NGINX, Apache HTTP Server, or an API gateway).
To implement this mitigation at the proxy tier:
1. Configure the reverse proxy to limit client request payload sizes (for example, using `client_max_body_size` in NGINX or `LimitRequestBody` in Apache HTTP Server).
2. Reload or restart the proxy service to apply the configuration.
Caveats:
Restricting the maximum request body size will block client requests that exceed the specified threshold. Modifying reverse proxy settings requires a service reload, which may cause a brief disruption to active network connections.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.