{"answers":{"affected":"1 open source package ship an affected version, including rustls-ffi.","exploited":"There is no known exploitation of RUSTSEC-2026-0413 in the wild and no public exploit code.","fix":"Upgrade rustls-ffi to 0.15.7 or later.","what":"RUSTSEC-2026-0413 is a vulnerability in rustls-ffi, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0413 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0413 is a vulnerability in rustls-ffi, published on 26 Oct 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0413 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rustls-ffi (crates.io): affected from 0.12.0; fixed in 0.15.7\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-0413/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0413/index.md)","id":"RUSTSEC-2026-0413","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0413/index.md","name":"RUSTSEC-2026-0413","record":{"aliases":["GHSA-rc3f-4j82-cmrg"],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In rustls-ffi 0.12.0 through 0.15.6, `rustls_client_connection_new()` and\n`rustls_client_connection_new_alpn()` retained a reference to the caller's\n`server_name` buffer after returning, rather than copying it. The API\ndocumentation did not require the buffer to outlive the call and as a result\nif the caller freed or reused the buffer, later TLS processing read freed\nmemory.\n\nClients that free or reuse the `server_name` buffer after the constructor\nreturns are affected. This is most likely for language bindings that pass\ntemporary strings. Callers that keep the `server_name` buffer alive for the\nlifetime of the `rustls_client_config` are not affected.\n\nVersions 0.12.0 through 0.15.6 are affected. Version 0.15.7+ changed these APIs\nto copy the input buffer.","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":"Use-after-free of caller-owned server name in client connection constructors","id":"RUSTSEC-2026-0413","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.15.7"],"introduced":["0.12.0"],"last_affected":[],"package":"rustls-ffi","purl":"pkg:cargo/rustls-ffi","source":"RUSTSEC-2026-0413"}],"products":null,"published":"2026-10-26","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":null,"url":"https://insights.sbomify.com/RUSTSEC-2026-0413/"}