Skip to main content
VulnerabilityPublished

CVE-2025-63749: pnetlab · Command Injection

Affects pnetlabSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubxunmint/pnetlabpkg:github/xunmint/pnetlabOther threatsAffected
  • =5.3.11
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since no official patches are currently available, European organizations should implement immediate compensating controls. First, restrict network access to pnetlab management interfaces using firewalls or VPNs to limit exposure to trusted users only. Second, apply strict input validation or sanitization on the qemu_options parameter if customization is possible, or disable any unnecessary features that accept user input for QEMU options. Third, monitor logs and network traffic for unusual command execution attempts or anomalies related to pnetlab usage. Fourth, isolate pnetlab environments from production networks to prevent lateral movement in case of compromise. Fifth, maintain up-to-date backups of network configurations and virtual environments to enable rapid recovery. Finally, stay alert for official patches or advisories from pnetlab developers and apply updates promptly once available. Conduct security awareness training for administrators managing pnetlab to recognize and respond to suspicious activities.

Description

pnetlab 5.3.11 is vulnerable to Command Injection via the qemu_options parameter.

References

Community reviews

Loading reviews…