Loading story…
Bulwark Webmail, the self-hosted webmail client for Stalwart Mail Server, patched two high-severity vulnerabilities in version 1.4.10. CVE-2026-34833 exposed users' plaintext passwords because the GET /api/auth/session endpoint returned the password in a JSON response, creating a risk of credential leakage through browser logs, local caches, and network proxies. The issue was classified as CWE-312 and carries a high confidentiality impact.
A second flaw, CVE-2026-34834, allowed authentication bypass in the verifyIdentity() function because missing session cookies were not properly validated. In affected versions before 1.4.10, an unauthenticated attacker could send arbitrary headers and gain access to or modify user settings through the /api/settings endpoint. The vulnerability was classified as CWE-287, and GitHub security advisories published references to both the advisory and the patch release.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
On April 2, 2026, CVE entries were published for two Bulwark Webmail vulnerabilities: CVE-2026-34833 for plaintext password disclosure and CVE-2026-34834 for authentication bypass due to missing cookie validation. The advisories described the affected versions, impact, and references to the patch release.
Bulwark Webmail version 1.4.10 fixed two vulnerabilities affecting earlier releases: plaintext password exposure via GET /api/auth/session and an authentication bypass in verifyIdentity() that could enable unauthorized access to /api/settings. The fixes addressed credential leakage and missing session cookie validation in versions prior to 1.4.10.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Multiple severe vulnerabilities in **SmarterMail** exposed internet-facing mail servers to compromise, including `CVE-2025-52691`, an unauthenticated arbitrary file upload flaw that can lead to immediate remote code execution, and `CVE-2026-23760`, an authentication bypass tied to the password reset API. Public reporting said `CVE-2025-52691` affected **Build 9406 and earlier**, carried a **CVSS 10.0** rating, and allowed attackers with network access to place files in arbitrary server locations and execute code with the privileges of the SmarterMail service. Advisories from Censys highlighted both issues, while a public GitHub proof-of-concept for `CVE-2026-23760` increased the risk of opportunistic exploitation. SmarterTools reportedly fixed the file upload vulnerability in **Build 9413**, with later builds available afterward, and security reporting warned that successful compromise of a mail gateway could expose customer email, credentials, and connected backend systems. The flaws were described as especially dangerous for hosting providers and organizations running exposed SmarterMail instances because they enable unauthenticated access paths that can quickly escalate to full server compromise.
Jun 29, 2026
SmarterTools *SmarterMail* patched a critical authentication bypass tracked as **WT-2026-0001** after researchers reported that attackers can reset the **system administrator** password without authentication by abusing the `/api/v1/auth/force-reset-password` endpoint. The flaw stems from logic in `SmarterMail.Web.Api.AuthenticationController.ForceResetPassword` that permits anonymous access and trusts a user-supplied boolean (`IsSysAdmin`); when set to `true`, the code path updates an admin account’s password without validating the old password or enforcing authorization checks. Both reporting indicate the issue is **actively exploited in the wild**, with observed exploitation occurring **within days of the vendor patch** (including reports of activity as soon as two days after release). Once an attacker resets the admin password, they can take over the mail server and leverage built-in administrative capabilities to execute OS commands, effectively achieving **remote code execution (RCE)** and full compromise of affected SmarterMail deployments; the patch was released as **Build 9511** following responsible disclosure by watchTowr Labs researchers **Piotr Bazydlo** and **Sina Kheirkhah**.
Jun 29, 2026
**watchTowr Labs** disclosed **WT-2026-0001**, an **authentication bypass** in *SmarterTools SmarterMail* that allows a user to reset the **system administrator password** via a password-reset mechanism and then leverage SmarterMail’s built-in “RCE-as-a-feature” capabilities to execute OS commands. The researcher reported the issue and stated it was patched quickly, citing a fixed release on **SmarterMail release 9511 (2026-01-15)**; the publication was accelerated after a tip that attackers were actively exploiting the flaw to reset admin passwords, with forum-shared logs reportedly showing suspicious activity tied to the `force-reset-password` endpoint. **Resecurity** reported exploitation of **CVE-2026-22794** in *Appsmith*, a critical authentication weakness in the password reset flow where the application trusts a **client-controlled `Origin` header** to build reset links. An attacker can initiate a reset for a victim while supplying a malicious Origin so the victim’s email contains a link to attacker infrastructure; when clicked, the reset token is exposed, enabling password change and **full account takeover**. Resecurity identified the affected endpoint as `/api/v1/users/forgotPassword`, stated **Appsmith ≤ 1.92** is affected, and that the issue is fixed in **Appsmith ≥ 1.93**.
Jun 29, 2026