# CVE-2026-93534: spatie Scotty Self Update SelfUpdater.php update code download

> Remote attackers can execute arbitrary code by exploiting a lack of integrity checks during the self-update process in the Scotty library.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-m88j-9w7j-676j

## What is CVE-2026-93534?

CVE-2026-93534 is a medium-severity code injection vulnerability in spatie Scotty, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2026-93534?


## How do I fix CVE-2026-93534?

No fix has been published for CVE-2026-93534 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93534 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93534 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93534 and fix it if it is affected.

What it is: CVE-2026-93534 is a medium-severity code injection vulnerability in spatie Scotty, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93534 exists.

Affected product: spatie Scotty. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93534/ (Markdown: https://insights.sbomify.com/CVE-2026-93534/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93534
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93534
- OSV: https://osv.dev/vulnerability/CVE-2026-93534

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93534/
Summaries are generated and may contain mistakes; the official description above is the record.