Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-fp53-qcf8-2xx2 | Bunsink has an SSRF bypass in `validate_webhook_url` |
Wed, 27 May 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 26 May 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Bugsink
Bugsink bugsink |
|
| Vendors & Products |
Bugsink
Bugsink bugsink |
Tue, 26 May 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Bugsink: SSRF bypass in `validate_webhook_url` | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-27T17:21:38.121Z
Reserved: 2026-05-06T18:28:20.886Z
Link: CVE-2026-44502
Updated: 2026-05-27T17:21:34.554Z
Status : Deferred
Published: 2026-05-26T17:16:46.387
Modified: 2026-06-17T10:50:44.163
Link: CVE-2026-44502
No data.
OpenCVE Enrichment
Updated: 2026-05-26T19:45:06Z
Github GHSA