# CVE-2026-96795: Horilla: Authenticated RCE in Horilla List-View Export

> Authenticated attackers can execute arbitrary code via crafted input in the list-view export feature, potentially gaining root privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-5g4v-4rv4-r26f

## What is CVE-2026-96795?

CVE-2026-96795 is a high-severity code injection vulnerability in horilla-hr, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Horilla is an HR and CRM software. Prior to 2.0.0, HorillaListView.export_data in horilla_views/generic/cbv/views.py accepts an authenticated user's columns POST parameter, takes field_tuple[1], interpolates it into dynamic_fn_str as Python source, and passes the generated function definition to exec(). A crafted string that remains valid under ast.literal_eval can inject Python syntax into a default argument evaluated during function definition, allowing arbitrary operating-system commands to execute with the application process privileges, including root privileges in the shipped Docker image. This issue is fixed in version 2.0.0.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-96795 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96795 is a high-severity code injection vulnerability in horilla-hr, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-96795 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-96795/ (Markdown: https://insights.sbomify.com/CVE-2026-96795/index.md)
```

## Sources

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

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