{"answers":{"affected":"1 open source package ship an affected version, including wasmtime-wasi-http.","exploited":"There is no known exploitation of RUSTSEC-2026-0376 in the wild and no public exploit code.","fix":"Upgrade wasmtime-wasi-http to a fixed version for your release line: 36.0.19, 48.0.7 or 49.0.4.","what":"RUSTSEC-2026-0376 is a vulnerability in wasmtime-wasi-http, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0376 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0376 is a vulnerability in wasmtime-wasi-http, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of RUSTSEC-2026-0376 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- wasmtime-wasi-http (crates.io): affected from 0.0.0-0; fixed in 36.0.19, 48.0.7, 49.0.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0376/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0376/index.md)","id":"RUSTSEC-2026-0376","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0376/index.md","name":"RUSTSEC-2026-0376","record":{"aliases":["GHSA-r8xh-cgf7-392j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Wasmtime wasi-http","requires_auth":"none","summary":"Guests can inject conflicting content lengths in wasi-http messages, potentially causing request smuggling or data integrity issues.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This is an entry in the RustSec database for the Wasmtime security advisory\nlocated at\nhttps://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-r8xh-cgf7-392j\nFor more information see the GitHub-hosted security advisory.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"`wasi-http`: Guests can add conflicting content lengths to messages","id":"RUSTSEC-2026-0376","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["36.0.19","48.0.7","49.0.4"],"introduced":["0.0.0-0","37.0.0","49.0.0"],"last_affected":[],"package":"wasmtime-wasi-http","purl":"pkg:cargo/wasmtime-wasi-http","source":"RUSTSEC-2026-0376"}],"products":null,"published":"2026-10-19","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Guests can inject conflicting content lengths in wasi-http messages, potentially causing request smuggling or data integrity issues.","url":"https://insights.sbomify.com/RUSTSEC-2026-0376/"}