CVE-2026-33156: NickeManarin ScreenToGif · Untrusted Search Path
Affects NickeManarin ScreenToGifSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NickeManarinScreenToGif | Affected
| Fixed in– |
GitHubnickemanarin/ScreenToGifpkg:github/nickemanarin/ScreenToGifOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-33156, organizations should implement the following specific measures: 1) Restrict execution of portable applications like ScreenToGif from user-writable directories by enforcing application whitelisting or using AppLocker/Windows Defender Application Control policies to allow execution only from trusted locations such as Program Files or system directories. 2) Educate users to avoid running portable executables from untrusted or shared folders and to report suspicious files. 3) Regularly audit directories where users commonly run portable apps for unauthorized DLL files, especially version.dll, and remove any suspicious files. 4) Employ endpoint detection and response (EDR) solutions to monitor for anomalous DLL loading behaviors and execution of ScreenToGif from unusual paths. 5) Isolate or sandbox user environments where portable apps are necessary to limit potential damage. 6) Monitor vendor communications for patches or updates addressing this vulnerability and apply them promptly once available. 7) Consider alternative screen recording tools with secure DLL loading practices until a fix is released.
Description
ScreenToGif is a screen recording tool. In versions from 2.42.1 and prior, ScreenToGif is vulnerable to DLL sideloading via version.dll . When the portable executable is run from a user-writable directory, it loads version.dll from the application directory instead of the Windows System32 directory, allowing arbitrary code execution in the user's context. This is especially impactful because ScreenToGif is primarily distributed as a portable application intended to be run from user-writable locations. At time of publication, there are no publicly available patches.