{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-blockchain. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40093 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40093 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40093 is a high-severity vulnerability in nimiq core-rs-albatross, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40093 and fix it if it is affected.\n\nWhat it is: CVE-2026-40093 is a high-severity vulnerability in nimiq core-rs-albatross, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-40093 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nimiq-blockchain (crates.io): affected all versions up to 1.3.0; no fix listed\n- nimiq-blockchain (crates.io): affected all versions up to 1.3.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-40093/ (Markdown: https://insights.sbomify.com/CVE-2026-40093/index.md)","id":"CVE-2026-40093","markdown":"https://insights.sbomify.com/CVE-2026-40093/index.md","name":"CVE-2026-40093","record":{"aliases":["GHSA-49xc-52mp-cc9j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Nimiq blockchain library","requires_auth":"low_privilege","summary":"A malicious validator can set future block timestamps to inflate monetary supply, affecting reward calculations in the Nimiq blockchain library.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nimiq_proof-of-stake","vendor":"nimiq"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In 1.3.0 and earlier, block timestamp validation enforces that timestamp \u003e= parent.timestamp for non-skip blocks and timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule.","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-blockchain is missing a wall-clock upper bound on block timestamps","id":"CVE-2026-40093","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"nimiq-blockchain: network-libp2p untrusted peer can crash address book via empty peer contact addresses","id":"CVE-2026-40094"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.3.0"],"package":"nimiq-blockchain","purl":null,"source":"GHSA-49xc-52mp-cc9j"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.3.0"],"package":"nimiq-blockchain","purl":"pkg:cargo/nimiq-blockchain","source":"GHSA-49xc-52mp-cc9j"}],"prev":{"headline":"nimiq-keys: Unchecked Ed25519 signature length in TaggedPublicKey::verify causes remote node panic via DHT","id":"CVE-2026-40092"},"products":["core-rs-albatross"],"published":"2026-04-09","related":[{"cvss_score":9.6,"headline":"nimiq-block has skip block quorum bypass via out-of-range BitSet indices \u0026 u16 truncation","id":"CVE-2026-33471","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":7.5,"headline":"network-libp2p: Peer can crash the node by opening discovery protocol substream twice","id":"CVE-2026-34063","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":7.5,"headline":"nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals","id":"CVE-2026-34065","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":7.5,"headline":"Nimiq: Remote crash via off-by-one signer bounds check in proposal buffer","id":"CVE-2026-32605","kev_date_added":null,"published":"2026-04-13"},{"cvss_score":7.5,"headline":"nimiq/core-rs-albatross: Discovery handshake limit could underflow and later provoke a deterministic overflow panic","id":"CVE-2026-33184","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":7.1,"headline":"nimiq/core-rs-albatross's nimiq-blockchain missing proposal body root verification","id":"CVE-2026-28402","kev_date_added":null,"published":"2026-02-27"}],"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":"US public information, NVD API terms","name":"NVD"},{"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-04-13","vendors":["nimiq"]},"summary":"A malicious validator can set future block timestamps to inflate monetary supply, affecting reward calculations in the Nimiq blockchain library.","url":"https://insights.sbomify.com/CVE-2026-40093/"}