Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Compressed request bodies can exhaust memory before extractor limits apply

GHSA-qph8-7859-gq2f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (actix-http 3.20.1; actix-web 4.18.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io actix-http

    Affected
    >= 0.0.0-0, < 3.20.1
    Fixed in
    3.20.1

  • crates.io actix-web

    Affected
    >= 0.0.0-0, < 4.18.2
    Fixed in
    4.18.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Body extractors do not pass their size limits to the decompression layer. A small compressed request can therefore cause a large allocation before the extractor rejects the decoded body. A remote attacker can use this to exhaust memory or CPU resources and cause denial of service. This affects applications that read compressed request bodies with the corresponding compression feature enabled. Upgrade to actix-web 4.18.2 or later with actix-http 3.20.1 or later. As a workaround, reject compressed request bodies at a reverse proxy or in middleware before body extraction.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record RUSTSEC-2026-0448

  2. Revision 1 · created ·

    Published from osv record RUSTSEC-2026-0447

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-qph8-7859-gq2f

Advisory: Compressed request bodies can exhaust memory before extractor limits apply
IDs: GHSA-qph8-7859-gq2f
Record: https://patchnext.com/advisories/rustsec-2026-0447 (revision 2, source checked 7 Nov 2026, 06:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: actix-http 3.20.1; actix-web 4.18.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io actix-http: affected >= 0.0.0-0, < 3.20.1; fixed in 3.20.1
- crates.io actix-web: affected >= 0.0.0-0, < 4.18.2; fixed in 4.18.2

## Suggested inspection (read-only)
- crates.io actix-http: check the installed version with your package manager.
- crates.io actix-web: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on actix-http, actix-web.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0447 (OSV record RUSTSEC-2026-0447 lists affected ranges: crates.io actix-web >=0.0.0-0 <4.18.2 (fixed))
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0448 (OSV record RUSTSEC-2026-0448 lists affected ranges: crates.io actix-http >=0.0.0-0 <3.20.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…