{"answers":{"affected":"2 open source packages ship an affected version, including matrix-js-sdk.","exploited":"There is no known exploitation of CVE-2025-59160 in the wild and no public exploit code.","fix":"Upgrade matrix-js-sdk to 38.2.0 or later.","what":"CVE-2025-59160 is a low-severity vulnerability in matrix-org matrix-js-sdk, published on 16 Sep 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-59160 and fix it if it is affected.\n\nWhat it is: CVE-2025-59160 is a low-severity vulnerability in matrix-org matrix-js-sdk, published on 16 Sep 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-59160 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- matrix-js-sdk (npm): affected all versions; fixed in 38.2.0\n- matrix-js-sdk (npm): affected all versions; fixed in 38.2.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-59160/ (Markdown: https://insights.sbomify.com/CVE-2025-59160/index.md)","id":"CVE-2025-59160","markdown":"https://insights.sbomify.com/CVE-2025-59160/index.md","name":"CVE-2025-59160","record":{"aliases":["DEBIAN-CVE-2025-59160","GHSA-mp7c-m3rh-r56v","UBUNTU-CVE-2025-59160"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Matrix JavaScript SDK","requires_auth":"none","summary":"Attackers can replace tombstoned rooms with unrelated rooms due to insufficient validation, potentially misleading clients about room history.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Matrix JavaScript SDK is a Matrix Client-Server SDK for JavaScript and TypeScript. matrix-js-sdk before 38.2.0 has insufficient validation of room predecessor links in MatrixClient::getJoinedRooms, allowing a remote attacker to attempt to replace a tombstoned room with an unrelated attacker-supplied room. The issue has been patched and users should upgrade to 38.2.0. A workaround is to avoid using MatrixClient::getJoinedRooms in favor of getRooms() and filtering upgraded rooms separately.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"matrix-js-sdk has insufficient validation when considering a room to be upgraded by another","id":"CVE-2025-59160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Business logic in element-web","id":"CVE-2025-59161"},"packages":[{"ecosystem":"npm","fixed":["38.2.0"],"introduced":["0"],"last_affected":[],"package":"matrix-js-sdk","purl":null,"source":"GHSA-mp7c-m3rh-r56v"},{"ecosystem":"npm","fixed":["38.2.0"],"introduced":["0"],"last_affected":[],"package":"matrix-js-sdk","purl":"pkg:npm/matrix-js-sdk","source":"GHSA-mp7c-m3rh-r56v"}],"prev":{"headline":"SillyTavern Web Interface Vulnerable to DNS Rebinding","id":"CVE-2025-59159"},"products":["matrix-js-sdk"],"published":"2025-09-16","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-16","vendors":["matrix-org"]},"summary":"Attackers can replace tombstoned rooms with unrelated rooms due to insufficient validation, potentially misleading clients about room history.","url":"https://insights.sbomify.com/CVE-2025-59160/"}