CVE-2026-86066

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (16th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-87371 (ENISA EUVD)Source: ENISA EUVD

5.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Horilla is an HR and CRM software. Prior to 2.0.0, approve_validate_attendance_request at /attendance/approve-validate-attendance-request/ changes attendance_validated, is_validate_request_approved, approved_by, and related pending-request state through an HTTP GET before calling attendance.save(), so Django does not require CSRF validation for the action. An unauthenticated attacker can cause a logged-in manager with attendance.change_attendance to make a top-level request that carries the manager's SameSite=Lax session cookie, silently approving attendance with the victim's privileges and attributing the approval to the victim in the audit trail. This issue is fixed in version 2.0.0.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
16th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

2.0.0

Patch available: horilla/horilla-hr 2.0.0

https://github.com/horilla/horilla-hr/releases/tag/2.0.0
GitHub commit Patch Available

commit 87a23ecaf294 (horilla/horilla-hr)

Patch available: horilla/horilla-hr 2.0.0 (contains commit 87a23ecaf294)

https://github.com/horilla/horilla-hr/commit/87a23ecaf2944c15dc5c131f813d2b83fd56eaa0
GitHub advisoryMentions a patch (unverified)

Cross-Site Request Forgery (CSRF) · Advisory · horilla/horilla-hr · GitHub

https://github.com/horilla/horilla-hr/security/advisories/GHSA-65vj-5p5g-pv5m

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  5. 2026-10-29 23:55 UTCOSV refresh
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  11. 2026-10-25 13:55 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-22 12:48 UTCEG score recompute
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-18 03:05 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 38 more
  1. 2026-10-12 14:52 UTCEG score recompute
  2. 2026-10-11 19:17 UTCEG score recompute
  3. 2026-10-11 16:34 UTCEG score recompute
  4. 2026-10-11 13:51 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-11 05:34 UTCEG score recompute
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-10 05:11 UTCEG score recompute
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-09 04:51 UTCEG score recompute
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-08 04:29 UTCEG score recompute
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-07 04:09 UTCEG score recompute
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-06 03:49 UTCEG score recompute
  17. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-05 03:25 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-04 03:05 UTCEG score recompute
  21. 2026-10-03 02:44 UTCEG score recompute
  22. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-02 02:23 UTCEG score recompute
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-01 01:50 UTCEG score recompute
  26. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  27. 2026-09-30 01:30 UTCEG score recompute
  28. 2026-09-30 00:39 UTCEG score recompute
  29. 2026-09-29 17:01 UTCEG score recompute
  30. 2026-09-28 16:40 UTCEG score recompute
  31. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  32. 2026-09-28 00:02 UTCEG score recompute
  33. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  34. 2026-09-26 23:42 UTCEG score recompute
  35. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-09-25 23:21 UTCEG score recompute
  37. 2026-09-25 22:28 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  38. 2026-09-25 22:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86066?
CVE-2026-86066 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. Horilla is an HR and CRM software. Prior to 2.0.0, approve_validate_attendance_request at /attendance/approve-validate-attendance-request/ changes attendance_validated, is_validate_request_approved, approved_by, and related pending-request state through an HTTP GET before calling attendance.save(),…
When was the CVE record for CVE-2026-86066 published?
The CVE record for CVE-2026-86066 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-86066 actively exploited?
CVE-2026-86066 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86066?
CVE-2026-86066 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-86066?
A fix for CVE-2026-86066 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-86066

Explore →

Is Your Infrastructure Affected by CVE-2026-86066?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.