Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker sends email signed with self-signed certificate
-
ExploitBulwark Webmail displays signature as valid
-
ExecutionUser trusts forged sender identity
-
ImpactAttacker executes phishing or fraud attack
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
|
| Exploitation Conditions | Bulwark Webmail versions prior to 1.4.11 with S/MIME signature verification enabled. Attacker sends email signed with self-signed or untrusted certificate. No authentication required; victim must view the email in Bulwark Webmail to be deceived by false signature validity indicator. |
| Impact | The CVSS 4.0 score of 8.7 with vector AV:N/AC:L/PR:N/UI:N reflects the ease of exploitation (network-accessible, low complexity, no authentication or user interaction required) and high integrity impact (VI:H). However, real-world risk requires contextual assessment. The attack is trivially executable by any remote party capable of sending email, requiring only the ability to generate self-signed certificates and craft S/MIME-signed messages. No authentication barriers exist, and exploitation can be fully automated. The technical impact is limited to integrity compromise of email signatures rather than confidentiality breach or system availability, which moderates severity compared to RCE vulnerabilities. SSVC framework considerations indicate this is automatable with integrity impact on end-user trust in signed communications. The vulnerability affects organizations relying on S/MIME signatures for email authenticity verification, particularly in regulated industries where signed email provides non-repudiation. While no public exploit code exists, the attack technique is well-documented in cryptographic literature and requires minimal sophistication. Priority should be high for organizations using Bulwark Webmail in production where users depend on S/MIME signature validation for business-critical communications or compliance workflows. |
| Exploit ScenarioDerived | An attacker generates a self-signed X.509 certificate claiming to represent a trusted entity such as a corporate executive or financial institution. The attacker crafts a phishing email requesting wire transfer authorization or credential disclosure, signs it with the self-signed certificate using standard S/MIME tools, and sends it to Bulwark Webmail users. Recipients see a valid signature indicator in the webmail interface, falsely believing the message originated from the claimed sender and was cryptographically authenticated. The user trusts the signed message and executes the fraudulent request, resulting in financial loss or credential compromise. This attack requires no special access beyond standard email delivery and leverages the broken trust chain validation to bypass the security guarantees S/MIME is designed to provide. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 06, 2026
S/MIME signature verification in Bulwark Webmail prior to 1.4.11 fails to validate certificate trust chains, allowing attackers to forge digitally signed emails using self-signed or untrusted certificates that appear legitimate to recipients. This integrity bypass affects all unauthenticated remote attackers (CVSS:4.0 AV:N/AC:L/PR:N) with high integrity impact. No public exploit identified at time of analysis, though the attack is straightforward given the disabled trust validation (checkChain: false configuration flaw). ENISA EUVD-2026-19478 classifies this as an information disclosure issue, though the primary risk is message authenticity compromise in encrypted email workflows.
RemediationAI
Upgrade Bulwark Webmail to version 1.4.11 or later, which restores proper certificate trust chain validation in S/MIME signature verification. The vendor-released patch addresses the root cause by enabling checkChain validation to ensure certificates are verified against trusted certificate authorities before displaying signatures as valid. Organizations should prioritize this upgrade for any production deployments where users rely on S/MIME signatures for email authenticity. The complete security advisory with upgrade instructions is available at https://github.com/bulwarkmail/webmail/security/advisories/GHSA-v6w6-338p-p256. No workarounds exist that provide equivalent security; disabling S/MIME signature display entirely would eliminate the false-positive trust indicator but also remove legitimate signature verification functionality. After upgrading, administrators should audit previously received S/MIME-signed emails, as messages signed with untrusted certificates prior to patching may have been incorrectly displayed as valid.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
S/MIME (Secure/Multipurpose Internet Mail Extensions) provides cryptographic signing and encryption for email messages using X.509 certificates. Valid signature verification requires both cryptographic validation (signature matches public key) and certificate trust chain validation (certificate chains to a trusted root CA). This vulnerability stems from CWE-295 (Improper Certificate Validation), where Bulwark Webmail's signature verification explicitly disabled trust chain checking (checkChain: false parameter). The affected component is Bulwark Webmail (CPE cpe:2.3:a:bulwarkmail:webmail), a self-hosted webmail client designed for Stalwart Mail Server. Without trust chain validation, the application only verifies that the signature mathematically matches the certificate's public key, but not whether that certificate was issued by a legitimate Certificate Authority. This allows any attacker to generate a self-signed certificate, sign malicious emails, and have those signatures displayed as valid to Bulwark Webmail users, completely undermining S/MIME's authenticity guarantees.
Know when Webmail gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Bulwark Webmail is a self-hosted webmail client for Stalwart Mail Server. Prior to 1.4.11, S/MIME signature verification did not validate the certificate trust chain (checkChain: false). Any email signed with a self-signed or untrusted certificate was displayed as having a valid signature. This vulnerability is fixed in 1.4.11.
Executive ViewAI
Bulwark Webmail versions prior to 1.4.11 contain a critical S/MIME signature verification flaw that allows attackers to forge digitally signed emails appearing legitimate to recipients, compromising the authenticity and integrity of encrypted email communications. This vulnerability directly undermines trust in email authentication controls and poses significant risk to organizations relying on digital signatures for compliance, legal, or sensitive communications.
Apply vendor patch. Interim mitigations: disable S/MIME signature functionality until patched; configure mail gateway rules to flag or reject self-signed certificate chains; implement out-of-band verification procedures for authenticity-critical communications; educate users to manually verify certificate trust chains and sender identity through alternative channels.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Roundcube Webmail before 1.1.10, 1.2.x before 1.2.7, and 1.3.x before 1.3.3 allows unauthorized access to arbitrary file
steps/mail/sendmail.inc in Roundcube before 1.1.7 and 1.2.x before 1.2.3, when no SMTP server is configured and the send
rcube_image.php in Roundcube Webmail before 1.4.4 allows attackers to execute arbitrary code via shell metacharacters in
Roundcube Webmail before 1.4.4 allows attackers to include local files and execute code via directory traversal in a plu
The DBMail driver in the Password plugin in Roundcube before 1.1.0 allows remote attackers to execute arbitrary commands
A Cross-Site Scripting vulnerability in Roundcube through 1.5.7 and 1.6.x through 1.6.7 allows a remote attacker to stea
Multiple buffer overflows in the DBMail driver in the Password plugin in Roundcube before 1.1.0 allow remote attackers t
Roundcube Webmail allows arbitrary password resets by authenticated users. Rated high severity (CVSS 8.8), this vulnerab
Pre-authentication SQL injection in Roundcube Webmail's virtuser_query plugin allows unauthenticated remote attackers to
roundcube version 1.3.4 and earlier contains an Insecure Permissions vulnerability in enigma plugin that can result in e
An issue was discovered in Roundcube Webmail before 1.4.4. Rated medium severity (CVSS 6.5), this vulnerability is remot
EUVD-2026-19478
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB