CVE-2026-33241: Salvo Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-pp9r-xg4c-8j4x
CWE-770
Published
Advisory Summary

CVE-2026-33241 is a HIGH denial of service vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Salvo libraries in the crates.io ecosystem. The issue involves salvo affected by denial of service via unbounded memory allocation in form data parsing. Remediation is available by upgrading affected packages to version 0.89.3.

CVE-2026-33241 at a Glance

CVE Identifier CVE-2026-33241
GHSA Identifier GHSA-pp9r-xg4c-8j4x
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Salvo
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix CVE-2026-33241

To remediate this vulnerability, upgrade all affected Salvo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

salvo fixed: 0.89.3
Upgrade salvo to 0.89.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for salvo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-33241, inspect your project dependencies for Salvo:

inspect dependencies for salvo

Analyze the terminal output to locate any version of Salvo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.89.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where 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. In Salvo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Salvo's form data parsing implementations (`form_data()` method and `Extractible` macro) do not enforce payload size limits before reading request bodies into memory. This allows attackers to cause Out-of-Memory (OOM) conditions by sending extremely large payloads, leading to service crashes and denial of service. ## Details ### Vulnerability Description Three attack vectors exist in Salvo's form handling: 1. **URL-encoded form data** (`application/x-www-form-urlencoded`) - `Request::form_data()` calls `BodyExt::collect(body)` which reads the entire body into memory without size checking - Affects handlers using `req.form_data().await` directly 2. **Multipart form data** (`multipart/form-data`) - Similar unbounded memory allocation during parsing - Affects handlers processing multipart uploads 3. **Extractible macro** - `#[derive(Extractible)]` with `#[salvo(extract(default_source(from = "body")))]` internally calls `form_data()` - Vulnerabilities propagate to all extractors using body sources ### Root Cause The `FormData::read()` implementation prioritizes convenience over safety by reading entire request bodies before validation. Even when `Request::payload_with_max_size()` is available, it's not automatically applied in the form parsing path. ### PoC 1. run `Extract data from request` example in readme.md in docker file with limited memory say 100mb. 2. Send `application/x-www-form-urlencoded` OR `multipart/form-data` payload to the endpoint. 3. The server process OOM-crashes, instead of returning 413 error. ## Impact ### Immediate Effects - **Service Unavailability**: Servers crash under memory pressure - **Resource Exhaustion**: Single request can consume all available memory - **Cascading Failures**: In containerized environments, OOM can affect other services ### Attack Characteristics - **Low Cost**: Attacker needs minimal bandwidth (header only, body can be streamed) - **No Authentication**: Exploitable on public endpoints - **Difficult to Rate-Limit**: Traditional rate limiting may not prevent single large request - **Amplification**: Small network cost → large memory consumption ### Real-World Scenarios 1. Public API endpoints accepting form data 2. User registration/profile update handlers 3. File upload endpoints using multipart forms 4. Any endpoint using `#[derive(Extractible)]` with body sources ## Suggestion: Make Multipart File Upload Handling Explicit Opt-In ### Problem Statement Currently, Salvo's multipart form data parsing automatically handles file uploads without explicit developer intent. This creates several security and usability concerns: 1. **Unintended File Storage**: Developers may unknowingly accept file uploads when they only intended to handle text fields 2. **Disk Space Exhaustion**: Automatic file buffering to disk can fill storage without proper limits 3. **Resource Cleanup**: Temporary files may not be properly cleaned up if handlers don't expect them 4. **Attack Surface**: Endpoints inadvertently become file upload targets

CVE-2026-33241 Affected Salvo Versions

1 component(s)
Fixed Versions:
0.89.3
Product / Package Ecosystem Affected Versions Fixed Version
salvo
crates.io
< 0.89.3
0.89.3

References

Frequently Asked Questions

