Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-34833: CWE-312: Cleartext Storage of Sensitive Information in bulwarkmail webmail

0
High
VulnerabilityCVE-2026-34833cvecve-2026-34833cwe-312
Published: Thu Apr 02 2026 (04/02/2026, 19:11:39 UTC)
Source: CVE Database V5
Vendor/Project: bulwarkmail
Product: webmail

Description

CVE-2026-34833 is a high-severity vulnerability in Bulwark Webmail versions prior to 1. 4. 10 where the user's plaintext password is exposed in the JSON response of the GET /api/auth/session endpoint. This cleartext storage and transmission of sensitive credentials can lead to credential theft via browser logs, local caches, or network proxies without requiring authentication or user interaction. The vulnerability has been patched in version 1. 4. 10. Organizations using affected versions of Bulwark Webmail should upgrade immediately and review their credential handling policies to prevent exposure. No known exploits are currently reported in the wild, but the ease of exploitation and sensitive data exposure make it a critical risk. This vulnerability primarily affects deployments of Bulwark Webmail, which is a self-hosted webmail client for Stalwart Mail Server.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 19:53:48 UTC

Technical Analysis

CVE-2026-34833 is a vulnerability classified under CWE-312 (Cleartext Storage of Sensitive Information) affecting Bulwark Webmail, a self-hosted webmail client for Stalwart Mail Server. Prior to version 1.4.10, the GET /api/auth/session endpoint returned the user's plaintext password within the JSON response. This design flaw exposes sensitive credentials to multiple attack vectors including browser logs, local caches, and network proxies. Because the password is transmitted in cleartext and included in API responses, any entity with access to network traffic or local machine logs can capture user credentials without requiring authentication or user interaction. The vulnerability has a CVSS 4.0 base score of 8.7, indicating high severity due to network attack vector, low attack complexity, no privileges or user interaction required, and high impact on confidentiality. The flaw was addressed in version 1.4.10 by removing the plaintext password from the API response, thus preventing exposure. While no known exploits have been reported in the wild, the vulnerability represents a significant risk to confidentiality and user account security in affected deployments.

Potential Impact

The primary impact of CVE-2026-34833 is the compromise of user credentials through exposure of plaintext passwords in API responses. This can lead to unauthorized access to user email accounts, potentially allowing attackers to read sensitive communications, impersonate users, and escalate attacks within an organization. Since the password is exposed over the network and stored in browser caches and logs, attackers with network access or local machine access can easily harvest credentials. This undermines the confidentiality and integrity of user accounts and can facilitate further attacks such as phishing, lateral movement, or data exfiltration. Organizations relying on Bulwark Webmail for internal or external communications face increased risk of account compromise and data breaches if running affected versions. The vulnerability does not directly affect availability but can indirectly disrupt operations if accounts are compromised or trust is lost.

Mitigation Recommendations

Organizations should immediately upgrade Bulwark Webmail to version 1.4.10 or later where the vulnerability is patched. In addition, administrators should audit existing logs and caches for exposed credentials and enforce password resets for affected users to mitigate potential compromise. Network traffic should be monitored for suspicious activity indicating credential harvesting attempts. Implementing strict transport layer security (TLS) and ensuring no sensitive data is logged or cached by browsers can reduce exposure. Deploying network segmentation and limiting access to the webmail server can also reduce attack surface. Finally, educating users about the risks of credential exposure and encouraging use of multi-factor authentication (MFA) where possible will help mitigate the impact of stolen credentials.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-30T20:52:53.284Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69cec5aae6bfc5ba1dfbd823

Added to database: 4/2/2026, 7:38:18 PM

Last enriched: 4/2/2026, 7:53:48 PM

Last updated: 4/3/2026, 5:53:01 AM

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses