# CVE-2026-108733: Frappe HR (hrms) before 16.11.0 Missing Authorization via expire_allocation

> Authenticated users can expire any employee's leave allocation, wiping their remaining leave balance without proper authorization checks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 11 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-7xfq-498m-4hrf

## What is CVE-2026-108733?

CVE-2026-108733 is a medium-severity missing authorization vulnerability in frappe hrms, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Frappe HR (hrms) before 16.11.0, including all 14.x and 15.x releases through 15.64.3, contains a missing authorization vulnerability in the whitelisted expire_allocation method that allows authenticated users to expire any leave allocation. Attackers without HR roles can name another employee's Leave Allocation in a POST request to zero its allocated leaves and wipe that employee's remaining leave balance.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-108733 being exploited?

There is no known exploitation of CVE-2026-108733 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108733 is a medium-severity missing authorization vulnerability in frappe hrms, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108733 in the wild and no public exploit code.

Affected product: frappe hrms. 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-108733/ (Markdown: https://insights.sbomify.com/CVE-2026-108733/index.md)
```

## Sources

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

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