pymetasploit3 vulnerable to command injection in console.run_module_with_output()

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L · score source

EPSS

• CVE-2026-5463: 2.15% estimated exploitation activity in the next 30 days; percentile 82.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Command injection vulnerability in console.runmodulewithoutput() in pymetasploit3 through version 1.0.6 allows attackers to inject newline characters into module options such as RHOSTS. This breaks the intended command structure and causes the Metasploit console to execute additional unintended commands, potentially leading to arbitrary command execution and manipulation of Metasploit sessions.

Published by the source

3 Apr 2026, 06:31 UTC

Last modified by the source

29 Jun 2026, 12:26 UTC

Source last checked

26 Oct 2026, 13:45 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qpc3-8vqg-8g6w

2. Revision 3 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-qpc3-8vqg-8g6w

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-qpc3-8vqg-8g6w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-5463

Advisory: pymetasploit3 vulnerable to command injection in console.run_module_with_output()
IDs: CVE-2026-5463, GHSA-qpc3-8vqg-8g6w
Record: https://patchnext.com/advisories/cve-2026-5463 (revision 4, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pymetasploit3: affected <= 1.0.6

## Suggested inspection (read-only)
- `python -m pip show pymetasploit3`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pymetasploit3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qpc3-8vqg-8g6w (GitHub-reviewed advisory GHSA-qpc3-8vqg-8g6w lists affected ranges: PyPI pymetasploit3 >=0 <=1.0.6)
- Verified: https://osv.dev/vulnerability/GHSA-qpc3-8vqg-8g6w (OSV record GHSA-qpc3-8vqg-8g6w lists affected ranges: PyPI pymetasploit3 >=0 <=1.0.6)

Commands are suggestions: review each one before running it.