{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-95624 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-95624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-95624 is a medium-severity vulnerability in tauri-plugin-updater, published on 22 Sep 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-2026-95624 and fix it if it is affected.\n\nWhat it is: CVE-2026-95624 is a medium-severity vulnerability in tauri-plugin-updater, published on 22 Sep 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: There is no known exploitation of CVE-2026-95624 in the wild and no public exploit code.\n\nAffected product: tauri-plugin-updater. 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-2026-95624/ (Markdown: https://insights.sbomify.com/CVE-2026-95624/index.md)","id":"CVE-2026-95624","markdown":"https://insights.sbomify.com/CVE-2026-95624/index.md","name":"CVE-2026-95624","record":{"aliases":["GHSA-rjc6-5hfg-grp9","GHSA-wqjv-7vqv-x3mj"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Tauri updater plugin","requires_auth":"none","summary":"Attackers can bypass updater anti-rollback protections via frontend code, enabling downgrade attacks that may lead to code execution.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JFROG","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"The Tauri updater plugin's 'check' IPC command accepts an allowDowngrades boolean parameter directly from frontend JavaScript code. When set to true, it replaces the version comparator from \"update must be newer\" to \"update must be different.\" Because the default permission set grants allow-check to the webview, any XSS in the app frontend can invoke this command and bypass the only anti-rollback protection the updater offers. Combined with another bug, this enables downgrade attacks without even needing to fake a higher version number.","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":"Tauri framework v2 malicious downgrade via allow_downgrades from frontend code","id":"CVE-2026-95624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Tauri framework v2 missing updater signature version number validation can be exploited into forced downgrade","id":"CVE-2026-95625"},"packages":[],"prev":{"headline":"Tauri framework v2 SSRF Protection Bypass via HTTP Redirects","id":"CVE-2026-95623"},"products":["tauri-plugin-updater"],"published":"2026-09-22","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["Tauri"]},"summary":"Attackers can bypass updater anti-rollback protections via frontend code, enabling downgrade attacks that may lead to code execution.","url":"https://insights.sbomify.com/CVE-2026-95624/"}