{"answers":{"affected":"1 open source package ship an affected version, including nostr.","exploited":"There is no known exploitation of RUSTSEC-2026-0216 in the wild and no public exploit code.","fix":"Upgrade nostr to a fixed version for your release line: 0.44.5 or 0.45.0-alpha.5.","what":"RUSTSEC-2026-0216 is a denial of service vulnerability in nostr, published on 25 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0216 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0216 is a denial of service vulnerability in nostr, published on 25 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of RUSTSEC-2026-0216 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nostr (crates.io): affected from 0.0.0-0; fixed in 0.44.5, 0.45.0-alpha.5\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-0216/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0216/index.md)","id":"RUSTSEC-2026-0216","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0216/index.md","name":"RUSTSEC-2026-0216","record":{"aliases":["GHSA-hrqp-8w79-gwgw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust Nostr library","requires_auth":"low_privilege","summary":"A remote attacker with a conversation key can cause a denial of service in the nostr crate by sending a malformed NIP-44 v2 payload that triggers a panic.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The NIP-44 v2 decryption path in the `nostr` crate contains a reachable panic\nwhen processing a short or empty ciphertext. After the HMAC check passes and the\nciphertext is decrypted via ChaCha20, the code reads a 2‑byte unpadded‑length\nprefix via `buffer[0..2]` without first verifying that the decrypted buffer\ncontains at least 2 bytes. A malicious sender who holds the symmetric\nconversation key (e.g., a direct‑message sender) can craft a payload that\nproduces a 0 or 1‑byte decrypted buffer, causing an index‑out‑of‑bounds panic.\nThis can be triggered remotely through any relay that delivers the crafted\nevent to the victim's client, resulting in a denial of service. No key material,\nplaintext, or memory corruption occurs.\n\nThe vulnerability is present in all versions from `0.26.0` up to `0.44.4`\n(inclusive) and in the alpha releases `0.45.0‑alpha.1` through `0.45.0‑alpha.4`.\nVersions `0.44.5` and `0.45.0‑alpha.5` contain the fix.\n\n## Credit\n\nDiscovered and responsibly disclosed by **Muhammed Shekho** ([mhd-shekho.com](https://mhd-shekho.com)).","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":"Remote Denial of Service via malformed NIP‑44 v2 payload","id":"RUSTSEC-2026-0216","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.44.5","0.45.0-alpha.5"],"introduced":["0.0.0-0","0.45.0-alpha.1"],"last_affected":[],"package":"nostr","purl":"pkg:cargo/nostr","source":"RUSTSEC-2026-0216"}],"products":null,"published":"2026-07-25","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":"A remote attacker with a conversation key can cause a denial of service in the nostr crate by sending a malformed NIP-44 v2 payload that triggers a panic.","url":"https://insights.sbomify.com/RUSTSEC-2026-0216/"}