{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-44502","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","state":"PUBLISHED","assignerShortName":"GitHub_M","dateReserved":"2026-05-06T18:28:20.886Z","datePublished":"2026-05-26T16:13:32.350Z","dateUpdated":"2026-05-27T17:21:38.121Z"},"containers":{"cna":{"title":"Bugsink: SSRF bypass in `validate_webhook_url`","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":4.3,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"NONE","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"}}],"references":[{"name":"https://github.com/bugsink/bugsink/security/advisories/GHSA-fp53-qcf8-2xx2","tags":["x_refsource_CONFIRM"],"url":"https://github.com/bugsink/bugsink/security/advisories/GHSA-fp53-qcf8-2xx2"},{"name":"https://github.com/bugsink/bugsink/commit/940d2df635e06803ef658666d734306942db5cc7","tags":["x_refsource_MISC"],"url":"https://github.com/bugsink/bugsink/commit/940d2df635e06803ef658666d734306942db5cc7"},{"name":"https://github.com/bugsink/bugsink/releases/tag/2.1.3","tags":["x_refsource_MISC"],"url":"https://github.com/bugsink/bugsink/releases/tag/2.1.3"}],"affected":[{"vendor":"bugsink","product":"bugsink","versions":[{"version":"< 2.1.3","status":"affected"}]}],"providerMetadata":{"orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M","dateUpdated":"2026-05-26T16:13:32.350Z"},"descriptions":[{"lang":"en","value":"Bugsink is a self-hosted error tracking tool. Prior to 2.1.3, Bugsink’s webhook URL validation could be (partially) bypassed because of a mismatch in URL parsing. The original validation logic parsed webhook URLs with Python’s urllib.parse.urlparse, then sent the request with requests.post. For malformed inputs involving backslashes and @, those components can disagree about where the authority ends and which hostname is the real target. A URL may therefore appear to target an allowlisted public hostname during validation, while the HTTP client actually connects to a different host. This vulnerability is fixed in 2.1.3."}],"source":{"advisory":"GHSA-fp53-qcf8-2xx2","discovery":"UNKNOWN"}},"adp":[{"metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-05-27T17:21:30.414936Z","id":"CVE-2026-44502","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"title":"CISA ADP Vulnrichment","providerMetadata":{"orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP","dateUpdated":"2026-05-27T17:21:38.121Z"}}]}}