{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35390 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-35390 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35390 is a medium-severity cross-site scripting vulnerability in bulwarkmail webmail, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-35390 and fix it if it is affected.\n\nWhat it is: CVE-2026-35390 is a medium-severity cross-site scripting vulnerability in bulwarkmail webmail, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-35390 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-35390/ (Markdown: https://insights.sbomify.com/CVE-2026-35390/index.md)","id":"CVE-2026-35390","markdown":"https://insights.sbomify.com/CVE-2026-35390/index.md","name":"CVE-2026-35390","record":{"aliases":["GHSA-6q52-98cr-qx65"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Webmail client","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript via crafted emails because the Content-Security-Policy was set to Report-Only mode, allowing session theft.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"webmail","vendor":"bulwarkmail"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Bulwark Webmail is a self-hosted webmail client for Stalwart Mail Server. Prior to 1.4.11, the reverse proxy (proxy.ts) set the Content-Security-Policy-Report-Only header instead of the enforcing Content-Security-Policy header. This means cross-site scripting (XSS) attacks were logged but not blocked. Any user who could inject script content (e.g., via crafted email HTML) could execute arbitrary JavaScript in the context of the application, potentially stealing session tokens or performing actions on behalf of the user. 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":"Content-Security-Policy was set to Report-Only mode, failing to block XSS attacks","id":"CVE-2026-35390","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in webmail","id":"CVE-2026-35391"},"packages":[],"prev":{"headline":"Bulwark Webmail S/MIME signature verification accepted self-signed certificates","id":"CVE-2026-35389"},"products":["webmail"],"published":"2026-04-06","related":[{"cvss_score":8.7,"headline":"Bulwark Webmail S/MIME signature verification accepted self-signed certificates","id":"CVE-2026-35389","kev_date_added":null,"published":"2026-04-06"},{"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"}],"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 execute arbitrary JavaScript via crafted emails because the Content-Security-Policy was set to Report-Only mode, allowing session theft.","url":"https://insights.sbomify.com/CVE-2026-35390/"}