{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-keys.","exploited":"There is no known exploitation of CVE-2026-46542 in the wild and no public exploit code.","fix":"Upgrade nimiq-keys to 1.4.0 or later.","what":"CVE-2026-46542 is a medium-severity denial of service vulnerability in nimiq core-rs-albatross, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-46542 and fix it if it is affected.\n\nWhat it is: CVE-2026-46542 is a medium-severity denial of service vulnerability in nimiq core-rs-albatross, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-46542 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nimiq-keys (crates.io): affected all versions; fixed in 1.4.0\n- nimiq-keys (crates.io): affected all versions; fixed in 1.4.0\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-46542/ (Markdown: https://insights.sbomify.com/CVE-2026-46542/index.md)","id":"CVE-2026-46542","markdown":"https://insights.sbomify.com/CVE-2026-46542/index.md","name":"CVE-2026-46542","record":{"aliases":["GHSA-h9cc-w26m-j342"],"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":"Attackers can crash the application by providing invalid Ed25519 public keys to the delinearization function, causing a panic.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"description":"Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.4.0, a denial-of-service vulnerability exists in the Ed25519 multisig delinearization code path. Ed25519PublicKey::delinearize() in keys/src/multisig/mod.rs called .unwrap() on curve point decompression, which panics when a public key is constructed from 32 bytes that do not represent a valid point on the Ed25519 curve. Ed25519PublicKey construction only validates byte length, not curve membership, so invalid keys can reach the delinearization path and crash the hosting process. This issue has been patched 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":true,"headline":"nimiq-keys: Denial of service in Ed25519 multisig delinearization via invalid curve points","id":"CVE-2026-46542","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"nimiq-blockchain: Genesis batch set request","id":"CVE-2026-46543"},"packages":[{"ecosystem":"crates.io","fixed":["1.4.0"],"introduced":["0"],"last_affected":[],"package":"nimiq-keys","purl":null,"source":"GHSA-h9cc-w26m-j342"},{"ecosystem":"crates.io","fixed":["1.4.0"],"introduced":["0"],"last_affected":[],"package":"nimiq-keys","purl":"pkg:cargo/nimiq-keys","source":"GHSA-h9cc-w26m-j342"}],"prev":{"headline":"Nimiq network-libp2p: DHT query poisoning via first-record verification failure","id":"CVE-2026-46541"},"products":["core-rs-albatross"],"published":"2026-06-09","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-10","vendors":["nimiq"]},"summary":"Attackers can crash the application by providing invalid Ed25519 public keys to the delinearization function, causing a panic.","url":"https://insights.sbomify.com/CVE-2026-46542/"}