# CVE-2026-130794: Frappe HR (hrms) before 16.9.0 Missing Authorization via Roster get_events


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-ppx2-pv7c-qxcw

## What is CVE-2026-130794?

CVE-2026-130794 is a medium-severity vulnerability in frappe hrms, published on 17 Nov 2026. 

### Official description

Frappe HR (hrms) before 16.9.0 contains a missing authorization vulnerability in the hrms.api.roster.get_events method that allows authenticated employees to view other employees' leave and shift data by bypassing User Permissions. Attackers with the Employee role can call get_events with empty filters for any date range to retrieve every employee's approved leave applications and shift assignments, including leave types, dates, shift locations and times.

Weakness: CWE-863 (Incorrect Authorization)

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

1 open source package ship an affected version, including frappe/hrms.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `frappe/hrms` | GitHub | `pkg:github/frappe/hrms` | All versions | 16.9.0 |

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

Upgrade frappe/hrms to 16.9.0 or later.

## Is CVE-2026-130794 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130794 is a medium-severity vulnerability in frappe hrms, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130794 exists.

Affected packages and fixed versions:
- frappe/hrms (GitHub): affected all versions; fixed in 16.9.0

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-130794/ (Markdown: https://insights.sbomify.com/CVE-2026-130794/index.md)
```

## Sources

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

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