GHSA-4rm2-28vj-fj39
CRITICALGHSA-4rm2-28vj-fj39 is a critical-severity (CVSS 9.4) Code Injection vulnerability in dedoc/scramble. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-4rm2-28vj-fj39 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Scramble vulnerable to remote code execution via evaluation of user-controlled input in validation rules
Blast Radius
dedoc/scrambleReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | dedoc/scramble | ≥ 0.13.2&&< 0.13.22 | 0.13.22 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
scramble - Remote Code Execution
by joshua · May 27, 2026
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dedoc/scramble. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update dedoc/scramble to 0.13.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rm2-28vj-fj39 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4rm2-28vj-fj39 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-4rm2-28vj-fj39. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4rm2-28vj-fj39 in your dependencies?
O3 detects GHSA-4rm2-28vj-fj39 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.