# CVE-2026-41513: Horilla: Open Redirect via Unvalidated `next` Parameter in Notification Endpoints

> Attackers can redirect users to malicious external sites via unvalidated parameters in notification endpoints, facilitating phishing attacks.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-vqg4-fc32-cwvw

## What is CVE-2026-41513?

CVE-2026-41513 is a medium-severity vulnerability in horilla-hr, published on 12 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Horilla is an HR and CRM software. In 1.5.0, the notification endpoints trust the unvalidated next parameter and redirect users to arbitrary external URLs. This allows an attacker to turn trusted application links into phishing or social-engineering redirects.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-41513?


## How do I fix CVE-2026-41513?

No fix has been published for CVE-2026-41513 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41513 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41513 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41513 and fix it if it is affected.

What it is: CVE-2026-41513 is a medium-severity vulnerability in horilla-hr, published on 12 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41513 exists.

Affected product: horilla-hr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41513/ (Markdown: https://insights.sbomify.com/CVE-2026-41513/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41513
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41513
- OSV: https://osv.dev/vulnerability/CVE-2026-41513

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41513/
Summaries are generated and may contain mistakes; the official description above is the record.