Quick answers
- Is CVE-2026-41513 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41513 being exploited in the wild.
- How severe is CVE-2026-41513?
- Informational severity, with a CVSS score of 4.8, published 12 May 2026.
- Which products and versions are affected?
- Horilla 1.5.0.
- Is there a fix for CVE-2026-41513?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-41513 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-41513?
- Check whether you run Horilla at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An open redirect vulnerability exists in Horilla 1.5.0 within the notification component. The application's notification endpoints, such as 'mark-all-as-read/', accept a 'next' query parameter and pass it directly to the Django redirect() function without performing validation (e.g., using url_has_allowed_host_and_scheme()). An attacker with low privileges can craft a URL that, when clicked by an authenticated user, performs the notification action and then redirects the victim to an arbitrary external domain. This flaw facilitates phishing and social engineering attacks by leveraging the reputation of the trusted application domain. A fix has been committed to the project's repository to validate the redirect target.
Affected products
- Horilla Horilla 1.5.0
Timeline
- 2026-04-27: advisory: GitHub Security Advisory published
- 2026-05-12: disclosed: CVE published to NVD