{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-66559 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-66559 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66559 is a high-severity vulnerability in taikoxyz taiko-mono, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66559 and fix it if it is affected.\n\nWhat it is: CVE-2025-66559 is a high-severity vulnerability in taikoxyz taiko-mono, published on 4 Dec 2025. 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-2025-66559 in the wild and no public exploit code.\n\nAffected product: taikoxyz taiko-mono. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-66559/ (Markdown: https://insights.sbomify.com/CVE-2025-66559/index.md)","id":"CVE-2025-66559","markdown":"https://insights.sbomify.com/CVE-2025-66559/index.md","name":"CVE-2025-66559","record":{"aliases":["GHSA-5mxh-r33p-6h5x"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ethereum rollup protocol","requires_auth":"none","summary":"Attackers can corrupt verified chain pointers in Taiko Alethia by exploiting batch verification logic, compromising rollup integrity.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-129","name":"Improper Validation of Array Index"}],"description":"Taiko Alethia is an Ethereum-equivalent, permissionless, based rollup designed to scale Ethereum without compromising its fundamental properties. In 2.3.1 and earlier, TaikoInbox._verifyBatches (packages/protocol/contracts/layer1/based/TaikoInbox.sol:627-678) advanced the local tid to whatever transition matched the current blockHash before knowing whether that batch would actually be verified. When the loop later broke (e.g., cooldown window not yet passed or transition invalidated), the function still wrote that newer tid into batches[lastVerifiedBatchId].verifiedTransitionId after decrementing batchId. Result: the last verified batch could end up pointing at a transition index from the next batch (often zeroed), corrupting the verified chain pointer.","ecosystems":[],"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":"Taiko Alethia Pacaya inbox verification pointer corruption","id":"CVE-2025-66559","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write","id":"CVE-2025-66560"},"packages":[],"prev":{"headline":"Nextcloud Twofactor WebAuthn app was updated based on public key","id":"CVE-2025-66558"},"products":["taiko-mono"],"published":"2025-12-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2025-12-05","vendors":["taikoxyz"]},"summary":"Attackers can corrupt verified chain pointers in Taiko Alethia by exploiting batch verification logic, compromising rollup integrity.","url":"https://insights.sbomify.com/CVE-2025-66559/"}