Authenticated SSRF via divergent webhook URL parsing
Published May 26, 2026 · Updated May 26, 2026
SSRF in webhook URL validation in Bugsink before 2.1.3 allows remote authenticated users to send HTTP POST requests to blocked hosts. The validate_webhook_url function parsed the target with urllib.parse.urlparse, but requests.post interpreted crafted backslashes and @ signs differently when selecting the actual host. A user able to configure or influence a webhook URL can reach loopback, private, or non-allowlisted destinations, but cannot use the flaw as a general-purpose proxy.
Summary
What happened
SSRF in webhook URL validation in Bugsink before 2.1.3 allows remote authenticated users to send HTTP POST requests to blocked hosts. The validate_webhook_url function parsed the target with urllib.parse.urlparse, but requests.post interpreted crafted backslashes and @ signs differently when selecting the actual host. A user able to configure or influence a webhook URL can reach loopback, private, or non-allowlisted destinations, but cannot use the flaw as a general-purpose proxy.
The record
- CVE
- CVE-2026-44502
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- Bugsink
- Product
- Bugsink
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo