{"answers":{"affected":"1 open source package ship an affected version, including nostr-relay-pool.","exploited":"There is no known exploitation of RUSTSEC-2026-0232 in the wild and no public exploit code.","fix":"Upgrade nostr-relay-pool to 0.44.3 or later.","what":"RUSTSEC-2026-0232 is a 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-0232 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0232 is a 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-0232 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-0232/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0232/index.md)","id":"RUSTSEC-2026-0232","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0232/index.md","name":"RUSTSEC-2026-0232","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust relay SDK","requires_auth":"none","summary":"A malicious relay can bypass event verification, allowing forged events to be processed as authentic, compromising data integrity in the SDK.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The processed events received from a relay through admission-policy and database\npaths before verifying that the serialized fields matched the claimed event ID and\nsignature. In particular, a database result for the claimed ID could cause\nverification to be skipped. The verification cache also keyed successful checks by a\n64-bit hash instead of the complete event ID.\n\nA malicious relay could send an event whose claimed ID referred to a known database\nentry while its content, tags, author, or signature differed from that ID. The forged\nevent could then reach policy callbacks or other SDK processing as if it were\nauthentic. A cache-key collision provided a second path for an unverified event to be\ntreated as previously verified. This undermines event integrity but does not reveal\nprivate keys or enable the attacker to produce a valid signature for the altered\nevent.\n\nThe SDK now verifies each event before policy evaluation, database lookup, or\npropagation decisions, and the verification cache stores the complete `EventId` so a\ntruncated hash collision cannot stand in for successful verification.","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":"Processing of unverified relay events","id":"RUSTSEC-2026-0232","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"security_feature_bypass","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-0232"}],"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 bypass event verification, allowing forged events to be processed as authentic, compromising data integrity in the SDK.","url":"https://insights.sbomify.com/RUSTSEC-2026-0232/"}