CVE-2026-42865Network attack vector

Cross-account email disclosure via shared Redis listener

Published May 11, 2026 · Updated May 11, 2026

Information disclosure in Inbox Zero before 2.29.3 allows remote authenticated users to receive another account's cleaner thread events. The cleaner email stream endpoint reused a shared Redis subscription listener instead of isolating each server-sent event stream by account, so concurrent subscribers received events belonging to another account. Exposure requires two mutually untrusted authenticated accounts to use the early-access cleaner concurrently; self-hosted deployments are unaffected unless the disabled-by-default cleaner is enabled.

CVSS severity2.3
Low
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Inbox Zero before 2.29.3 allows remote authenticated users to receive another account's cleaner thread events. The cleaner email stream endpoint reused a shared Redis subscription listener instead of isolating each server-sent event stream by account, so concurrent subscribers received events belonging to another account. Exposure requires two mutually untrusted authenticated accounts to use the early-access cleaner concurrently; self-hosted deployments are unaffected unless the disabled-by-default cleaner is enabled.

The record

CVE
CVE-2026-42865
Published
May 11, 2026
Updated
May 11, 2026
Vendor
Inbox Zero Inc.
Product
Inbox Zero
Classifications
CWE-200, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. May 11, 2026CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.29.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Inbox Zero Inc. · Inbox Zeroversion=< 2.29.3

Published CVSS scores

4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
2.3GitHub, Inc.CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo