# CVE-2026-86066: Horilla attendance approval endpoint is vulnerable to cross-site request forgery

> An unauthenticated attacker can trick a logged-in manager into approving attendance requests via a GET request, modifying data and bypassing authorization checks.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-65vj-5p5g-pv5m

## What is CVE-2026-86066?

CVE-2026-86066 is a medium-severity vulnerability in horilla-hr, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Horilla is an HR and CRM software. Prior to 2.0.0, approve_validate_attendance_request at /attendance/approve-validate-attendance-request/ changes attendance_validated, is_validate_request_approved, approved_by, and related pending-request state through an HTTP GET before calling attendance.save(), so Django does not require CSRF validation for the action. An unauthenticated attacker can cause a logged-in manager with attendance.change_attendance to make a top-level request that carries the manager's SameSite=Lax session cookie, silently approving attendance with the victim's privileges and attributing the approval to the victim in the audit trail. This issue is fixed in version 2.0.0.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-86066 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86066 is a medium-severity vulnerability in horilla-hr, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, 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-86066 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-86066/ (Markdown: https://insights.sbomify.com/CVE-2026-86066/index.md)
```

## Sources

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

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