dbcve.org
WebmailApplication · Bulwarkmail

CVE-2026-34833

HIGH · 7.5 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to 1.4.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Bulwark Webmail is a self-hosted webmail client for Stalwart Mail Server. Prior to version 1.4.10, the GET /api/auth/session endpoint previously included the user's plaintext password in the JSON response. This exposed credentials to browser logs, local caches, and network proxie. This issue has been patched in version 1.4.10.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GET /api/auth/session endpoint in Bulwark Webmail (a webmail client for Stalwart Mail Server) versions prior to 1.4.10 returned user passwords in plaintext within the JSON response, exposing credentials to browser developer tools, local caches, and any network intercepting proxies.

MitigationUpgrade to Bulwark Webmail version 1.4.10 or later. Additionally, instruct users to rotate passwords that may have been exposed, as the plaintext credentials were logged or cached in multiple locations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WebmailApplication
Affected:< 1.4.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Bulwark Webmail is installed
    Locate the Bulwark Webmail application in your environment using package managers, deployment directories, or running services
    Affected if Bulwark Webmail is present on the system
  2. Check the installed version
    Determine the version of Bulwark Webmail using package metadata, application headers, or the version file within the deployment
    Affected if The version is below 1.4.10
  3. Verify the API endpoint is accessible
    Confirm the GET /api/auth/session endpoint is reachable (requires authentication first if your deployment protects it)
    Affected if The endpoint responds to authenticated requests
  4. Inspect the API response for plaintext password
    Send an authenticated GET request to /api/auth/session and examine the JSON response body for the password field containing plaintext credentials
    Affected if The response includes the user's password in plaintext

The environment is affected if Bulwark Webmail version is below 1.4.10 and the /api/auth/session endpoint returns plaintext passwords in its response.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.10 or later
Fixed in 1.4.10
Interim mitigation

Upgrade to Bulwark Webmail version 1.4.10 or later. Additionally, instruct users to rotate passwords that may have been exposed, as the plaintext credentials were logged or cached in multiple locations.

Recommended fix High confidence

1.4.10

  1. Identify the current version of Bulwark Webmail installed by checking the application or configuration files
  2. Backup the current Webmail installation, configuration, and any user data
  3. Upgrade Bulwark Webmail to version 1.4.10 or later using the appropriate installation method (package manager, Docker, or manual update)
  4. Verify the upgrade was successful by checking the application version
  5. Test the GET /api/auth/session endpoint to confirm the plaintext password is no longer exposed in the JSON response
  6. Review browser logs, caching systems, and network proxies to ensure no cached responses with plaintext passwords remain

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Webmail Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34833 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34833 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data