Information Disclosure in Inbox Zero (CVE-2026-42865)
Summary
Vulnerability in Inbox Zero (CVE-2026-42865). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.29.3 or later.
Original description
The description as published by the source.
Inbox Zero is an AI personal assistant for email. Prior to 2.29.3, the cleaner email stream endpoint used a shared Redis subscription listener, which could deliver thread events for one authenticated account to another authenticated account using the cleaner feature at the same time. This vulnerability is fixed in 2.29.3.
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-42865 has been found in Inbox Zero.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade Inbox Zero to 2.29.3 or later.
If unsure, ask your IT team or search "Inbox Zero CVE-2026-42865" on the vendor's site.
CVE-2026-42865 (Inbox Zero) — CWE-200 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.29.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.
Information disclosure (CWE-200) exists in Inbox Zero.
Check the vendor advisory for the affected versions of Inbox Zero.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.29.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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Inbox Zero を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Inbox Zero to 2.29.3ステージング環境で 2.29.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com