{
    "dataType": "CVE_RECORD",
    "dataVersion": "5.2",
    "cveMetadata": {
        "cveId": "CVE-2026-113728",
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "state": "PUBLISHED",
        "assignerShortName": "GitHub_M",
        "dateReserved": "2026-10-20T16:03:14.864Z",
        "datePublished": "2026-10-20T21:12:38.182Z",
        "dateUpdated": "2026-10-20T21:12:38.182Z"
    },
    "containers": {
        "cna": {
            "title": "Bulwark Webmail: DNS-rebinding SSRF in public iCalendar fetch endpoint",
            "problemTypes": [
                {
                    "descriptions": [
                        {
                            "cweId": "CWE-918",
                            "lang": "en",
                            "description": "CWE-918: Server-Side Request Forgery (SSRF)",
                            "type": "CWE"
                        }
                    ]
                }
            ],
            "metrics": [
                {
                    "cvssV3_1": {
                        "attackComplexity": "LOW",
                        "attackVector": "NETWORK",
                        "availabilityImpact": "NONE",
                        "baseScore": 7.5,
                        "baseSeverity": "HIGH",
                        "confidentialityImpact": "HIGH",
                        "integrityImpact": "NONE",
                        "privilegesRequired": "NONE",
                        "scope": "UNCHANGED",
                        "userInteraction": "NONE",
                        "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
                        "version": "3.1"
                    }
                }
            ],
            "references": [
                {
                    "name": "https://github.com/bulwarkmail/webmail/security/advisories/GHSA-24w9-8r42-8jwm",
                    "tags": [
                        "x_refsource_CONFIRM"
                    ],
                    "url": "https://github.com/bulwarkmail/webmail/security/advisories/GHSA-24w9-8r42-8jwm"
                },
                {
                    "name": "https://github.com/bulwarkmail/webmail/commit/3288589e5248dcc1da769cc578827a9ee1adc941",
                    "tags": [
                        "x_refsource_MISC"
                    ],
                    "url": "https://github.com/bulwarkmail/webmail/commit/3288589e5248dcc1da769cc578827a9ee1adc941"
                },
                {
                    "name": "https://github.com/bulwarkmail/webmail/releases/tag/1.9.2",
                    "tags": [
                        "x_refsource_MISC"
                    ],
                    "url": "https://github.com/bulwarkmail/webmail/releases/tag/1.9.2"
                }
            ],
            "affected": [
                {
                    "vendor": "bulwarkmail",
                    "product": "webmail",
                    "versions": [
                        {
                            "version": "< 1.9.2",
                            "status": "affected"
                        }
                    ]
                }
            ],
            "providerMetadata": {
                "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
                "shortName": "GitHub_M",
                "dateUpdated": "2026-10-20T21:12:38.182Z"
            },
            "descriptions": [
                {
                    "lang": "en",
                    "value": "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."
                }
            ],
            "source": {
                "advisory": "GHSA-24w9-8r42-8jwm",
                "discovery": "UNKNOWN"
            }
        }
    }
}