CVE-2026-19958: iatsiuk pptr-mcp · Code Injection
Affects iatsiuk pptr-mcpSource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 14 Nov 2026, 20:44 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 16 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| iatsiukpptr-mcp | Affected
| Fixed in– |
GitHubiatsiuk/pptr-mcppkg:github/iatsiuk/pptr-mcpOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:iatsiuk:pptr-mcp:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should monitor the vendor's communications for updates. Until a patch is released, consider restricting access to the affected component and applying compensating controls to limit exposure. Review usage of the executeCode function and avoid processing untrusted input if possible.
Description
CVE-2026-19958 is a medium severity code injection vulnerability in the iatsiuk pptr-mcp project affecting versions 0.2.0 through 0.2.7. The flaw exists in the executeCode function within src/vm-executor.ts of the execute Tool component. This vulnerability allows remote attackers to inject code. Public exploit code has been released. The vendor has been informed but has not yet responded or issued a fix.