# CVE-2026-44262: Scramble: Remote code execution via evaluation of user-controlled input in validation rules

> Attackers can execute arbitrary PHP code if documentation endpoints are public and validation rules process user input.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-4rm2-28vj-fj39

## What is CVE-2026-44262?

CVE-2026-44262 is a critical code injection vulnerability in dedoc scramble, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Scramble generates API documentation for Laravel project. From 0.13.2 to before 0.13.22, when documentation endpoints are publicly accessible and validation rules reference user-controlled input, request supplied data may be evaluated during documentation generation, leading to execution of arbitrary PHP code in the application context. This vulnerability is fixed in 0.13.22.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

2 open source packages ship an affected version, including dedoc/scramble.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dedoc/scramble` | Packagist | From 0.13.2 | 0.13.22 |
| `dedoc/scramble` | Packagist | From 0.13.2 | 0.13.22 |

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

Upgrade dedoc/scramble to 0.13.22 or later.

## Is CVE-2026-44262 being exploited?

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

Public exploit code:

- Unauthenticated RCE in dedoc/scramble — PoC, Nmap NSE & Nuclei template. (github_poc): https://github.com/joshuavanderpoll/CVE-2026-44262
- scramble - Remote Code Execution (exploitdb)
- https://github.com/akash-osmsec/CVE-2026-44262- (github_poc): https://github.com/akash-osmsec/CVE-2026-44262-
- Scramble Laravel - Remote Code Execution (nuclei): http/cves/2026/CVE-2026-44262.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44262 is a critical code injection vulnerability in dedoc scramble, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44262 exists.

Affected packages and fixed versions:
- dedoc/scramble (Packagist): affected from 0.13.2; fixed in 0.13.22
- dedoc/scramble (Packagist): affected from 0.13.2; fixed in 0.13.22

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-44262/ (Markdown: https://insights.sbomify.com/CVE-2026-44262/index.md)
```

## Sources

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

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