{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35389 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-35389 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35389 is a high-severity vulnerability in bulwarkmail webmail, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35389 and fix it if it is affected.\n\nWhat it is: CVE-2026-35389 is a high-severity vulnerability in bulwarkmail webmail, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-35389 in the wild and no public exploit code.\n\nAffected product: bulwarkmail webmail. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-35389/ (Markdown: https://insights.sbomify.com/CVE-2026-35389/index.md)","id":"CVE-2026-35389","markdown":"https://insights.sbomify.com/CVE-2026-35389/index.md","name":"CVE-2026-35389","record":{"aliases":["GHSA-v6w6-338p-p256"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Webmail client","requires_auth":"none","summary":"Attackers can spoof signed emails by using self-signed certificates, bypassing S/MIME signature verification in Bulwark Webmail.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"webmail","vendor":"bulwarkmail"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Bulwark Webmail S/MIME signature verification accepted self-signed certificates","id":"CVE-2026-35389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Content-Security-Policy was set to Report-Only mode, failing to block XSS attacks","id":"CVE-2026-35390"},"packages":[],"prev":{"headline":"Security feature bypass in OpenSSH","id":"CVE-2026-35388"},"products":["webmail"],"published":"2026-04-06","related":[{"cvss_score":8.7,"headline":"Security feature bypass in webmail","id":"CVE-2026-35391","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":8.7,"headline":"Bulwark Webmail: Information Exposure: password returned in /api/auth/session","id":"CVE-2026-34833","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":8.7,"headline":"Bulwark Webmail: Authentication Bypass in verifyIdentity() due to missing cookie validation","id":"CVE-2026-34834","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":5.3,"headline":"Content-Security-Policy was set to Report-Only mode, failing to block XSS attacks","id":"CVE-2026-35390","kev_date_added":null,"published":"2026-04-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["bulwarkmail"]},"summary":"Attackers can spoof signed emails by using self-signed certificates, bypassing S/MIME signature verification in Bulwark Webmail.","url":"https://insights.sbomify.com/CVE-2026-35389/"}