{"answers":{"affected":"1 open source package ship an affected version, including nostr.","exploited":"There is no known exploitation of RUSTSEC-2026-0219 in the wild and no public exploit code.","fix":"Upgrade nostr to a fixed version for your release line: 0.44.6 or 0.45.0-alpha.6.","what":"RUSTSEC-2026-0219 is a denial of service vulnerability in nostr, published on 26 Jul 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-0219 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0219 is a denial of service vulnerability in nostr, published on 26 Jul 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-0219 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.6, 0.45.0-alpha.6\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-0219/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0219/index.md)","id":"RUSTSEC-2026-0219","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0219/index.md","name":"RUSTSEC-2026-0219","record":{"aliases":["GHSA-xg7c-246g-6qpv"],"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":"none","summary":"A remote attacker can cause a denial of service in applications using the nostr crate by sending malformed NIP-04 initialization vectors that trigger 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 `nostr` crate did not validate the length of the initialization vector\ndecoded from the `?iv=` portion of a NIP-04 encrypted message.\n\nThe decoded IV was converted from a byte slice to the 16-byte AES-CBC IV type\nusing a conversion that asserts the slice length. As a result, an IV whose\ndecoded length was not exactly 16 bytes caused a panic before ciphertext\ndecryption. For example, `?iv=AAAA` decodes to a three-byte IV and triggers the\npanic.\n\nApplications that decrypt untrusted NIP-04 content are affected. The issue is\nalso reachable through NIP-47 (Nostr Wallet Connect), where response and\nnotification events from a malicious or compromised wallet service are passed\nto NIP-04 decryption. If the panic is not isolated, a crafted event can terminate\nthe application or disrupt message processing, causing a denial of service.\n\nThe issue does not affect confidentiality or integrity.\n\nThe flaw was corrected by converting the decoded IV to `[u8; 16]` using a\nchecked conversion. Invalid IV lengths now return a `Malformed` error instead of\npanicking.\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-04 IV","id":"RUSTSEC-2026-0219","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.6","0.45.0-alpha.6"],"introduced":["0.0.0-0","0.45.0-alpha.1"],"last_affected":[],"package":"nostr","purl":"pkg:cargo/nostr","source":"RUSTSEC-2026-0219"}],"products":null,"published":"2026-07-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":"A remote attacker can cause a denial of service in applications using the nostr crate by sending malformed NIP-04 initialization vectors that trigger a panic.","url":"https://insights.sbomify.com/RUSTSEC-2026-0219/"}