dbcve.org
WebmailApplication · Bulwarkmail

CVE-2026-34834

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 verifyIdentity() function contained logic that returned true if no session cookies were present. This allowed unauthenticated attackers to bypass security checks and access/modify user settings via the /api/settings endpoint by providing arbitrary headers. 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

Bulwark Webmail prior to v1.4.10 contains an authentication bypass in the verifyIdentity() function. The function incorrectly returns true when no session cookies are present, allowing unauthenticated attackers to bypass security checks and access the /api/settings endpoint to read or modify user settings by supplying arbitrary HTTP headers.

MitigationUpgrade to Bulwark Webmail version 1.4.10 or later, which patches the flawed verifyIdentity() logic. Until then, consider restricting access to the /api/settings endpoint via network-level controls or web application firewall rules.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Bulwarkmail Webmail is running
    Check running processes, installed packages, or query the web server at the expected URL (e.g., /webmail or /). Look for Bulwarkmail in process lists, package managers, or web server logs.
    Affected if Bulwarkmail Webmail is installed and accessible on the network.
  2. Determine the installed version
    Check the version of Bulwarkmail Webmail by inspecting the package manager (dpkg, rpm, etc.), reading version files in the installation directory, or accessing the web interface version information if exposed in the UI or HTTP headers.
    Affected if The version is below 1.4.10 (e.g., 1.4.9, 1.4.8, etc.).
  3. Verify the /api/settings endpoint is accessible
    Send an HTTP request to the /api/settings endpoint on the server (e.g., GET https://yourserver/api/settings or POST to the same endpoint) and observe if it responds, regardless of authentication status.
    Affected if The endpoint is reachable and responds to requests.
  4. Test for authentication bypass
    Send a request to /api/settings with arbitrary headers but WITHOUT any session cookies (e.g., curl -H "X-Custom-Header: value" https://yourserver/api/settings). If the server responds with user data or allows modification of settings without a valid session, the vulnerability is present.
    Affected if The server returns settings data or accepts changes without valid session cookies.

A defender is affected if Bulwarkmail Webmail version is below 1.4.10 and the /api/settings endpoint can be accessed or manipulated without valid session cookies.

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, which patches the flawed verifyIdentity() logic. Until then, consider restricting access to the /api/settings endpoint via network-level controls or web application firewall rules.

Recommended fix High confidence

version 1.4.10

  1. 1. Check the current running version of Bulwark Webmail
  2. 2. Create a backup of the webmail configuration and any custom settings
  3. 3. Update Bulwark Webmail to version 1.4.10 using your package manager or deployment method (e.g., Docker, binary release, or source compilation)
  4. 4. Restart the webmail service to ensure the new version is loaded
  5. 5. Verify the version is now 1.4.10 and test that authentication is required for /api/settings endpoint

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

Fix this in Webmail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34834 — 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-34834 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