Quick answers
- Is CVE-2026-93533 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93533 being exploited in the wild.
- How severe is CVE-2026-93533?
- Medium severity, with a CVSS score of 6.3, published 18 September 2026.
- Which products and versions are affected?
- Spatie Scotty up to 1.4.4.
- Is there a fix for CVE-2026-93533?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-93533 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-93533?
- Check whether you run Spatie Scotty at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The DoctorCommand::checkSshConnectivity() and DoctorCommand::checkRemoteTools() methods directly interpolate unsanitized host values from the @servers configuration directive into shell command strings and execute them via Process::fromShellCommandline(), allowing OS command injection via shell metacharacters. The vulnerability requires the victim to run scotty doctor against an attacker-influenced configuration file (e.g., from a malicious repository or via --conf/--path argument pointing to attacker-controlled content). A fix is pending in a pull request awaiting acceptance.
Affected products
- Spatie Scotty up to 1.4.4
Timeline
- 2026-09-18: disclosed: Vulnerability published to NVD