Quick answers
- Is CVE-2026-93534 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93534 being exploited in the wild.
- How severe is CVE-2026-93534?
- 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.2.
- Is there a fix for CVE-2026-93534?
- A patch was published on 2026-09-08: Version 1.4.3 released with signature verification Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93534 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-93534?
- 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 vulnerability exists in the SelfUpdater::update function, which lacked cryptographic verification of downloaded PHAR files before installation (CWE-494). An attacker positioned to perform MITM or DNS poisoning could replace the legitimate PHAR with malicious code. The fix (v1.4.3) adds ed25519 signature verification against a public key embedded in the application, so the authenticity of releases is no longer transport-dependent.
Affected products
- Spatie Scotty up to 1.4.2
Timeline
- 2026-09-18: disclosed
- 2026-09-08: patched: Version 1.4.3 released with signature verification