{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48886 exists.","fix":"No fix has been published for CVE-2025-48886 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48886 is a medium-severity vulnerability in cardano-scaling hydra, published on 19 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-48886 and fix it if it is affected.\n\nWhat it is: CVE-2025-48886 is a medium-severity vulnerability in cardano-scaling hydra, published on 19 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48886 exists.\n\nAffected product: cardano-scaling hydra. 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-48886/ (Markdown: https://insights.sbomify.com/CVE-2025-48886/index.md)","id":"CVE-2025-48886","markdown":"https://insights.sbomify.com/CVE-2025-48886/index.md","name":"CVE-2025-48886","record":{"aliases":["GHSA-qr9f-mpgf-wp25"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Cardano L2 scaling","requires_auth":"low_privilege","summary":"Hydra node incorrectly assumes L1 event finality, allowing re-org attacks to manipulate state progression and bypass transaction validation.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"Hydra is a layer-two scalability solution for Cardano. Prior to version 0.22.0, the process assumes L1 event finality and does not consider failed transactions. Currently, Cardano L1 is monitored for certain events which are necessary for state progression. At the moment, Hydra considers those events as finalized as soon as they are recognized by the node participants making such transactions the target of re-org attacks. The system does not currently consider the fact that failed transactions on the Cardano L1 can indeed appear in blocks because these transactions are so infrequent. This issue has been patched in version 0.22.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"hydra-node dangerously assumes L1 event finality and does not consider failed transactions","id":"CVE-2025-48886","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"vLLM has a Regular Expression Denial of Service (ReDoS, Exponential Complexity) Vulnerability in `pythonic_tool_parser.py`","id":"CVE-2025-48887"},"packages":[],"prev":{"headline":"application-urlshortener users can create arbitrary pages as long as they have view access to them","id":"CVE-2025-48885"},"products":["hydra"],"published":"2025-06-19","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-23","vendors":["cardano-scaling"]},"summary":"Hydra node incorrectly assumes L1 event finality, allowing re-org attacks to manipulate state progression and bypass transaction validation.","url":"https://insights.sbomify.com/CVE-2025-48886/"}