CVE-2026-81818

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

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

Affected versions of Flowintel contain an authorization flaw in the administrative user-edit API.

The existing authorization check correctly prevented an organization administrator from editing users in another organization, but it did not prevent them from editing a full administrator within their own organization. As a result, an org admin could modify that full administrator account, including changing its password. The upstream commit explicitly describes the issue as:

“Org admin can change the password of a full admin in the same organization.”

The fix adds a higher-privilege boundary check:

if user_to_edit.is_admin(): return ... 403

so organization administrators can no longer modify full administrator accounts.

Version impacted >=3.3.0

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

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
Severity86% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-81818(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 18× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-31 03:52 UTCEG score recompute
  2. 2026-08-31 03:51 UTCGHSA enrichment
  3. 2026-08-30 19:18 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 15:51 UTCGHSA enrichment
  6. 2026-08-30 03:50 UTCEG score recompute
  7. 2026-08-30 03:50 UTCGHSA enrichment
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-29 15:48 UTCGHSA enrichment
  10. 2026-08-29 03:47 UTCEG score recompute
  11. 2026-08-29 03:47 UTCGHSA enrichment
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-28 15:45 UTCGHSA enrichment
  14. 2026-08-28 08:35 UTCGHSA enrichment
  15. 2026-08-27 20:28 UTCGHSA enrichment
  16. 2026-08-27 17:27 UTCEG score recompute
  17. 2026-08-27 16:49 UTCEG score recompute
  18. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81818?
CVE-2026-81818 is a high vulnerability published on August 27, 2026. Affected versions of Flowintel contain an authorization flaw in the administrative user-edit API. The existing authorization check correctly prevented an organization administrator from editing users in another organization, but it did not prevent them from editing a full administrator within their…
When was CVE-2026-81818 disclosed?
CVE-2026-81818 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81818 actively exploited?
CVE-2026-81818 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.9% of all scored CVEs.
What is the CVSS score of CVE-2026-81818?
CVE-2026-81818 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-81818?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81818, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81818?

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