DHI-v7o7-aooy-b5ej-twdd: undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. While…

Published Nov 13, 2026
·
Updated

undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. While the number of content-encoding layers is capped, the total decompressed output size is unbounded and there is no configuration option to limit it. A malicious or faulty upstream can therefore return a small compressed payload, a compression bomb, that expands to hundreds of megabytes or more in client memory, an asymmetric resource consumption that can exhaust memory and crash the process. This affects undici versions from 7.15.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.

Affected Software

7 affected components
docker-hardened-images/kyverno-policy-reporter-ui-dev=2.6.1-r0, =2.7.0-r0, =2.7.0-r1, =2.7.0-r2, =2.7.1-r0, =2.7.1-r1, =2.7.1-r2, =2.7.2-r0, =2.7.2-r1, =2.7.3-r0, =2.8.1-r0, =2.8.1-r1, =2.8.1-r2, =2.8.1-r3, =2.8.1-r4, =2.8.1-r5, =2.9.0-r1, =2.9.1-r0, =2.9.1-r1, =2.9.1-r2, =2.9.1-r3, =2.9.1-r4, =2.9.1-r5
docker-hardened-images/kyverno-policy-reporter-ui-fips-dev=2.6.1-r0, =2.7.0-r0, =2.7.0-r1, =2.7.0-r2, =2.7.1-r0, =2.7.1-r1, =2.7.1-r2, =2.7.2-r0, =2.7.2-r1, =2.7.3-r0, =2.8.1-r0, =2.8.1-r1, =2.8.1-r2, =2.8.1-r3, =2.8.1-r4, =2.8.1-r5, =2.9.0-r1, =2.9.1-r0, =2.9.1-r1, =2.9.1-r2, =2.9.1-r3, =2.9.1-r4, =2.9.1-r5
docker-hardened-images/kyverno-policy-reporter-ui-fips=2.6.1-r0, =2.7.0-r0, =2.7.0-r1, =2.7.0-r2, =2.7.1-r0, =2.7.1-r1, =2.7.1-r2, =2.7.2-r0, =2.7.2-r1, =2.7.3-r0, =2.8.1-r0, =2.8.1-r1, =2.8.1-r2, =2.8.1-r3, =2.8.1-r4, =2.8.1-r5, =2.9.0-r1, =2.9.1-r0, =2.9.1-r1, =2.9.1-r2, =2.9.1-r3, =2.9.1-r4, =2.9.1-r5
docker-hardened-images/kyverno-policy-reporter-ui=2.6.1-r0, =2.7.0-r0, =2.7.0-r1, =2.7.0-r2, =2.7.1-r0, =2.7.1-r1, =2.7.1-r2, =2.7.2-r0, =2.7.2-r1, =2.7.3-r0, =2.8.1-r0, =2.8.1-r1, =2.8.1-r2, =2.8.1-r3, =2.8.1-r4, =2.8.1-r5, =2.9.0-r1, =2.9.1-r0, =2.9.1-r1, =2.9.1-r2, =2.9.1-r3, =2.9.1-r4, =2.9.1-r5
docker-hardened-images/qdrant=1.18.3-0, =1.18.3-1, =1.18.3-2, =1.19.0-0, =1.19.0-1, =1.19.0-2, =1.19.0-3, =1.19.0-4, =1.19.0-5, =1.19.0-6, =1.19.1-1, =1.19.1-2, =1.19.1-3, =1.19.1-4, =1.19.1-5, =1.19.1-6, =1.19.1-7, =1.19.2-0, =1.19.2-1, =1.19.2-2, =1.20.0-0, =1.20.0-1, =1.20.0-2, =1.20.0-3, =1.20.0-4, =1.20.0-6, =1.20.0-7, =1.20.0-8, =1.20.1-0
docker-hardened-images/supabase-storage=1.74.1-0, =1.79.30-0, =1.79.30-1, =1.79.30-2, =1.84.25-0, =1.84.28-0, =1.84.32-0, =1.84.33-0, =1.84.36-0, =1.84.36-1, =1.85.0-0, =1.89.12-0, =1.89.12-1, =1.89.12-2, =1.89.13-0, =1.89.13-1, =1.90.0-0, =1.90.1-0, =1.90.2-0, =1.91.0-0, =1.92.0-0, =1.94.0-0, =1.94.2-0, =1.94.2-1, =1.95.0-0
docker-hardened-images/uptime-kuma-2=2.5.0-0, =2.5.0-1, =2.5.0-2, =2.5.10-0, =2.5.11-0, =2.5.11-1, =2.5.11-2, =2.5.11-3, =2.5.3-0, =2.5.3-1, =2.5.4-0, =2.5.5-0, =2.5.5-1, =2.5.6-0, =2.5.7-0, =2.5.7-1, =2.5.9-0, =2.5.9-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 7.29.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.10.2

Event History

Nov 13, 2026
Advisory Published
via OSV·05:03 PM
Data Sourced
via OSV·05:03 PM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What conditions are needed for exploitation?

An attacker needs to control, or cause the client to contact, an upstream that can return a crafted compressed HTTP response. The response uses a small payload that expands to a very large size when processed according to its Content-Encoding header.

2

Is there a configuration setting that limits the memory impact?

No. The decompression interceptor has no configuration option to limit the total decompressed output size, although it caps the number of content-encoding layers.

3

How can I determine whether a deployment is affected?

Check whether the deployment uses undici's decompress interceptor and is running an undici version from 7.15.0 through 7.29.1 or from 8.0.0 through 8.10.2. The affected software list includes the specified Docker Hardened Images for Kyverno Policy Reporter UI, Qdrant, Supabase Storage, and Uptime Kuma 2.

4

What remediation is provided?

The provided guidance is to upgrade undici to 7.29.1 or 8.10.2. No alternative mitigation is specified for cases where upgrading cannot be performed immediately.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203