{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9116 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9116 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9116 is a high-severity vulnerability in n/a, published on 25 Feb 2019. 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-2019-9116 and fix it if it is affected.\n\nWhat it is: CVE-2019-9116 is a high-severity vulnerability in n/a, published on 25 Feb 2019. 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: There is no known exploitation of CVE-2019-9116 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-2019-9116/ (Markdown: https://insights.sbomify.com/CVE-2019-9116/index.md)","id":"CVE-2019-9116","markdown":"https://insights.sbomify.com/CVE-2019-9116/index.md","name":"CVE-2019-9116","record":{"aliases":["GHSA-4p9g-444m-88pg"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Sublime Text editor","requires_auth":"none","summary":"Attackers can execute arbitrary code via DLL hijacking when victims open text files from a specific temporary directory in Sublime Text.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sublime_text_3","vendor":"sublimetext"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"DLL hijacking is possible in Sublime Text 3 version 3.1.1 build 3176 on 32-bit Windows platforms because a Trojan horse api-ms-win-core-fibers-l1-1-1.dll or api-ms-win-core-localization-l1-2-1.dll file may be loaded if a victim uses sublime_text.exe to open a .txt file within an attacker's %LOCALAPPDATA%\\Temp\\sublime_text folder. NOTE: the vendor's position is \"This does not appear to be a bug with Sublime Text, but rather one with Windows that has been patched.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2019-9116","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2019-9117"},"packages":[],"prev":{"headline":"irisnet-crypto RCE Vulnerability","id":"CVE-2019-9115"},"products":["n/a"],"published":"2019-02-25","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-65741","kev_date_added":null,"published":"2025-12-09"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2017-8368","kev_date_added":null,"published":"2017-07-05"}],"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":"Attackers can execute arbitrary code via DLL hijacking when victims open text files from a specific temporary directory in Sublime Text.","url":"https://insights.sbomify.com/CVE-2019-9116/"}