What is CVE-2026-33241?
CVE-2026-33241 is a security vulnerability in Salvo involving Salvo Affected by Denial of Service via Unbounded Memory Allocation in Form Data Parsing under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Salvo versions are affected?
Affected versions include releases prior to 0.89.3 across affected packages: salvo.
What version fixes CVE-2026-33241?
Upgrading to 0.89.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is salvo affected?
Yes, salvo is affected in releases prior to 0.89.3. Upgrade your dependency to 0.89.3 or later.
What CWE is associated with CVE-2026-33241?
CVE-2026-33241 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (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.).
How can I check crates.io dependencies for CVE-2026-33241?
Run the dependency tree command: 'inspect dependencies for salvo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pp9r-xg4c-8j4x",
  "modified" : "2026-03-25T20:48:57Z",
  "published" : "2026-03-19T12:44:56Z",
  "aliases" : [ "CVE-2026-33241" ],
  "summary" : "Salvo Affected by Denial of Service via Unbounded Memory Allocation in Form Data Parsing",
  "details" : "## Summary\nSalvo's form data parsing implementations (`form_data()` method and `Extractible` macro) do not enforce payload size limits before reading request bodies into memory. This allows attackers to cause Out-of-Memory (OOM) conditions by sending extremely large payloads, leading to service crashes and denial of service.\n\n## Details\n### Vulnerability Description\nThree attack vectors exist in Salvo's form handling:\n\n1. **URL-encoded form data** (`application/x-www-form-urlencoded`)\n   - `Request::form_data()` calls `BodyExt::collect(body)` which reads the entire body into memory without size checking\n   - Affects handlers using `req.form_data().await` directly\n\n2. **Multipart form data** (`multipart/form-data`)\n   - Similar unbounded memory allocation during parsing\n   - Affects handlers processing multipart uploads\n\n3. **Extractible macro**\n   - `#[derive(Extractible)]` with `#[salvo(extract(default_source(from = \"body\")))]` internally calls `form_data()`\n   - Vulnerabilities propagate to all extractors using body sources\n\n### Root Cause\nThe `FormData::read()` implementation prioritizes convenience over safety by reading entire request bodies before validation. Even when `Request::payload_with_max_size()` is available, it's not automatically applied in the form parsing path.\n\n### PoC\n1. run `Extract data from request` example in readme.md in docker file with limited memory say 100mb.\n2. Send `application/x-www-form-urlencoded` OR `multipart/form-data` payload to the endpoint.\n3. The server process OOM-crashes, instead of returning 413 error.\n\n\n## Impact\n### Immediate Effects\n- **Service Unavailability**: Servers crash under memory pressure\n- **Resource Exhaustion**: Single request can consume all available memory\n- **Cascading Failures**: In containerized environments, OOM can affect other services\n\n### Attack Characteristics\n- **Low Cost**: Attacker needs minimal bandwidth (header only, body can be streamed)\n- **No Authentication**: Exploitable on public endpoints\n- **Difficult to Rate-Limit**: Traditional rate limiting may not prevent single large request\n- **Amplification**: Small network cost → large memory consumption\n\n### Real-World Scenarios\n1. Public API endpoints accepting form data\n2. User registration/profile update handlers\n3. File upload endpoints using multipart forms\n4. Any endpoint using `#[derive(Extractible)]` with body sources\n\n## Suggestion: Make Multipart File Upload Handling Explicit Opt-In\n\n### Problem Statement\n\nCurrently, Salvo's multipart form data parsing automatically handles file uploads without explicit developer intent. This creates several security and usability concerns:\n\n1. **Unintended File Storage**: Developers may unknowingly accept file uploads when they only intended to handle text fields\n2. **Disk Space Exhaustion**: Automatic file buffering to disk can fill storage without proper limits\n3. **Resource Cleanup**: Temporary files may not be properly cleaned up if handlers don't expect them\n4. **Attack Surface**: Endpoints inadvertently become file upload targets",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "salvo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.89.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/salvo-rs/salvo/security/advisories/GHSA-pp9r-xg4c-8j4x"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33241"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/salvo-rs/salvo"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/salvo-rs/salvo/releases/tag/v0.89.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-19T12:44:56Z",
    "nvd_published_at" : "2026-03-24T00:16:29Z"
  }
}