CVE-2026-46547

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2026-05-21. a secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: 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, a reflected XSS vulnerability exists in the Page Leaving Warning page. The ncRedirectUrl and ncBackUrl query parameters are used in window.location.href and tag bindings without validation, allowing javascript: URI injection. This vulnerability is fixed in 2026.04.1.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
5.2%
KEV
Not listed

Published

May 21, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
Patch available. Sources: github.
github Patch Available

Reflected Cross-Site Scripting via Page Leaving Redirect URL · Advisory · nocodb/nocodb · GitHub

https://github.com/nocodb/nocodb/security/advisories/GHSA-9qgr-6vpg-9gh9

Vendor Advisories for CVE-2026-46547(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
npmnocodbghsa

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 7× 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-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-17 21:59 UTCOSV refresh
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-13 22:30 UTCEPSS rescore
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-29 19:56 UTCGHSA enrichment
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 29 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-27 20:06 UTCGHSA enrichment
  3. 2026-06-27 03:08 UTCEPSS rescore
  4. 2026-06-26 19:20 UTCGHSA enrichment
  5. 2026-06-25 14:14 UTCGHSA enrichment
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-24 14:05 UTCEPSS rescore
  8. 2026-06-17 20:29 UTCGHSA enrichment
  9. 2026-06-16 19:44 UTCGHSA enrichment
  10. 2026-06-15 15:37 UTCGHSA enrichment
  11. 2026-06-14 23:18 UTCEPSS rescore
  12. 2026-06-14 12:50 UTCGHSA enrichment
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-13 12:05 UTCGHSA enrichment
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 10:51 UTCGHSA enrichment
  17. 2026-06-11 10:06 UTCGHSA enrichment
  18. 2026-06-10 09:21 UTCGHSA enrichment
  19. 2026-06-09 08:37 UTCGHSA enrichment
  20. 2026-06-08 07:52 UTCGHSA enrichment
  21. 2026-06-07 07:08 UTCGHSA enrichment
  22. 2026-06-06 06:23 UTCGHSA enrichment
  23. 2026-06-05 05:38 UTCGHSA enrichment
  24. 2026-06-04 04:53 UTCGHSA enrichment
  25. 2026-06-03 04:08 UTCGHSA enrichment
  26. 2026-06-02 03:23 UTCGHSA enrichment
  27. 2026-06-01 02:38 UTCGHSA enrichment
  28. 2026-05-24 06:11 UTCEG score recompute
  29. 2026-05-24 06:11 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-46547?
CVE-2026-46547 is a medium vulnerability published on May 21, 2026. NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, a reflected XSS vulnerability exists in the Page Leaving Warning page. The ncRedirectUrl and ncBackUrl query parameters are used in window.location.href and <a> tag bindings without validation, allowing javascript: URI…
When was CVE-2026-46547 disclosed?
CVE-2026-46547 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-46547 actively exploited?
CVE-2026-46547 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46547?
CVE-2026-46547 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-46547?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46547, 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-46547

Explore →

Is Your Infrastructure Affected by CVE-2026-46547?

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