How severe is CVE-2026-44262?

CVE-2026-44262 has a CVSS score of 9.4/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-44262?

CVE-2026-44262 affects the following packages: dedoc/scramble (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-44262?

Update dedoc/scramble to 0.13.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44262 is resolved across your whole dependency graph.

How do I detect CVE-2026-44262 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dedoc/scramble, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-44262 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2026-44262 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2026-44262, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2026-44262?

CVE-2026-44262 has an EPSS (Exploit Prediction Scoring System) score of 5.9%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-44262?

CVE-2026-44262 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2026-44262?

A Nuclei detection template exists for CVE-2026-44262, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-44262 published, and has it been updated?

CVE-2026-44262 was published on May 12, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2026-44262 — scramble

CRITICAL

CVE-2026-44262 is a critical-severity (CVSS 9.4) Code Injection vulnerability in dedoc/scramble. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for dedoc/scramble — see the affected versions and patch details below.

Scramble: Remote code execution via evaluation of user-controlled input in validation rules

Also known asGHSA-4rm2-28vj-fj39

Published

May 12, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44262.

EPSS Exploitation Probability

via FIRST.org ↗

5.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘dedoc/scramble

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A remote code execution (RCE) vulnerability affects versions 0.13.2 through 0.13.21. 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.

Patches

Fixed in version 0.13.22.

Workarounds

If upgrading is not immediately possible:

Restrict access to documentation endpoints (/docs/api, /docs/api.json)
Avoid using user-controlled variables inside validation rule expressions (e.g., values derived from request input)
Disable documentation endpoints in production environments if not required

These measures significantly reduce or prevent exploitability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`dedoc/scramble`	≥ 0.13.2&&< 0.13.22	0.13.22`composer require dedoc/scramble:^0.13.22`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52582webappsphp

scramble - Remote Code Execution

by joshua · May 27, 2026

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dedoc/scramble, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dedoc/scramble to 0.13.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44262 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2026-44262

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2026-44262 -u https://target

Template: Scramble Laravel - Remote Code Execution
Severity: critical
Impact: Remote attackers can execute arbitrary PHP code, potentially leading to full application compromise.
Remediation: Upgrade to version 0.13.22 or later.

Template by ProjectDiscovery nuclei-templates (joshuavanderpoll), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact A remote code execution (RCE) vulnerability affects versions `0.13.2` through `0.13.21`. 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. ### Patches Fixed in version `0.13.22`. ### Workarounds If upgrading is not immediately possible: * Restrict access to documentation endpoints (`/docs/api`, `/docs/api.json`) * Avoid using user-controlled variables inside validation rule expres