CVE Vulnerabilities

CVE-2026-105854

Uncontrolled Resource Consumption

Published: Oct 06, 2026 | Modified: Oct 15, 2026
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu
root.io logo minimus.io logo echo.ai logo

Payload is a free and open source headless content management system. In versions from 3.0.0 before 3.90.0 and canary versions before 4.0.0-canary.34, a malformed multipart request body can cause multipart Content-Type processing to take an extremely long time, resulting in uncontrolled resource consumption. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.

Weakness

The product does not properly control the allocation and maintenance of a limited resource.

Affected Software

NameVendorStart VersionEnd Version
PayloadPayloadcms3.0.0 (including)3.90.0 (excluding)
PayloadPayloadcms4.0.0-canary0 (including)4.0.0-canary0 (including)
PayloadPayloadcms4.0.0-canary1 (including)4.0.0-canary1 (including)
PayloadPayloadcms4.0.0-canary10 (including)4.0.0-canary10 (including)
PayloadPayloadcms4.0.0-canary11 (including)4.0.0-canary11 (including)
PayloadPayloadcms4.0.0-canary12 (including)4.0.0-canary12 (including)
PayloadPayloadcms4.0.0-canary13 (including)4.0.0-canary13 (including)
PayloadPayloadcms4.0.0-canary14 (including)4.0.0-canary14 (including)
PayloadPayloadcms4.0.0-canary15 (including)4.0.0-canary15 (including)
PayloadPayloadcms4.0.0-canary16 (including)4.0.0-canary16 (including)
PayloadPayloadcms4.0.0-canary17 (including)4.0.0-canary17 (including)
PayloadPayloadcms4.0.0-canary18 (including)4.0.0-canary18 (including)
PayloadPayloadcms4.0.0-canary19 (including)4.0.0-canary19 (including)
PayloadPayloadcms4.0.0-canary2 (including)4.0.0-canary2 (including)
PayloadPayloadcms4.0.0-canary20 (including)4.0.0-canary20 (including)
PayloadPayloadcms4.0.0-canary21 (including)4.0.0-canary21 (including)
PayloadPayloadcms4.0.0-canary22 (including)4.0.0-canary22 (including)
PayloadPayloadcms4.0.0-canary23 (including)4.0.0-canary23 (including)
PayloadPayloadcms4.0.0-canary24 (including)4.0.0-canary24 (including)
PayloadPayloadcms4.0.0-canary25 (including)4.0.0-canary25 (including)
PayloadPayloadcms4.0.0-canary26 (including)4.0.0-canary26 (including)
PayloadPayloadcms4.0.0-canary27 (including)4.0.0-canary27 (including)
PayloadPayloadcms4.0.0-canary28 (including)4.0.0-canary28 (including)
PayloadPayloadcms4.0.0-canary29 (including)4.0.0-canary29 (including)
PayloadPayloadcms4.0.0-canary3 (including)4.0.0-canary3 (including)
PayloadPayloadcms4.0.0-canary30 (including)4.0.0-canary30 (including)
PayloadPayloadcms4.0.0-canary31 (including)4.0.0-canary31 (including)
PayloadPayloadcms4.0.0-canary32 (including)4.0.0-canary32 (including)
PayloadPayloadcms4.0.0-canary33 (including)4.0.0-canary33 (including)
PayloadPayloadcms4.0.0-canary4 (including)4.0.0-canary4 (including)
PayloadPayloadcms4.0.0-canary5 (including)4.0.0-canary5 (including)
PayloadPayloadcms4.0.0-canary6 (including)4.0.0-canary6 (including)
PayloadPayloadcms4.0.0-canary7 (including)4.0.0-canary7 (including)
PayloadPayloadcms4.0.0-canary8 (including)4.0.0-canary8 (including)
PayloadPayloadcms4.0.0-canary9 (including)4.0.0-canary9 (including)

Potential Mitigations

  • Mitigation of resource exhaustion attacks requires that the target system either:

  • The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.

  • The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.

References