Approved changes feed: RSS · Atom
cpe:2.3:a:bulwarkmail:webmail:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Bulwarkmail (b1afa6c5-6a98-5026-91a6-9ae3ad107ce0) |
|---|---|
| Product | Webmail (0edd7295-c1ac-52b5-b018-ee4853f32d82) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/bulwarkmail/webmail |
purl2cpe | 2026-07-28 16:41:16.291728 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-113728 |
vulnerable | 2026-11-03 10:16:27.964431 |
Bulwark Webmail: DNS-rebinding SSRF in public iCalendar fetch endpoint
HIGH (7.5)
Bulwark Webmail is a self-hosted webmail client for Stalwart Mail Server. Prior to 1.9.2, the unauthenticated POST /api/fetch-ical endpoint validates a caller-supplied hostname with one DNS lookup and then passes the URL to fetch, which performs a separate lookup for the socket connection. An attacker controlling authoritative DNS can return a public address during validation and then rebind the hostname to a loopback, private, link-local, or cloud metadata address for the connection, causing the server to return up to 10 MB of an internal HTTP or HTTPS response. The same check-then-fetch pattern also existed in authenticated JMAP login and TOTP token-exchange flows. This issue is fixed in version 1.9.2.
Published: 2026-10-20T21:12:38.182Z
Updated: 2026-10-27T13:28:01.863Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35391 |
vulnerable | 2026-06-08 07:59:13.823900 |
Bulwark Webmail getClientIP() trusted client-controlled X-Forwarded-For value, enabling rate limit bypass and audit log forgery
Bulwark Webmail is a self-hosted webmail client for Stalwart Mail Server. Prior to 1.4.11, the getClientIP() function in lib/admin/session.ts trusted the first (leftmost) entry of the X-Forwarded-For header, which is fully controlled by the client. An attacker could forge their source IP address to bypass IP-based rate limiting (enabling brute-force attacks against the admin login) or forge audit log entries (making malicious activity appear to originate from arbitrary IP addresses). This vulnerability is fixed in 1.4.11.
Published: 2026-04-06T20:17:39.793Z
Updated: 2026-04-07T15:09:49.591Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35390 |
vulnerable | 2026-06-08 07:59:13.823554 |
Content-Security-Policy was set to Report-Only mode, failing to block XSS attacks
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.
Published: 2026-04-06T20:13:30.093Z
Updated: 2026-04-07T19:33:05.084Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35389 |
vulnerable | 2026-06-08 07:59:13.823197 |
Bulwark Webmail S/MIME signature verification accepted self-signed certificates
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.
Published: 2026-04-06T20:11:56.827Z
Updated: 2026-04-07T16:19:51.168Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34834 |
vulnerable | 2026-06-08 07:59:13.229880 |
Bulwark Webmail: Authentication Bypass in verifyIdentity() due to missing cookie validation
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.
Published: 2026-04-02T19:11:54.448Z
Updated: 2026-04-03T18:11:56.037Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34833 |
vulnerable | 2026-06-08 07:59:13.229425 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.