On this page (6 sections)

CVE-2026-126315 affects Frappe HRMS 16.14.0 before 16.20.1. According to the GitHub Advisory Database entry, the software sends product usage events on certain HR transactions without checking the site's telemetry setting. Some of those events carry more detail than they need to, so sensitive HR values can leave your system even when an administrator has switched telemetry off.

If you run Frappe HRMS, or host it for clients, this matters because the data involved is HR data: leave type names, claimed amounts and appraisal scores. The fix version named in the description is 16.20.1.

What happened

The advisory describes a telemetry setting bypass. Frappe HRMS has a site-level setting that controls whether product usage telemetry is sent. In the affected versions, certain HR transactions emit usage events without consulting that setting. In addition, some events include more detail than is needed for usage analytics.

The description states that this happens during normal use, with no user action required, and that values such as leave type names, claimed amounts and appraisal scores are transmitted even when telemetry is disabled.

Technical details and what is unclear

The weakness class is information exposure through a missing configuration check. The application is not being tricked by an outside attacker in the usual sense. Instead, the code path that emits events ignores the operator's privacy choice, and the payload is richer than necessary (a data minimization failure). Two problems combine: the opt-out is not honored, and the content is over-detailed.

Several points remain unconfirmed, and you should treat them with caution:

  • The sources do not say where the events are sent, who receives them, or how they are protected in transit. Do not assume a destination without checking the vendor's code and release notes.
  • The CVSS score differs between sources. The CVE record lists 9.8, while the GitHub advisory page shows 9.3 under CVSS v4, with network attack vector, low complexity, no privileges and no user interaction. A score this high is unusual for a telemetry issue, and the advisory is marked Unreviewed, so treat the exact severity figure as provisional.
  • The GitHub page lists affected and patched versions as Unknown and no package. The version range comes from the description text only.
  • The research contains no mention of active exploitation, and only one independent publisher covers this so far. The NVD entry repeats the same description and is not separate confirmation.

Who is affected

You are in scope if your Frappe HRMS installation is at version 16.14.0 or later but earlier than 16.20.1. Versions before 16.14.0 are not named in the description. Because the behavior occurs during normal HR transactions, no special user action or attacker interaction is described as necessary.

The practical risk is privacy and compliance rather than a described break-in. Employee-related financial and performance values, such as claimed amounts and appraisal scores, may have been sent off your system against your configured policy. If you promised staff, works councils or auditors that telemetry was disabled, you may need to document that this did not hold in the affected versions.

How to check your exposure

First find the installed version. On a standard Frappe bench setup, the following command lists installed apps and versions. Run it on the server, inside your bench directory, and look for the hrms line.

List installed Frappe apps and versions (run inside your bench directory)Shell
bench version

If hrms shows a version from 16.14.0 up to but not including 16.20.1, you are in the affected range. If you use a managed host or container image, check the image tag or ask your provider which HRMS version is deployed.

Next, look at what leaves your network. Review egress logs from the application server or proxy for outbound connections made around HR actions such as leave applications, expense claims or appraisals. Unexpected destinations that appear only after those actions are worth investigating. The research does not name a destination, so this is a general review, not a known indicator.

What to do now

  1. Identify every Frappe HRMS instance you run, including staging and client sites, and record its version.
  2. Upgrade any instance in the 16.14.0 to pre-16.20.1 range to 16.20.1 or later, following Frappe's standard update procedure.
  3. Take a backup before updating and test the upgrade on staging if you can.
  4. After upgrading, confirm the new version with the version command shown above.
  5. If you cannot upgrade right away, consider blocking outbound traffic from the HRMS server to anything not on an approved list, so stray events cannot leave. Test this carefully, since it can break legitimate integrations such as email or payment services.
  6. Ask your privacy or compliance lead whether the possible transmission of employee data needs to be assessed or documented under your policies.
  7. Check the vendor's release notes for 16.20.1 for details on what was changed and what data was sent, since the public advisory is thin on detail.
Caution. Updating an HR system can run database migrations and restart services. Schedule it outside payroll and appraisal periods, and keep a tested backup before you begin.

Detection and monitoring afterwards

Do not rely on the in-app telemetry toggle as a privacy control for this product line. Treat outbound network rules as the real enforcement point: allow only the destinations your HR server needs, and alert on new ones. Keep an eye on the GitHub advisory and the NVD record for corrections to the severity, version data or a fuller description, since the entry is currently unreviewed.

For the public-facing side of your HR portal, regular outside-in checks help catch expired certificates, DNS changes and missing headers. Webforta Monitor covers certificate, DNS and header-change monitoring, and the free security headers checker is a quick starting point. These do not detect this telemetry issue; they simply cover the surrounding basics.

For broader habits on keeping software current, see Small business website security.

Only one independent publisher covers this story so far, and the NVD page repeats the GitHub advisory text. Details may be revised as the vendor or reviewers add information.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-126315 - GitHub Advisory Databasegithub.com
  2. CVE-2026-126315: Frappe HRMS 16.14.0 before 16.20.1 sends product usage events on certain HR transactions without checking the site's telemetry setting, and some events…nvd.nist.gov ·
  • Frappe HRMS
  • CVE-2026-126315
  • telemetry
  • information exposure
  • HR software