{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49450 exists.","fix":"No fix has been published for CVE-2026-49450 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49450 is a high-severity code injection vulnerability in laurent22 joplin, published on 21 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-49450 and fix it if it is affected.\n\nWhat it is: CVE-2026-49450 is a high-severity code injection vulnerability in laurent22 joplin, published on 21 Sep 2026. It can only be exploited from the same machine or local 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-2026-49450 exists.\n\nAffected product: laurent22 joplin. 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-49450/ (Markdown: https://insights.sbomify.com/CVE-2026-49450/index.md)","id":"CVE-2026-49450","markdown":"https://insights.sbomify.com/CVE-2026-49450/index.md","name":"CVE-2026-49450","record":{"aliases":["GHSA-9wp7-hr9m-3273"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Joplin desktop app","requires_auth":"none","summary":"Attackers can execute arbitrary code by supplying a maliciously signed or unsigned update installer due to missing publisher verification in the auto-updater.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-494","name":"Download of Code Without Integrity Check"},{"id":"CWE-353","name":"Missing Support for Integrity Check"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.7.2, Joplin Desktop for Windows omits publisherName from packages/app-desktop/package.json, so the generated app-update.yml causes NsisUpdater.verifySignature() to skip comparison of a downloaded update's Authenticode signer with Joplin's signer. An attacker who controls the update delivery path can replace the update metadata and installer, and the client accepts an installer signed by another publisher or left unsigned after the user approves installation. Successful exploitation runs attacker-controlled code with the user's privileges and can compromise notes, credentials, and local data. This issue is fixed in version 3.7.2.","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":"Code injection in joplin","id":"CVE-2026-49450","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Microsoft.OpenAPI: Circular schema references may terminate OpenAPI parsing","id":"CVE-2026-49451"},"packages":[],"prev":{"headline":"Joplin: KaTeX `trust:true` enables URL-allowlist bypass leading to NTLMv2 credential theft via UNC path on Windows","id":"CVE-2026-49449"},"products":["joplin"],"published":"2026-09-21","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":"total"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["laurent22"]},"summary":"Attackers can execute arbitrary code by supplying a maliciously signed or unsigned update installer due to missing publisher verification in the auto-updater.","url":"https://insights.sbomify.com/CVE-2026-49450/"}