CVE-2026-18817

LOWPre-NVD 2.22.2—
EchelonGraph scoreMEDIUM 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.3%CVSS: 2.2Exploit: None knownExposed services: Not assessed

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

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.2LOWmedium confidence
EG Risk
10
EG Risk 10/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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 7× in last 7d / 36× 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-10-04 23:21 UTCEPSS rescore
  2. 2026-10-02 10:05 UTCEG score recompute
  3. 2026-10-02 10:05 UTCGHSA enrichment
  4. 2026-10-01 19:49 UTCEPSS rescore
  5. 2026-09-30 15:02 UTCEPSS rescore
  6. 2026-09-29 15:20 UTCEPSS rescore
  7. 2026-09-28 13:51 UTCEPSS rescore
  8. 2026-09-28 12:51 UTCEG score recompute
  9. 2026-09-28 12:51 UTCGHSA enrichment
  10. 2026-09-27 13:47 UTCEPSS rescore
  11. 2026-09-26 15:58 UTCEPSS rescore
  12. 2026-09-25 07:37 UTCEG score recompute
  13. 2026-09-25 07:37 UTCGHSA enrichment
  14. 2026-09-22 03:04 UTCEG score recompute
  15. 2026-09-22 03:03 UTCGHSA enrichment
  16. 2026-09-18 22:21 UTCEG score recompute
  17. 2026-09-18 22:21 UTCGHSA enrichment
  18. 2026-09-18 19:27 UTCEPSS rescore
  19. 2026-09-16 14:07 UTCEPSS rescore
  20. 2026-09-16 05:14 UTCEPSS rescore
  21. 2026-09-15 16:51 UTCEG score recompute
  22. 2026-09-15 16:51 UTCGHSA enrichment
  23. 2026-09-13 16:46 UTCEPSS rescore
  24. 2026-09-12 15:00 UTCEPSS rescore
  25. 2026-09-12 12:17 UTCEG score recompute
Show 63 more
  1. 2026-09-12 12:17 UTCGHSA enrichment
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-11 09:36 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-09 06:34 UTCEG score recompute
  6. 2026-09-09 06:34 UTCGHSA enrichment
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-05 18:31 UTCEG score recompute
  11. 2026-09-05 18:31 UTCGHSA enrichment
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-02 07:40 UTCEG score recompute
  15. 2026-09-02 07:39 UTCGHSA enrichment
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-29 21:41 UTCEG score recompute
  21. 2026-08-29 21:41 UTCGHSA enrichment
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 15:34 UTCEG score recompute
  26. 2026-08-25 15:34 UTCGHSA enrichment
  27. 2026-08-25 13:48 UTCEPSS rescore
  28. 2026-08-23 00:19 UTCEPSS rescore
  29. 2026-08-22 10:58 UTCEG score recompute
  30. 2026-08-22 10:58 UTCGHSA enrichment
  31. 2026-08-21 23:49 UTCEPSS rescore
  32. 2026-08-20 22:55 UTCEPSS rescore
  33. 2026-08-19 17:03 UTCEPSS rescore
  34. 2026-08-19 06:24 UTCEG score recompute
  35. 2026-08-19 06:24 UTCGHSA enrichment
  36. 2026-08-18 13:48 UTCEPSS rescore
  37. 2026-08-17 13:47 UTCEPSS rescore
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 02:14 UTCEPSS rescore
  40. 2026-08-16 01:42 UTCEG score recompute
  41. 2026-08-16 01:42 UTCGHSA enrichment
  42. 2026-08-15 01:30 UTCEPSS rescore
  43. 2026-08-13 22:00 UTCEPSS rescore
  44. 2026-08-12 21:08 UTCEG score recompute
  45. 2026-08-12 21:08 UTCGHSA enrichment
  46. 2026-08-12 13:50 UTCEPSS rescore
  47. 2026-08-12 01:38 UTCEG score recompute
  48. 2026-08-12 01:38 UTCGHSA enrichment
  49. 2026-08-11 13:42 UTCEPSS rescore
  50. 2026-08-11 00:00 UTCEPSS rescore
  51. 2026-08-09 13:46 UTCEPSS rescore
  52. 2026-08-08 21:05 UTCEG score recompute
  53. 2026-08-08 21:05 UTCGHSA enrichment
  54. 2026-08-08 16:37 UTCEPSS rescore
  55. 2026-08-06 13:46 UTCEPSS rescore
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-05 16:31 UTCEG score recompute
  58. 2026-08-05 16:31 UTCGHSA enrichment
  59. 2026-08-05 15:28 UTCEG score recompute
  60. 2026-08-05 15:28 UTCGHSA enrichment
  61. 2026-08-04 22:31 UTCEG score recompute
  62. 2026-08-04 22:06 UTCEG score recompute
  63. 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 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.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18817?
CVE-2026-18817 has a CVSS base score of 2.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18817?
No fix for CVE-2026-18817 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-18817 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs