CVE-2026-46550

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: 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 refresh-token cookie was set with httpOnly: true but missing both the secure flag and the sameSite attribute. Over plain HTTP the cookie could be intercepted on the network; without sameSite, browsers attached it to cross-site POSTs, enabling CSRF against the token-refresh endpoint. This vulnerability is fixed in 2026.04.1.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
—
EPSS
1.0%
KEV
Not listed

Published

May 21, 2026

Last Modified

June 25, 2026

Advisory Details (1)

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

Refresh Token Cookie Set Without `Secure` and `SameSite` Flags · Advisory · nocodb/nocodb · GitHub

https://github.com/nocodb/nocodb/security/advisories/GHSA-f74w-272x-mqcv

Vendor Advisories for CVE-2026-46550(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 5× in last 7d / 27× 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-20 17:08 UTCEPSS rescore
  3. 2026-07-18 10:04 UTCEPSS rescore
  4. 2026-07-17 21:59 UTCOSV refresh
  5. 2026-07-16 17:03 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-13 22:30 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-29 19:56 UTCGHSA enrichment
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 21:05 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 19:20 UTCGHSA enrichment
  25. 2026-06-25 14:14 UTCGHSA enrichment
Show 22 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-24 14:05 UTCEPSS rescore
  3. 2026-06-17 04:23 UTCGHSA enrichment
  4. 2026-06-16 02:41 UTCGHSA enrichment
  5. 2026-06-15 00:58 UTCGHSA enrichment
  6. 2026-06-14 23:18 UTCEPSS rescore
  7. 2026-06-13 23:11 UTCGHSA enrichment
  8. 2026-06-12 23:12 UTCEPSS rescore
  9. 2026-06-12 21:28 UTCGHSA enrichment
  10. 2026-06-11 19:45 UTCGHSA enrichment
  11. 2026-06-10 18:03 UTCGHSA enrichment
  12. 2026-06-09 16:20 UTCGHSA enrichment
  13. 2026-06-08 14:38 UTCGHSA enrichment
  14. 2026-06-07 12:55 UTCGHSA enrichment
  15. 2026-06-06 11:12 UTCGHSA enrichment
  16. 2026-06-05 09:30 UTCGHSA enrichment
  17. 2026-06-04 07:47 UTCGHSA enrichment
  18. 2026-06-03 06:04 UTCGHSA enrichment
  19. 2026-06-02 04:21 UTCGHSA enrichment
  20. 2026-06-01 02:38 UTCGHSA enrichment
  21. 2026-05-24 06:10 UTCEG score recompute
  22. 2026-05-24 06:10 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-46550?
CVE-2026-46550 is a medium vulnerability published on May 21, 2026. NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, the refresh-token cookie was set with httpOnly: true but missing both the secure flag and the sameSite attribute. Over plain HTTP the cookie could be intercepted on the network; without sameSite, browsers attached it to…
When was CVE-2026-46550 disclosed?
CVE-2026-46550 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-46550 actively exploited?
CVE-2026-46550 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46550?
CVE-2026-46550 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-46550?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46550, 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-46550

Explore →

Is Your Infrastructure Affected by CVE-2026-46550?

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

Start Free Scan →Browse All CVEs