CVE
HRMS personal data leak via telemetry events
Only affects Frappe HRMS 16.14.0 up to but not including 16.20.1 on sites with telemetry disabled. Fixed in 16.20.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 16.20.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 16.20.1.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.55% · 46th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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 include more detail than needed. During normal use, with no user action, values such as leave type names, claimed amounts and appraisal scores are transmitted even when telemetry is disabled.
Who should check
Teams running Frappe HRMS 16.14.0 through 16.20.0 on sites with telemetry disabled, which should upgrade to 16.20.1.
Read the source excerpt
“Sites running an affected version with telemetry disabled are impacted.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 16.20.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126315 (Frappe HRMS 16.14.0 before 16.20.1 Telemetry Setting Bypass Information Exposure), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126315 (entry last updated 2026-11-13):
Affected:
- frappe hrms: from 16.14.0, fixed in 16.20.1
Fixed versions: 16.20.1.
Conditions (all must be true for the bug to be hit):
- Frappe HRMS versions 16.14.0 up to but not including 16.20.1 (source: https://github.com/frappe/hrms/security/advisories/GHSA-26gj-rr4j-3hgc)
- Site has telemetry disabled (source: https://github.com/frappe/hrms/security/advisories/GHSA-26gj-rr4j-3hgc)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126315 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126315 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/frappe/hrms/security/advisories/GHSA-26gj-rr4j-3hgc
- https://www.vulncheck.com/advisories/frappe-hrms-16.14.0-before-16.20.1-telemetry-setting-bypass-information-exposure
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126315
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126315"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- frappe hrms
From 16.14.0 · fixed in 16.20.1
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126315
Is CVE-2026-126315 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Private HR details such as leave type names, claimed amounts and appraisal scores are sent in product usage events even when telemetry is disabled.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-126315?
hrms: from 16.14.0 before 16.20.1.Source: cve.now feed data
Am I affected, and how do I check?
Sites running Frappe HRMS 16.14.0 up to but not including 16.20.1 with telemetry disabled are impacted. Check the installed HRMS version and the site's telemetry setting to see which category a site falls into.Source: github.com, vulncheck.com
How do I fix CVE-2026-126315?
Upgrade Frappe HRMS to 16.20.1 or later.Source: github.com, vulncheck.com