GHSA-xhj4-vrgc-hr34: Actix http Actix-http Has HTTP/1.1 CL.TE Request Vulnerability

MODERATE
CWE-444
Published
Advisory Summary

GHSA-xhj4-vrgc-hr34 is a MODERATE actix-http has http/1.1 cl.te request vulnerability (CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')) affecting Actix http libraries in the crates.io ecosystem. The issue involves actix-http has http/1.1 cl.te request smuggling. Remediation is available by upgrading affected packages to version 3.12.1.

GHSA-xhj4-vrgc-hr34 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-xhj4-vrgc-hr34
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Affected Product Actix http
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-xhj4-vrgc-hr34

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

actix-http fixed: 3.12.1
Upgrade actix-http to 3.12.1
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 actix-http

How to Check if You Are Affected

To determine whether your application is affected by GHSA-xhj4-vrgc-hr34, inspect your project dependencies for Actix http:

inspect dependencies for actix-http

Analyze the terminal output to locate any version of Actix http in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.12.1), 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-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'), where the product acts as an intermediary http agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed http requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. In Actix http, 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

A vulnerability in `actix-http`'s HTTP/1.1 request parser allows an unauthenticated remote client to smuggle requests in deployments where a front-end HTTP intermediary and the Actix backend disagree about whether `Content-Length` or `Transfer-Encoding: chunked` defines the request body length. ## Severity **Medium**. This is an HTTP request smuggling vulnerability that can be triggered over the network without application-level credentials. Exploitation requires a specific proxy topology: an upstream proxy, WAF, load balancer, or similar intermediary must use `Content-Length` framing while forwarding the conflicting `Transfer-Encoding: chunked` request to an Actix backend over a reused HTTP/1.1 connection. ## Affected Versions - `actix-http`: versions up to and including **3.12.0** ## Description HTTP/1.1 requests that contain both `Content-Length` and `Transfer-Encoding: chunked` are ambiguous and must be rejected by recipients to avoid request smuggling. Affected versions of `actix-http` accepted a request with a syntactically valid `Content-Length` header and `Transfer-Encoding: chunked` on the same HTTP/1.1 message. The parser then selected chunked decoding instead of rejecting the conflicting framing signals. In a CL.TE proxy topology, an intermediary may treat bytes after the declared `Content-Length` body as part of the first request, while the Actix backend stops at the terminating chunk marker and parses the remaining bytes on the backend connection as a second HTTP request. This creates a backend-side request desynchronization primitive. The issue is limited to HTTP/1.1 request parsing. ## Impact **HTTP request smuggling** * **Attack Vector:** Network, unauthenticated. * **Effect:** Backend request desynchronization with low integrity impact to requests processed by the vulnerable Actix service. * **Scope:** Actix services using affected `actix-http` versions behind an HTTP/1.1 intermediary that forwards ambiguous `Content-Length` plus `Transfer-Encoding: chunked` requests and reuses backend connections. No direct confidentiality, availability, or subsequent-system impact is scored for this advisory. ## Fixed Versions This issue is fixed in **actix-http 3.12.1**. The fix rejects HTTP/1.1 requests that contain both `Content-Length` and `Transfer-Encoding: chunked` instead of choosing one framing interpretation. ## Mitigation Users should upgrade to **actix-http 3.12.1** or later. Applications that depend on `actix-http` through `actix-web`, `awc`, or another Actix crate should ensure dependency resolution selects `actix-http` 3.12.1 or later. For example: ```bash cargo update -p actix-http ``` If an immediate upgrade is not possible, configure all upstream HTTP intermediaries to reject HTTP/1.1 requests that contain both `Content-Length` and `Transfer-Encoding`, and avoid forwarding ambiguous request framing to Actix backends. ## Credits Actix thanks [mufeedvh](https://github.com/mufeedvh) who disclosed this issue through coordinated disclosure.

GHSA-xhj4-vrgc-hr34 Affected Actix http Versions

1 component(s)
Fixed Versions:
3.12.1
Product / Package Ecosystem Affected Versions Fixed Version
actix-http
crates.io
< 3.12.1
3.12.1

References

Frequently Asked Questions

