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
2.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.0Exploit: NoneExposed: 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)
EPSS
4.7%
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 6× in last 7d / 29× 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-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 19:56 UTCEG score recompute
  12. 2026-06-29 19:56 UTCGHSA enrichment
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 14:14 UTCEG score recompute
  20. 2026-06-25 14:14 UTCGHSA enrichment
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-24 14:05 UTCEPSS rescore
  23. 2026-06-16 10:33 UTCEG score recompute
  24. 2026-06-16 10:33 UTCGHSA enrichment
  25. 2026-06-14 23:18 UTCEPSS rescore
Show 14 more
  1. 2026-06-13 23:00 UTCEPSS rescore
  2. 2026-06-13 08:21 UTCEG score recompute
  3. 2026-06-13 08:21 UTCGHSA enrichment
  4. 2026-06-12 23:12 UTCEPSS rescore
  5. 2026-06-10 06:54 UTCEG score recompute
  6. 2026-06-10 06:54 UTCGHSA enrichment
  7. 2026-06-07 05:27 UTCEG score recompute
  8. 2026-06-07 05:27 UTCGHSA enrichment
  9. 2026-06-04 04:03 UTCEG score recompute
  10. 2026-06-04 04:03 UTCGHSA enrichment
  11. 2026-06-01 02:38 UTCEG score recompute
  12. 2026-06-01 02:38 UTCGHSA enrichment
  13. 2026-05-24 06:11 UTCEG score recompute
  14. 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 4.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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