← Back
CVE-2026-44262
critical
CVSS 9.4
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in dedoc/scramble.
📍 Affected scope
dedoc/scramble — .
🔥 Severity
Severity: Critical (CVSS 9.4/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.13.22**.
🛡️ Workaround
Workaround: * Restrict access to documentation endpoints (`/docs/api`, `/docs/api.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
* Restrict access to documentation endpoints (`/docs/api`, `/docs/api.パッチが適用されるまでの応急処置として、* Restrict access to documentation endpoints (`/docs/api`, `/docs/api. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade dedoc/scramble to 0.13.22ステージング環境で 0.13.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
dedoc/scramble
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.13.22"}]}]