A vulnerability was identified in spatie Scotty up to 1.4.2. Affected is the function SelfUpdater::update of the file app/Updater/SelfUpdater.php of the component Self Update Handler. Such manipulation leads to download of code without integrity check. It is possible to launch the attack remotely. Upgrading to version 1.4.3 is able to address this issue. The name of the patch is 4b4e11bfc98e3a2159bb2b3d9b040293fcc44744. It is advisable to upgrade the affected component.
CVE-2026-93534
Score 6.3 from GitHub Security Advisory published 2026-09-18. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 59(Attend)EG Risk 59/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (4)
Auto-updated Sep 18, 2026GitHub - spatie/scotty: A beautiful SSH task runner · GitHub
https://github.com/spatie/scotty/1.4.3
Patch available: spatie/scotty 1.4.3
https://github.com/spatie/scotty/releases/tag/1.4.3commit 4b4e11bfc98e (spatie/scotty)
Patch available: spatie/scotty 1.4.3 (contains commit 4b4e11bfc98e)
https://github.com/spatie/scotty/commit/4b4e11bfc98e3a2159bb2b3d9b040293fcc44744self-update replaces phar without integrity/signature verification (CWE-494) · Issue #21 · spatie/scotty · GitHub
https://github.com/spatie/scotty/issues/21Vendor Advisories for CVE-2026-93534(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:27 UTCEG score recompute
- 2026-09-18 19:27 UTCGHSA enrichment
- 2026-09-18 18:27 UTCEG score recompute
- 2026-09-18 17:19 UTCEG score recompute
- 2026-09-18 16:39 UTCEG score recompute
- 2026-09-18 16:39 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-93534?
When was CVE-2026-93534 disclosed?
What is the CVSS score of CVE-2026-93534?
How do I remediate CVE-2026-93534?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93534
Is Your Infrastructure Affected by CVE-2026-93534?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.