{"answers":{"affected":"1 open source package ship an affected version, including nostr-relay-pool.","exploited":"There is no known exploitation of RUSTSEC-2026-0231 in the wild and no public exploit code.","fix":"Upgrade nostr-relay-pool to 0.44.3 or later.","what":"RUSTSEC-2026-0231 is a denial of service vulnerability in nostr-relay-pool, published on 1 Aug 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-0231 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0231 is a denial of service vulnerability in nostr-relay-pool, published on 1 Aug 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-0231 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nostr-relay-pool (crates.io): affected from 0.0.0-0; fixed in 0.44.3\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-0231/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0231/index.md)","id":"RUSTSEC-2026-0231","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0231/index.md","name":"RUSTSEC-2026-0231","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust Nostr SDK","requires_auth":"none","summary":"A malicious relay can exhaust client memory by flooding authentication challenges, causing denial of service in the Rust Nostr SDK.","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 SDK forwarded every NIP-42 `AUTH` challenge received from a relay through an\nunbounded command queue. Challenge handling can wait for an asynchronous signer or\nuser interaction, so receiving challenges was substantially faster than completing\nthe corresponding authentication work.\n\nA malicious relay could continuously send new challenges without authenticating or\ndelivering valid events. Every value remained queued, causing memory use and pending\nsigner operations to grow without a fixed limit until the client became unavailable.\nThe issue does not allow the relay to forge a signature or learn the client's private\nkey.\n\nThe SDK now coalesces pending challenges through a latest-value channel. NIP-42 makes\nan earlier challenge invalid when the relay sends a new one, so replacing pending\nwork preserves the only challenge that can still be answered while keeping memory\nuse bounded.","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":"Relay authentication challenges can exhaust memory","id":"RUSTSEC-2026-0231","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.3"],"introduced":["0.0.0-0"],"last_affected":[],"package":"nostr-relay-pool","purl":"pkg:cargo/nostr-relay-pool","source":"RUSTSEC-2026-0231"}],"products":null,"published":"2026-08-01","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 malicious relay can exhaust client memory by flooding authentication challenges, causing denial of service in the Rust Nostr SDK.","url":"https://insights.sbomify.com/RUSTSEC-2026-0231/"}