What is GHSA-xhj4-vrgc-hr34?
GHSA-xhj4-vrgc-hr34 is a security vulnerability in Actix http involving actix-http has HTTP/1.1 CL.TE Request Smuggling under CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling').
Which Actix http versions are affected?
Affected versions include releases prior to 3.12.1 across affected packages: actix-http.
What version fixes GHSA-xhj4-vrgc-hr34?
Upgrading to 3.12.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is actix-http affected?
Yes, actix-http is affected in releases prior to 3.12.1. Upgrade your dependency to 3.12.1 or later.
What CWE is associated with GHSA-xhj4-vrgc-hr34?
GHSA-xhj4-vrgc-hr34 is classified under CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') (The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.).
How can I check crates.io dependencies for GHSA-xhj4-vrgc-hr34?
Run the dependency tree command: 'inspect dependencies for actix-http'. 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-xhj4-vrgc-hr34",
  "modified" : "2026-04-22T14:37:30Z",
  "published" : "2026-04-22T14:37:30Z",
  "aliases" : [ ],
  "summary" : "actix-http has HTTP/1.1 CL.TE Request Smuggling ",
  "details" : "A vulnerability in `actix-http`'s HTTP/1.1 request parser allows an unauthenticated remote client to smuggle requests in deployments where a front-end HTTP intermediary and the Actix backend disagree about whether `Content-Length` or `Transfer-Encoding: chunked` defines the request body length.\n\n## Severity\n\n**Medium**.\nThis is an HTTP request smuggling vulnerability that can be triggered over the network without application-level credentials. Exploitation requires a specific proxy topology: an upstream proxy, WAF, load balancer, or similar intermediary must use `Content-Length` framing while forwarding the conflicting `Transfer-Encoding: chunked` request to an Actix backend over a reused HTTP/1.1 connection.\n\n## Affected Versions\n\n- `actix-http`: versions up to and including **3.12.0**\n\n## Description\n\nHTTP/1.1 requests that contain both `Content-Length` and `Transfer-Encoding: chunked` are ambiguous and must be rejected by recipients to avoid request smuggling.\n\nAffected versions of `actix-http` accepted a request with a syntactically valid `Content-Length` header and `Transfer-Encoding: chunked` on the same HTTP/1.1 message. The parser then selected chunked decoding instead of rejecting the conflicting framing signals.\n\nIn a CL.TE proxy topology, an intermediary may treat bytes after the declared `Content-Length` body as part of the first request, while the Actix backend stops at the terminating chunk marker and parses the remaining bytes on the backend connection as a second HTTP request. This creates a backend-side request desynchronization primitive.\n\nThe issue is limited to HTTP/1.1 request parsing.\n\n## Impact\n\n**HTTP request smuggling**\n\n* **Attack Vector:** Network, unauthenticated.\n* **Effect:** Backend request desynchronization with low integrity impact to requests processed by the vulnerable Actix service.\n* **Scope:** Actix services using affected `actix-http` versions behind an HTTP/1.1 intermediary that forwards ambiguous `Content-Length` plus `Transfer-Encoding: chunked` requests and reuses backend connections.\n\nNo direct confidentiality, availability, or subsequent-system impact is scored for this advisory.\n\n## Fixed Versions\n\nThis issue is fixed in **actix-http 3.12.1**.\n\nThe fix rejects HTTP/1.1 requests that contain both `Content-Length` and `Transfer-Encoding: chunked` instead of choosing one framing interpretation.\n\n## Mitigation\n\nUsers should upgrade to **actix-http 3.12.1** or later.\n\nApplications that depend on `actix-http` through `actix-web`, `awc`, or another Actix crate should ensure dependency resolution selects `actix-http` 3.12.1 or later. For example:\n\n```bash\ncargo update -p actix-http\n```\n\nIf an immediate upgrade is not possible, configure all upstream HTTP intermediaries to reject HTTP/1.1 requests that contain both `Content-Length` and `Transfer-Encoding`, and avoid forwarding ambiguous request framing to Actix backends.\n## Credits\n\nActix thanks [mufeedvh](https://github.com/mufeedvh) who disclosed this issue through coordinated disclosure.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "actix-http"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.12.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/actix/actix-web/security/advisories/GHSA-xhj4-vrgc-hr34"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/actix/actix-web"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/actix/actix-web/releases/tag/http-v3.12.1"
  }, {
    "type" : "WEB",
    "url" : "https://www.rfc-editor.org/rfc/rfc9112.html#name-message-body-length"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-444" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-22T14:37:30Z",
    "nvd_published_at" : null
  }
}