Code Injection in dedoc/scramble (CVE-2026-44262)
Summary
Code injection in dedoc/scramble (CVE-2026-44262). Confidential information can be exposed externally. Mitigation: upgrade to 0.13.22 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44262 has been found in dedoc/scramble.
Confidential information can be exposed externally. CVSS score: 9.4/10.
What to do: upgrade dedoc/scramble to 0.13.22 or later.
If unsure, ask your IT team or search "dedoc/scramble CVE-2026-44262" on the vendor's site.
CVE-2026-44262 (dedoc/scramble) — CWE-94 / CVSS v3 9.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.13.22 — apply immediately
Workaround: * Restrict access to documentation endpoints (/docs/api, `/docs/api.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in dedoc/scramble.
Check the vendor advisory for the affected versions of dedoc/scramble.
Severity: Critical (CVSS 9.4/10). Confidential information can be exposed externally.
Update to 0.13.22.
Workaround: * Restrict access to documentation endpoints (/docs/api, `/docs/api.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'dedoc/scramble' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dedoc/scramble' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dedoc/scrambleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
* Restrict access to documentation endpoints (`/docs/api`, `/docs/api.パッチが適用されるまでの応急処置として、* Restrict access to documentation endpoints (
/docs/api, `/docs/api. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade dedoc/scramble to 0.13.22ステージング環境で 0.13.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com