{"answers":{"affected":"2 open source packages ship an affected version, including @bsv/sdk.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69287 exists.","fix":"Upgrade @bsv/sdk to 2.0.0 or later.","what":"CVE-2025-69287 is a medium-severity authentication bypass vulnerability in bsv-blockchain ts-sdk, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-69287 and fix it if it is affected.\n\nWhat it is: CVE-2025-69287 is a medium-severity authentication bypass vulnerability in bsv-blockchain ts-sdk, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, 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-69287 exists.\n\nAffected packages and fixed versions:\n- @bsv/sdk (npm): affected all versions; fixed in 2.0.0\n- @bsv/sdk (npm): affected all versions; fixed in 2.0.0\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-69287/ (Markdown: https://insights.sbomify.com/CVE-2025-69287/index.md)","id":"CVE-2025-69287","markdown":"https://insights.sbomify.com/CVE-2025-69287/index.md","name":"CVE-2025-69287","record":{"aliases":["GHSA-vjpq-xx5g-qvmm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"BSV Blockchain SDK","requires_auth":"none","summary":"Incorrect signature data preparation in the BSV Blockchain SDK allows attackers to bypass mutual authentication checks between peers.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-573","name":"Improper Following of Specification by Caller"}],"description":"The BSV Blockchain SDK is a unified TypeScript SDK for developing scalable apps on the BSV Blockchain. Prior to version 2.0.0, a cryptographic vulnerability in the TypeScript SDK's BRC-104 authentication implementation caused incorrect signature data preparation, resulting in signature incompatibility between SDK implementations and potential authentication bypass scenarios. The vulnerability was located in the `Peer.ts` file of the TypeScript SDK, specifically in the `processInitialRequest` and `processInitialResponse` methods where signature data is prepared for BRC-104 mutual authentication. The TypeScript SDK incorrectly prepared signature data by concatenating base64-encoded nonce strings (`message.initialNonce + sessionNonce`) then decoding the concatenated base64 string (`base64ToBytes(concatenatedString)`). This produced ~32-34 bytes of signature data instead of the correct 64 bytes. BRC-104 authentication relies on cryptographic signatures to establish mutual trust between peers. When signature data preparation is incorrect, signatures generated by the TypeScript SDK don't match those expected by Go/Python SDKs; cross-implementation authentication fails; and an attacker could potentially exploit this to bypass authentication checks. The fix in version 2.0.0 ensures all SDKs now produce identical cryptographic signatures, restoring proper mutual authentication across implementations.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"BSV Blockchain SDK has an Authentication Signature Data Preparation Vulnerability","id":"CVE-2025-69287","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Titra has Remote Code Execution in Admin Functionality","id":"CVE-2025-69288"},"packages":[{"ecosystem":"npm","fixed":["2.0.0"],"introduced":["0"],"last_affected":[],"package":"@bsv/sdk","purl":null,"source":"GHSA-vjpq-xx5g-qvmm"},{"ecosystem":"npm","fixed":["2.0.0"],"introduced":["0"],"last_affected":[],"package":"@bsv/sdk","purl":"pkg:npm/%40bsv/sdk","source":"GHSA-vjpq-xx5g-qvmm"}],"prev":{"headline":"RAGFlow has Predictable Token Generation Leading to Authentication Bypass Vulnerability","id":"CVE-2025-69286"},"products":["ts-sdk"],"published":"2026-02-18","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-18","vendors":["bsv-blockchain"]},"summary":"Incorrect signature data preparation in the BSV Blockchain SDK allows attackers to bypass mutual authentication checks between peers.","url":"https://insights.sbomify.com/CVE-2025-69287/"}