Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-108733 Overview
CVE-2026-108733 is a missing authorization vulnerability [CWE-862] in Frappe HR (hrms) before version 16.11.0, including all 14.x and 15.x releases through 15.64.3. The flaw resides in the whitelisted expire_allocation method, which fails to verify that the caller has HR permissions on the targeted Leave Allocation record. Any authenticated user can send a crafted POST request naming another employee's Leave Allocation to zero out the allocated leaves. The result is wiping that employee's remaining leave balance without any HR role.
Critical Impact
Authenticated low-privilege users can tamper with the leave balances of any employee in the organization, undermining HR data integrity.
Affected Products
- Frappe HR (hrms) 14.x releases (all versions)
- Frappe HR (hrms) 15.x releases through 15.64.3
- Frappe HR (hrms) 16.x releases before 16.11.0
Discovery Timeline
- 2026-10-11 - CVE-2026-108733 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-108733
Vulnerability Analysis
Frappe HR exposes server-side Python functions to the HTTP API using the @frappe.whitelist() decorator. The expire_allocation method is one such whitelisted endpoint that modifies Leave Ledger Entry records to zero out an employee's leave allocation. The method omits a call to frappe.has_permission() for the referenced Leave Allocation document. As a result, authorization is reduced to simple authentication, not role or document-level access control. Any employee account can submit a POST request specifying another employee's allocation document name and overwrite the balance.
The affected logic lives in hrms/hr/doctype/leave_ledger_entry/leave_ledger_entry.py around lines 199-228, which handles ledger entry creation during allocation expiry.
Root Cause
The root cause is a classic missing authorization check in a whitelisted API method. Frappe's @frappe.whitelist() decorator makes a function callable over HTTP for authenticated sessions, but it does not enforce document-level permissions. The developer is responsible for calling frappe.has_permission(doctype, action, docname, throw=True) to validate access. The expire_allocation handler, along with several sibling methods patched in the same commit, never performed this check before mutating HR data.
Attack Vector
An attacker needs only valid credentials for any Frappe HR user account. The attacker enumerates or guesses the name field of a target employee's Leave Allocation, then issues an authenticated POST request to the expire_allocation endpoint with that name. The server executes the method and writes a ledger entry that zeros the allocated leaves. No HR role, administrator privilege, or user interaction is required.
# Security patch pattern applied in commit 6ab7a50
# Source: https://github.com/frappe/hrms/commit/6ab7a50347367413b78ad5bd5d9e4b8c6653c81f
@frappe.whitelist()
def get_company_cost_center_and_expense_account(company: str) -> dict:
+ frappe.has_permission("Company", "read", company, throw=True)
return frappe.db.get_value(
"Company", company, ["cost_center", "default_expense_claim_payable_account"], as_dict=True
)
# Same permission-check pattern added to roster API
# Source: https://github.com/frappe/hrms/commit/6ab7a50347367413b78ad5bd5d9e4b8c6653c81f
@frappe.whitelist()
def get_schedule_from_assignment(shift_schedule_assignment: str):
+ frappe.has_permission("Shift Schedule Assignment", "read", shift_schedule_assignment, throw=True)
shift_schedule = frappe.db.get_value(
"Shift Schedule Assignment", shift_schedule_assignment, "shift_schedule"
)
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-108733
Indicators of Compromise
- Leave Ledger Entry rows created with leaves = 0 or negative values via expire_allocation for users whose session owner lacks the HR Manager or HR User role.
- POST requests to /api/method/hrms.hr.doctype.leave_allocation.leave_allocation.expire_allocation from accounts that do not normally administer leave.
- Sudden drops in total_leaves_allocated across multiple employees that correlate with a single acting user.
Detection Strategies
- Audit Frappe's Activity Log and Version doctype for Leave Allocation and Leave Ledger Entry modifications performed by non-HR users.
- Enable request logging on the Frappe app server and alert on calls to any whitelisted expire_allocation endpoint originating from employee-tier roles.
- Correlate HTTP access logs with user role assignments to surface low-privilege sessions interacting with HR document types.
Monitoring Recommendations
- Forward Frappe application and NGINX access logs into a centralized log platform for role-aware query capabilities.
- Baseline the normal volume of leave expiry operations per day and alert on statistical anomalies.
- Monitor the tabLeave Ledger Entry table for off-hours writes or batches that affect multiple distinct employee values from the same owner.
How to Mitigate CVE-2026-108733
Immediate Actions Required
- Upgrade Frappe HR (hrms) to version 16.11.0 or later as soon as a maintenance window allows.
- Review Leave Allocation and Leave Ledger Entry records created or modified since deployment of any 14.x, 15.x, or pre-16.11.0 release for unauthorized zeroing.
- Rotate credentials for any user account that exhibited abnormal access to HR endpoints.
Patch Information
The fix is delivered in commit 6ab7a50 and shipped in Frappe HRMS Release v16.11.0. The patch adds frappe.has_permission(..., throw=True) calls to expire_allocation and other whitelisted methods so that document-level authorization is enforced before any state mutation. See the Vulncheck Advisory for Frappe HRMS and the HackMD Analysis on Authorization for additional detail.
Workarounds
- Restrict network exposure of the Frappe HR site to trusted internal users until the patch is applied.
- Apply a reverse-proxy rule that blocks POST requests to the expire_allocation method from non-HR source IP ranges.
- As a temporary measure, override the whitelisted method in a custom app to call frappe.has_permission("Leave Allocation", "write", name, throw=True) before any mutation.
# Upgrade Frappe HR to the fixed release using the bench CLI
bench get-app --branch version-16 hrms https://github.com/frappe/hrms
bench --site <site-name> install-app hrms
bench --site <site-name> migrate
bench version | grep hrms # Confirm hrms 16.11.0 or later
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

