CVE-2026-18817

LOWPre-NVD 2.22.2—
EchelonGraph scoreHIGH confidence

Score 2.2 from GitHub Security Advisory (severity: LOW) published 2026-08-05. a secondary CVSS source baseline 2.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
2.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.2Exploit: None knownExposed: 0

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

A security flaw has been discovered in Baserow up to 2.3.2. Affected by this issue is the function BaserowImpersonateAuthTokenSerializer of the file backend/src/baserow/api/admin/users/serializers.py of the component Inactive Non-Staff User Handler. Performing a manipulation results in improper authorization. Remote exploitation of the attack is possible. The complexity of an attack is rather high. The exploitation is known to be difficult. The presence of this vulnerability remains uncertain at this time. Upgrading to version 2.3.3 can resolve this issue. The affected component should be upgraded. The project maintainer explains: "While the problem exists, I'm not really sure if it's a vulnerability. (....) Even though the back gives a token for a deactivate user, none of the endpoints actually work. That said, we will fix it, but so far it seems more like a bug instead of a vulnerability."

CVSS v3
2.2
EG Score
2.2(high)
EG Risk
10(Track)
EG Risk 10/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
Severity22% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 12, 2026

References (5)

Vendor Advisories for CVE-2026-18817(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 32× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-19 06:24 UTCEG score recompute
  4. 2026-08-19 06:24 UTCGHSA enrichment
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-16 01:42 UTCEG score recompute
  10. 2026-08-16 01:42 UTCGHSA enrichment
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-12 21:08 UTCEG score recompute
  14. 2026-08-12 21:08 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-12 01:38 UTCEG score recompute
  17. 2026-08-12 01:38 UTCGHSA enrichment
  18. 2026-08-11 13:42 UTCEPSS rescore
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-08 21:05 UTCEG score recompute
  22. 2026-08-08 21:05 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-05 19:17 UTCEPSS rescore
Show 7 more
  1. 2026-08-05 16:31 UTCEG score recompute
  2. 2026-08-05 16:31 UTCGHSA enrichment
  3. 2026-08-05 15:28 UTCEG score recompute
  4. 2026-08-05 15:28 UTCGHSA enrichment
  5. 2026-08-04 22:31 UTCEG score recompute
  6. 2026-08-04 22:06 UTCEG score recompute
  7. 2026-08-04 22:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18817?
CVE-2026-18817 is a low vulnerability published on August 4, 2026. A security flaw has been discovered in Baserow up to 2.3.2. Affected by this issue is the function BaserowImpersonateAuthTokenSerializer of the file backend/src/baserow/api/admin/users/serializers.py of the component Inactive Non-Staff User Handler. Performing a manipulation results in improper…
When was CVE-2026-18817 disclosed?
CVE-2026-18817 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18817 actively exploited?
CVE-2026-18817 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 89.4% of all scored CVEs.
What is the CVSS score of CVE-2026-18817?
CVE-2026-18817 has a CVSS v3 base score of 2.2 (NVD).
How do I remediate CVE-2026-18817?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18817, 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-18817

Explore →

Is Your Infrastructure Affected by CVE-2026-18817?

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

Start Free Scan →Browse All CVEs