Bugsink up to 2.1.2 URL Parser urllib.parse.urlparse server-side request forgery

Summaryinfo

A vulnerability was found in Bugsink up to 2.1.2 and classified as critical. This vulnerability affects the function urllib.parse.urlparse of the component URL Parser. Executing a manipulation can lead to server-side request forgery. This vulnerability appears as CVE-2026-44502. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Bugsink up to 2.1.2. This vulnerability affects the function urllib.parse.urlparse of the component URL Parser. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability was named CVE-2026-44502 since 05/06/2026. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit.

Upgrading to version 2.1.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 940d2df635e06803ef658666d734306942db5cc7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• Bugsink

Version

• 2.1.0
• 2.1.1
• 2.1.2

License

• open-source

Website

• Product: https://github.com/bugsink/bugsink/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion