← Back
CVE-2026-48156
low
CVSS 3.3
Vulnerability in pypdf (CVE-2026-48156)
Summary
vulnerability in pypdf (CVE-2026-48156). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `6.12.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48156** has been found in pypdf.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade pypdf to **6.12.0** or later.
If unsure, ask your IT team or search "pypdf CVE-2026-48156" on the vendor's site.
CVE-2026-48156 (pypdf) — CWE-834 / CVSS v3 3.3
Attack vector: local / unauthenticated
Patched: `6.12.0` — apply immediately
Workaround: If developers are unable to upgrade their apps immediately, they should consider applying the changes from PR [#3791](https://github.com/py-pdf/pypdf/pull/3791).
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** (CWE-834) exists in pypdf.
📍 Affected scope
pypdf — .
🔥 Severity
Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.12.0**.
🛡️ Workaround
Workaround: If developers are unable to upgrade their apps immediately, they should consider applying the changes from PR [#3791](https://github.com/py-pdf/pypdf/pull/3791).
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '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 'pypdf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pypdf` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
If developers are unable to upgrade their apps immediately, they should consider applying the changes from PR [#3791](https://github.com/py-pdf/pypdf/pull/3791).パッチが適用されるまでの応急処置として、If developers are unable to upgrade their apps immediately, they should consider applying the changes from PR [#3791](https://github.com/py-pdf/pypdf/pull/3791). を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade pypdf to 6.12.0ステージング環境で 6.12.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
pypdf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0"}]}]
PyPI
pypdf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-48156
- package https://github.com/py-pdf/pypdf
- web https://github.com/py-pdf/pypdf/pull/3791
- web https://github.com/py-pdf/pypdf/releases/tag/6.12.0
- web https://github.com/py-pdf/pypdf/security/advisories/GHSA-248m-82v9-q6g6
- web https://github.com/py-pdf/pypdf/commit/507d7c9aa6ea83389b954b9c3c0c528fe5d5da70
- web https://github.com/advisories/GHSA-248m-82v9-q6g6