Quick answers
- Is CVE-2026-35391 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35391 being exploited in the wild.
- How severe is CVE-2026-35391?
- High severity, with a CVSS score of 7.5, published 6 April 2026.
- Which products and versions are affected?
- Bulwark Webmail < 1.4.11.
- Is there a fix for CVE-2026-35391?
- A patch was published on 2026-04-06: Fixed in version 1.4.11 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35391 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-35391?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in the getClientIP() function within lib/admin/session.ts of Bulwark Webmail. The application incorrectly trusts the leftmost entry of the X-Forwarded-For HTTP header, which is entirely client-controlled. By providing a forged IP address in this header, a remote attacker can bypass IP-based rate limiting mechanisms, facilitating brute-force attacks against the administrative login interface. Additionally, this allows for the forgery of audit log entries, masking the true origin of malicious activity. The issue is resolved in version 1.4.11 by switching to rightmost header parsing and introducing a configurable trusted proxy depth.
Affected products
- Bulwark Webmail < 1.4.11
Timeline
- 2026-04-02: advisory: GitHub Security Advisory published
- 2026-04-06: disclosed: CVE published
- 2026-04-06: patched: Fixed in version 1.4.11