Vulnerability in py7zr (CVE-2026-55195)
Summary
Vulnerability in py7zr (CVE-2026-55195). Risk of unauthorized operations or information disclosure. Exploitable via zipfile. Mitigation: upgrade to 1.1.3 or later.
Original description
The description as published by the source.
py7zr is a Python-based library and utility to support 7zip archive compression, decompression, encryption and decryption. Prior to 1.1.3, py7zr's Worker.decompress() extracted archive entries without tracking total decompressed size, allowing a crafted .7z file such as a 15.6 KB archive that expands to 100 MB to exhaust disk or memory before extraction completes. This issue is fixed in version 1.1.3.
Source: GitHub Security Advisories (Global) 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-55195 has been found in py7zr.
Attackers can target a specific entry point like zipfile over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade py7zr to 1.1.3 or later.
If unsure, ask your IT team or search "py7zr CVE-2026-55195" on the vendor's site.
CVE-2026-55195 (py7zr) — CWE-409
Attack surface: zipfile / max_size
Patched: 1.1.3 — 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.
A vulnerability (CWE-409) exists in py7zr. Attackers reach the vulnerable code path via zipfile.
Check the vendor advisory for the affected versions of py7zr. Attack surface: zipfile / max_size.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.1.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'py7zr' . 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 'py7zr' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
py7zrを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade py7zr to 1.1.3ステージング環境で 1.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-55195 py7zr
- Ubuntu UBUNTU-CVE-2026-55195 py7zr
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com