Find a vulnerability
Search criteria
Related vulnerabilities
RUSTSEC-2026-0554 (GHSA-54PM-2WM5-HPMG)
Vulnerability from osv_rustsec – Published: 2026-11-16 12:00 – Updated: 2026-11-17 10:14 – Source websiteAffected versions of actix-http apply the request header timeout only to the
first request on an HTTP/1 connection. When data arrives for a later request,
the dispatcher clears the idle keep-alive timer without starting a request
header timer.
A remote client without authentication can complete one request, send one byte of a second request, and leave the connection open indefinitely without sending more data. The same problem occurs when a complete pipelined request is followed by a partial request in the same read. Repeating this can exhaust connection or file-descriptor limits and prevent new connections from being accepted. The effect depends on the server's resource limits and upstream connection controls.
Upgrade to actix-http 3.21.2 or later. The fix applies the configured request
header timeout to later partial requests, including those left in the buffer
after a complete pipelined request. Additional bytes do not renew the deadline.
The timeout covers request headers, not upload bodies.
If an upgrade is not possible, disable HTTP keep-alive, for example with
HttpServer::keep_alive(KeepAlive::Disabled) in actix-web. Connection limits
can reduce resource use but do not make stalled connections expire.
{
"affected": [
{
"database_specific": {
"categories": [
"denial-of-service"
],
"cvss": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "actix-http",
"purl": "pkg:cargo/actix-http"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "3.21.2"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-54pm-2wm5-hpmg"
],
"database_specific": {
"license": "CC-BY-4.0"
},
"details": "Affected versions of `actix-http` apply the request header timeout only to the\nfirst request on an HTTP/1 connection. When data arrives for a later request,\nthe dispatcher clears the idle keep-alive timer without starting a request\nheader timer.\n\nA remote client without authentication can complete one request, send one byte\nof a second request, and leave the connection open indefinitely without sending\nmore data. The same problem occurs when a complete pipelined request is followed\nby a partial request in the same read. Repeating this can exhaust connection or\nfile-descriptor limits and prevent new connections from being accepted. The\neffect depends on the server\u0027s resource limits and upstream connection controls.\n\nUpgrade to `actix-http` 3.21.2 or later. The fix applies the configured request\nheader timeout to later partial requests, including those left in the buffer\nafter a complete pipelined request. Additional bytes do not renew the deadline.\nThe timeout covers request headers, not upload bodies.\n\nIf an upgrade is not possible, disable HTTP keep-alive, for example with\n`HttpServer::keep_alive(KeepAlive::Disabled)` in `actix-web`. Connection limits\ncan reduce resource use but do not make stalled connections expire.",
"id": "RUSTSEC-2026-0554",
"modified": "2026-11-17T10:14:35Z",
"published": "2026-11-16T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/actix-http"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0554.html"
},
{
"type": "WEB",
"url": "https://github.com/actix/actix-web/releases/tag/actix-http-v3.21.2"
},
{
"type": "ADVISORY",
"url": "https://github.com/actix/actix-web/security/advisories/GHSA-54pm-2wm5-hpmg"
}
],
"related": [],
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Partial requests on keep-alive connections can bypass the request header timeout"
}