Out-of-Bounds Write in NanaZip (CVE-2026-44215)
Summary
Out-of-bounds write in NanaZip (CVE-2026-44215). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.0.1698.0 or later.
Original description
The description as published by the source.
NanaZip is an open source file archive. From 5.0.1252.0 to before 6.0.1698.0, a one-byte heap out-of-bounds null write exists in the UFS/UFS2 filesystem image parser in NanaZip. The vulnerability is triggered when opening a crafted UFS filesystem image. The attacker controls the byte offset of the write within a ~254-byte window past the heap allocation boundary. This vulnerability is fixed in 6.0.1698.0.
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-44215 has been found in NanaZip.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: upgrade NanaZip to 6.0.1698.0 or later.
If unsure, ask your IT team or search "NanaZip CVE-2026-44215" on the vendor's site.
CVE-2026-44215 (NanaZip) — CWE-787 / CVSS v3 4.4
Attack vector: local / unauthenticated
Patched: 6.0.1698.0 — 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.
Out-of-bounds write (CWE-787) exists in NanaZip.
Check the vendor advisory for the affected versions of NanaZip.
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.
Update to 6.0.1698.0.
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 'NanaZip' . 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 'NanaZip' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
NanaZipを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade NanaZip to 6.0.1698.0ステージング環境で 6.0.1698.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov