{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26896 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26896 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26896 is a high-severity vulnerability in n/a, published on 21 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-26896 and fix it if it is affected.\n\nWhat it is: CVE-2020-26896 is a high-severity vulnerability in n/a, published on 21 Oct 2020. 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-2020-26896 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-26896/ (Markdown: https://insights.sbomify.com/CVE-2020-26896/index.md)","id":"CVE-2020-26896","markdown":"https://insights.sbomify.com/CVE-2020-26896/index.md","name":"CVE-2020-26896","record":{"aliases":[],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["data_read","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Lightning Network Daemon","requires_auth":"none","summary":"A malicious peer can steal intercepted HTLC funds and compromise receiver privacy by exploiting a preimage release logic flaw in LND.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lightning_network_daemon","vendor":"lightning_network_daemon_project"}],"cvss":{"score":8.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"Prior to 0.11.0-beta, LND (Lightning Network Daemon) had a vulnerability in its invoice database. While claiming on-chain a received HTLC output, it didn't verify that the corresponding outgoing off-chain HTLC was already settled before releasing the preimage. In the case of a hash-and-amount collision with an invoice, the preimage for an expected payment was instead released. A malicious peer could have deliberately intercepted an HTLC intended for the victim node, probed the preimage through a colluding relayed HTLC, and stolen the intercepted HTLC. The impact is a loss of funds in certain situations, and a weakening of the victim's receiver privacy.","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":"Business logic in n/a","id":"CVE-2020-26896","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-26897"},"packages":[],"prev":{"headline":"Business logic in n/a","id":"CVE-2020-26895"},"products":["n/a"],"published":"2020-10-21","related":[{"cvss_score":8.6,"headline":"Business logic in n/a","id":"CVE-2021-41593","kev_date_added":null,"published":"2021-10-04"},{"cvss_score":5.3,"headline":"Business logic in n/a","id":"CVE-2020-26895","kev_date_added":null,"published":"2020-10-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A malicious peer can steal intercepted HTLC funds and compromise receiver privacy by exploiting a preimage release logic flaw in LND.","url":"https://insights.sbomify.com/CVE-2020-26896/"}