{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-blockchain.","exploited":"There is no known exploitation of CVE-2026-46369 in the wild and no public exploit code.","fix":"Upgrade nimiq-blockchain to 1.5.1 or later.","what":"CVE-2026-46369 is a high-severity vulnerability in nimiq core-rs-albatross, published on 26 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 CVE-2026-46369 and fix it if it is affected.\n\nWhat it is: CVE-2026-46369 is a high-severity vulnerability in nimiq core-rs-albatross, published on 26 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 CVE-2026-46369 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nimiq-blockchain (crates.io): affected all versions; fixed in 1.5.1\n- nimiq-blockchain (crates.io): affected all versions; fixed in 1.5.1\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-46369/ (Markdown: https://insights.sbomify.com/CVE-2026-46369/index.md)","id":"CVE-2026-46369","markdown":"https://insights.sbomify.com/CVE-2026-46369/index.md","name":"CVE-2026-46369","record":{"aliases":["GHSA-3763-qp59-59vf"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Nimiq blockchain node","requires_auth":"none","summary":"A remote attacker can replay signed transactions due to an off-by-one error in validity checks, causing double balance updates.","user_interaction":"not_required","vuln_class":"business_logic"},"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:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"},{"id":"CWE-193","name":"Off-by-one Error"}],"description":"Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Through 1.5.0, the validity store uses a strict lower-bound comparison that expires a stored transaction too early relative to Transaction::is_valid_at, allowing a remote attacker to replay the same signed transaction during a blocks_per_batch minus one block window and cause the sender and recipient balances to be updated twice. This issue is fixed in version 1.5.1.","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: Validity store off by one error","id":"CVE-2026-46369","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Fleet has observer-level enrollment secret extraction via ORDER BY oracle on labels host-listing endpoint","id":"CVE-2026-46370"},"packages":[{"ecosystem":"crates.io","fixed":["1.5.1"],"introduced":["0"],"last_affected":[],"package":"nimiq-blockchain","purl":null,"source":"GHSA-3763-qp59-59vf"},{"ecosystem":"crates.io","fixed":["1.5.1"],"introduced":["0"],"last_affected":[],"package":"nimiq-blockchain","purl":"pkg:cargo/nimiq-blockchain","source":"GHSA-3763-qp59-59vf"}],"prev":{"headline":"luci-app-https-dns-proxy Authenticated Command Injection via setInitAction","id":"CVE-2026-46368"},"products":["core-rs-albatross"],"published":"2026-08-26","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-08-27","vendors":["nimiq"]},"summary":"A remote attacker can replay signed transactions due to an off-by-one error in validity checks, causing double balance updates.","url":"https://insights.sbomify.com/CVE-2026-46369/"}