← Back
ROOT-APP-PYPI-CVE-2026-33123
Vulnerability in rootio-pypdf (ROOT-APP-PYPI-CVE-2026-33123)
Summary
vulnerability in rootio-pypdf (ROOT-APP-PYPI-CVE-2026-33123). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `6.6.0+root.io.5, 6.6.0+root.io.6, 6.6.0+root.io.7, 6.6.0+root.io.8, 6.6.0+root.io.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **ROOT-APP-PYPI-CVE-2026-33123** has been found in rootio-pypdf.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade rootio-pypdf to **6.6.0+root.io.5, 6.6.0+root.io.6, 6.6.0+root.io.7, 6.6.0+root.io.8, 6.6.0+root.io.9** or later.
If unsure, ask your IT team or search "rootio-pypdf ROOT-APP-PYPI-CVE-2026-33123" on the vendor's site.
ROOT-APP-PYPI-CVE-2026-33123 (rootio-pypdf) —
Patched: `6.6.0+root.io.5, 6.6.0+root.io.6, 6.6.0+root.io.7, 6.6.0+root.io.8, 6.6.0+root.io.9` — apply immediately
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
**A vulnerability** (unclassified) exists in rootio-pypdf.
📍 Affected scope
rootio-pypdf — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.6.0+root.io.5, 6.6.0+root.io.6, 6.6.0+root.io.7, 6.6.0+root.io.8, 6.6.0+root.io.9**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'rootio-pypdf' .` 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 'rootio-pypdf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `rootio-pypdf` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade rootio-pypdf to 6.6.0+root.io.5, 6.6.0+root.io.6, 6.6.0+root.io.7, 6.6.0+root.io.8, 6.6.0+root.io.9ステージング環境で 6.6.0+root.io.5, 6.6.0+root.io.6, 6.6.0+root.io.7, 6.6.0+root.io.8, 6.6.0+root.io.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Root:PyPI
rootio-pypdf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0+root.io.5"},{"fixed":"6.6.0+root.io.6"},{"fixed":"6.6.0+root.io.7"},{"fixed":"6.6.0+root.io.8"},{"fixed":"6.6.0+root.io.9"}]}]
Root:PyPI
pypdf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0+aikido.7"},{"fixed":"6.6.0+aikido.8"},{"fixed":"6.6.0+aikido.9"}]}]