{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-keys.","exploited":"There is no known exploitation of CVE-2026-40092 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40092 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40092 is a high-severity denial of service vulnerability in nimiq core-rs-albatross, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40092 and fix it if it is affected.\n\nWhat it is: CVE-2026-40092 is a high-severity denial of service vulnerability in nimiq core-rs-albatross, published on 20 May 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 CVE-2026-40092 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nimiq-keys (crates.io): affected all versions up to 0.2.0; no fix listed\n- nimiq-keys (crates.io): affected all versions up to 0.2.0; no fix listed\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/CVE-2026-40092/ (Markdown: https://insights.sbomify.com/CVE-2026-40092/index.md)","id":"CVE-2026-40092","markdown":"https://insights.sbomify.com/CVE-2026-40092/index.md","name":"CVE-2026-40092","record":{"aliases":["GHSA-27w2-87xv-37c6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust blockchain library","requires_auth":"none","summary":"A malicious peer can crash Nimiq full nodes by sending a DHT record with an invalid Ed25519 signature length, causing a panic.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-252","name":"Unchecked Return Value"}],"description":"nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In versions 1.3.0 and below, a malicious network peer can crash any Nimiq full node by publishing a crafted Kademlia DHT record. The maliciously crafted record would contain a TaggedSigned\u003cValidatorRecord, KeyPair\u003e with a signature field whose byte length is not exactly 64 in order to cause a crash. When the victim node's DHT verifier calls TaggedSigned::verify, execution reaches Ed25519Signature::from_bytes(sig).unwrap() in the TaggedPublicKey implementation for Ed25519PublicKey. The from_bytes call fails because ed25519_zebra::Signature::try_from rejects slices not 64 bytes, and the unwrap() panics. The BLS TaggedPublicKey implementation correctly returns false on error; only the Ed25519 implementation panics. This issue has been fixed in version 1.4.0.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"nimiq-keys: Unchecked Ed25519 signature length in TaggedPublicKey::verify causes remote node panic via DHT","id":"CVE-2026-40092","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"nimiq-blockchain is missing a wall-clock upper bound on block timestamps","id":"CVE-2026-40093"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nimiq-keys","purl":null,"source":"GHSA-27w2-87xv-37c6"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nimiq-keys","purl":"pkg:cargo/nimiq-keys","source":"GHSA-27w2-87xv-37c6"}],"prev":{"headline":"SpiceDB: SPICEDB_DATASTORE_CONN_URI is leaked on startup logs","id":"CVE-2026-40091"},"products":["core-rs-albatross"],"published":"2026-05-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-21","vendors":["nimiq"]},"summary":"A malicious peer can crash Nimiq full nodes by sending a DHT record with an invalid Ed25519 signature length, causing a panic.","url":"https://insights.sbomify.com/CVE-2026-40092/"}