CVE-2026-86193

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th 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
Trending — 3 sources updated this weekElevated
8.7EG
EchelonGraph verdictPlan mitigationRemediate 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.4%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

grav-plugin-api before 1.0.20 fails to validate group-inherited super permissions in user-management guards, allowing non-super user managers to modify super-admin accounts. Attackers with api.access and api.users.write can patch password fields on group-super accounts to gain full administrative control.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
The EG Score, 8.7 of 10.
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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

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.

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 5, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Sep 5, 2026
No fix on record yet. Sources: github.
Web page

Grav API Plugin Authentication Bypass via Group-Inherited Super | Advisories | VulnCheck

https://www.vulncheck.com/advisories/grav-api-plugin-authentication-bypass-via-group-inherited-super
GitHub advisoryMentions a patch (unverified)

Target-super guards ignore group-inherited super · Advisory · getgrav/grav · GitHub

https://github.com/getgrav/grav/security/advisories/GHSA-vv8m-jqpm-38x4

Vendor Advisories for CVE-2026-86193(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 113× 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.

Showing the most recent 100 of 143 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 43 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:17 UTCEG score recompute
  2. 2026-10-11 16:34 UTCEG score recompute
  3. 2026-10-11 13:51 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-10 10:20 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  7. 2026-10-09 22:55 UTCEG score recompute
  8. 2026-10-09 22:55 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-09 01:02 UTCEG score recompute
  11. 2026-10-09 01:02 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-08 10:19 UTCEG score recompute
  14. 2026-10-08 10:18 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-07 22:53 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  17. 2026-10-07 09:47 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  18. 2026-10-06 22:22 UTCEG score recompute
  19. 2026-10-06 22:22 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-06 10:59 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  22. 2026-10-05 22:57 UTCEG score recompute
  23. 2026-10-05 22:57 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  24. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-05 11:13 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
Show 75 more
  1. 2026-10-04 23:43 UTCEG score recompute
  2. 2026-10-04 23:43 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  3. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-04 12:19 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  5. 2026-10-04 00:56 UTCEG score recompute
  6. 2026-10-04 00:56 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  7. 2026-10-03 12:29 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  8. 2026-10-03 00:22 UTCEG score recompute
  9. 2026-10-03 00:22 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  10. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-02 12:55 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  12. 2026-10-02 01:32 UTCEG score recompute
  13. 2026-10-02 01:32 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-01 14:09 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  16. 2026-10-01 02:46 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  17. 2026-09-30 15:23 UTCEG score recompute
  18. 2026-09-30 15:23 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  19. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-09-30 02:37 UTCEG score recompute
  21. 2026-09-30 02:37 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  22. 2026-09-29 12:12 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  23. 2026-09-29 00:49 UTCEG score recompute
  24. 2026-09-29 00:49 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  25. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  26. 2026-09-28 13:20 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  27. 2026-09-28 01:57 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  28. 2026-09-27 14:14 UTCEG score recompute
  29. 2026-09-27 14:14 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  30. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  31. 2026-09-27 02:41 UTCEG score recompute
  32. 2026-09-27 02:41 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  33. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  34. 2026-09-26 15:17 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  35. 2026-09-26 01:42 UTCEG score recompute
  36. 2026-09-26 01:42 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  37. 2026-09-25 12:19 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  38. 2026-09-25 00:56 UTCEG score recompute
  39. 2026-09-25 00:56 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  41. 2026-09-24 13:32 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  42. 2026-09-24 02:08 UTCEG score recompute
  43. 2026-09-24 02:08 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  45. 2026-09-23 14:45 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  46. 2026-09-23 03:21 UTCEG score recompute
  47. 2026-09-23 03:21 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  48. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  49. 2026-09-22 15:57 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  50. 2026-09-22 04:33 UTCEG score recompute
  51. 2026-09-22 04:33 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  52. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  53. 2026-09-21 17:08 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  54. 2026-09-21 05:06 UTCEG score recompute
  55. 2026-09-21 05:06 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  56. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  57. 2026-09-20 17:40 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  58. 2026-09-20 06:17 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  59. 2026-09-19 18:52 UTCEG score recompute
  60. 2026-09-19 18:52 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  61. 2026-09-19 07:26 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  62. 2026-09-18 20:03 UTCEG score recompute
  63. 2026-09-18 20:03 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  64. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  65. 2026-09-18 08:39 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  66. 2026-09-17 21:16 UTCEG score recompute
  67. 2026-09-17 21:16 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  68. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  69. 2026-09-17 09:53 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  70. 2026-09-16 22:30 UTCEG score recompute
  71. 2026-09-16 22:30 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  72. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  73. 2026-09-16 10:45 UTCEG score recompute
  74. 2026-09-16 10:45 UTCGHSA enrichmentGHSA-6rq7-cjmj-rc58 · GitHub severity HIGH
  75. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-86193?
CVE-2026-86193 is a high-severity vulnerability; its CVE record was published on September 5, 2026. grav-plugin-api before 1.0.20 fails to validate group-inherited super permissions in user-management guards, allowing non-super user managers to modify super-admin accounts. Attackers with api.access and api.users.write can patch password fields on group-super accounts to gain full administrative…
When was CVE-2026-86193 made public?
CVE-2026-86193 was made public on August 21, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 5, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-86193 actively exploited?
CVE-2026-86193 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86193?
CVE-2026-86193 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-86193?
No fix for CVE-2026-86193 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-86193 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-86193?

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

Book a Demo →Browse All CVEs