CVE-2026-46549

LOWPre-NVD 2.02.0—
EchelonGraph scoreMEDIUM confidence

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

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

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

NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, the OAuth token strategy attached oauth_scope and oauth_granted_resources to the request user, but the ACL middleware never consulted either. An OAuth token issued with a restricted scope (e.g. MCP-only) therefore inherited the full permissions of the underlying user across all routes; the granted_resources.base_id restriction was bypassed on org-level endpoints that don't populate req.context.base_id. This vulnerability is fixed in 2026.04.1.

CVSS v3
2.0
EG Score
2.0(medium)
EG Risk
14(Track)
EG Risk 14/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
Severity20% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

May 21, 2026

Last Modified

June 25, 2026

References (1)

Vendor Advisories for CVE-2026-46549(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmnocodb—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
nocodb———

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 41× 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-25 13:49 UTCEPSS rescore
  2. 2026-08-23 20:10 UTCEG score recompute
  3. 2026-08-23 20:10 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 18:45 UTCEG score recompute
  8. 2026-08-20 18:45 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 03:23 UTCEG score recompute
  14. 2026-08-16 03:23 UTCGHSA enrichment
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-12 09:50 UTCEG score recompute
  20. 2026-08-12 09:50 UTCGHSA enrichment
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 01:26 UTCEG score recompute
  24. 2026-08-09 01:26 UTCGHSA enrichment
  25. 2026-08-06 13:47 UTCEPSS rescore
Show 63 more
  1. 2026-08-05 21:13 UTCEG score recompute
  2. 2026-08-05 21:13 UTCGHSA enrichment
  3. 2026-08-05 19:17 UTCEPSS rescore
  4. 2026-08-04 15:10 UTCEPSS rescore
  5. 2026-08-04 10:39 UTCEPSS rescore
  6. 2026-08-03 10:36 UTCEPSS rescore
  7. 2026-08-02 02:27 UTCEPSS rescore
  8. 2026-08-01 19:06 UTCEG score recompute
  9. 2026-08-01 19:06 UTCGHSA enrichment
  10. 2026-08-01 04:16 UTCEPSS rescore
  11. 2026-07-30 16:28 UTCEPSS rescore
  12. 2026-07-30 01:30 UTCEPSS rescore
  13. 2026-07-29 17:41 UTCEG score recompute
  14. 2026-07-29 17:41 UTCGHSA enrichment
  15. 2026-07-28 15:36 UTCEPSS rescore
  16. 2026-07-27 14:13 UTCEPSS rescore
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-24 14:17 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 03:17 UTCEG score recompute
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-21 15:24 UTCEPSS rescore
  23. 2026-07-20 17:08 UTCEPSS rescore
  24. 2026-07-19 14:31 UTCEPSS rescore
  25. 2026-07-19 02:29 UTCEPSS rescore
  26. 2026-07-18 10:04 UTCEPSS rescore
  27. 2026-07-17 21:59 UTCOSV refresh
  28. 2026-07-16 17:03 UTCEPSS rescore
  29. 2026-07-15 16:57 UTCEPSS rescore
  30. 2026-07-15 02:00 UTCEPSS rescore
  31. 2026-07-13 22:30 UTCEPSS rescore
  32. 2026-07-13 06:13 UTCEPSS rescore
  33. 2026-07-12 05:46 UTCEPSS rescore
  34. 2026-07-11 08:27 UTCEPSS rescore
  35. 2026-07-09 19:10 UTCEPSS rescore
  36. 2026-07-08 15:16 UTCEPSS rescore
  37. 2026-07-07 13:46 UTCEPSS rescore
  38. 2026-07-06 16:27 UTCEPSS rescore
  39. 2026-07-05 02:30 UTCEPSS rescore
  40. 2026-07-04 06:31 UTCEPSS rescore
  41. 2026-07-01 15:07 UTCEPSS rescore
  42. 2026-06-30 23:22 UTCEPSS rescore
  43. 2026-06-29 19:56 UTCGHSA enrichment
  44. 2026-06-29 14:06 UTCEPSS rescore
  45. 2026-06-29 14:06 UTCEPSS rescore
  46. 2026-06-28 14:07 UTCEPSS rescore
  47. 2026-06-28 04:56 UTCEPSS rescore
  48. 2026-06-28 04:56 UTCEPSS rescore
  49. 2026-06-27 03:08 UTCEPSS rescore
  50. 2026-06-25 14:14 UTCGHSA enrichment
  51. 2026-06-25 13:49 UTCEPSS rescore
  52. 2026-06-24 14:05 UTCEPSS rescore
  53. 2026-06-16 10:33 UTCGHSA enrichment
  54. 2026-06-14 23:18 UTCEPSS rescore
  55. 2026-06-13 23:00 UTCEPSS rescore
  56. 2026-06-13 08:21 UTCGHSA enrichment
  57. 2026-06-12 23:12 UTCEPSS rescore
  58. 2026-06-10 06:54 UTCGHSA enrichment
  59. 2026-06-07 05:27 UTCGHSA enrichment
  60. 2026-06-04 04:03 UTCGHSA enrichment
  61. 2026-06-01 02:38 UTCGHSA enrichment
  62. 2026-05-24 06:11 UTCEG score recompute
  63. 2026-05-24 06:11 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46549?
CVE-2026-46549 is a low vulnerability published on May 21, 2026. NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, the OAuth token strategy attached oauthscope and oauthgrantedresources to the request user, but the ACL middleware never consulted either. An OAuth token issued with a restricted scope (e.g. MCP-only) therefore inherited…
When was CVE-2026-46549 disclosed?
CVE-2026-46549 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46549 actively exploited?
CVE-2026-46549 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 85.0% of all scored CVEs.
What is the CVSS score of CVE-2026-46549?
CVE-2026-46549 has a CVSS v3 base score of 2.0 (NVD).
How do I remediate CVE-2026-46549?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46549, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46549

Explore →

Is Your Infrastructure Affected by CVE-2026-46549?

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

Start Free Scan →Browse All CVEs