CVE-2026-5463: pymetasploit3 vulnerable to command injection
Affects pymetasploit3Source GCVE Database
Not known to be exploited · CVSS 9.3 Critical.
Data as of 16 Nov 2026, 16:36 UTC
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 3 Apr 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 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIpymetasploit3 | 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
Users should avoid using vulnerable versions (<=1.0.6) of pymetasploit3. Monitor the vendor or project repository for updates or official patches addressing this vulnerability. Until a fix is available, restrict access to environments running pymetasploit3 and avoid passing untrusted input to console.run_module_with_output().
Description
pymetasploit3 versions up to 1.0.6 contain a command injection vulnerability in the console.run_module_with_output() function. This flaw allows attackers to inject newline characters into module options like RHOSTS, disrupting the command structure and causing the Metasploit console to execute unintended commands. This can lead to arbitrary command execution and manipulation of Metasploit sessions.