CVE-2026-41641

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 1.8%, top 24% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 7.2Exploit: NoneExposed: 0

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

NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Prior to version 2.0.39, the checkSQL() validation function that blocks dangerous SQL keywords (e.g., pg_read_file, LOAD_FILE, dblink) is applied on the collections:create and sqlCollection:execute endpoints but is entirely missing on the sqlCollection:update endpoint. An attacker with collection management permissions can create a SQL collection with benign SQL, then update it with arbitrary SQL that bypasses all validation, and query the collection to execute the injected SQL and exfiltrate data. This issue has been patched in version 2.0.39.

CVSS v3
7.2
EG Score
7.2(medium)
EPSS
76.5%
KEV
Not listed

Published

May 7, 2026

Last Modified

May 7, 2026

Advisory Details (4)

Auto-updated May 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

SQL Injection and Validation Bypass via `sqlCollection:update` Missing `checkSQL` Call · Advisory · nocobase/nocobase · GitHub

https://github.com/nocobase/nocobase/security/advisories/GHSA-wrwh-c28m-9jjh
generic

Release v2.0.39 · nocobase/nocobase · GitHub

https://github.com/nocobase/nocobase/releases/tag/v2.0.39
generic

fix(collection-sql): validate sql on update by 2013xile · Pull Request #9134 · nocobase/nocobase · GitHub

https://github.com/nocobase/nocobase/pull/9134
generic

fix(collection-sql): validate sql on update (#9134) · nocobase/nocobase@851aee5 · GitHub

https://github.com/nocobase/nocobase/commit/851aee543efa894142e0f7be03eb55d9cec06a91

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@nocobase/plugin-collection-sql—2.0.39—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× 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.

Showing the most recent 100 of 111 total refreshes for this CVE.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-16 10:49 UTCOSV refresh
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-13 22:30 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 15:15 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-01 15:06 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-28 14:07 UTCEPSS rescore
  24. 2026-06-28 09:41 UTCEG score recompute
  25. 2026-06-28 04:56 UTCEPSS rescore
Show 75 more
  1. 2026-06-27 14:43 UTCEG score recompute
  2. 2026-06-27 03:08 UTCEPSS rescore
  3. 2026-06-26 22:28 UTCEG score recompute
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 14:05 UTCEPSS rescore
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-22 14:25 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-19 19:25 UTCEPSS rescore
  14. 2026-06-18 17:52 UTCEPSS rescore
  15. 2026-06-18 17:52 UTCEPSS rescore
  16. 2026-06-17 17:53 UTCEPSS rescore
  17. 2026-06-16 17:52 UTCEPSS rescore
  18. 2026-06-15 17:49 UTCEPSS rescore
  19. 2026-06-14 19:45 UTCEG score recompute
  20. 2026-06-14 07:10 UTCEG score recompute
  21. 2026-06-13 23:00 UTCEPSS rescore
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 21:59 UTCEG score recompute
  25. 2026-06-12 02:04 UTCEG score recompute
  26. 2026-06-11 14:00 UTCEPSS rescore
  27. 2026-06-11 13:29 UTCEG score recompute
  28. 2026-06-11 00:53 UTCEG score recompute
  29. 2026-06-10 22:18 UTCEPSS rescore
  30. 2026-06-10 13:22 UTCEPSS rescore
  31. 2026-06-10 13:22 UTCEPSS rescore
  32. 2026-06-10 11:45 UTCEG score recompute
  33. 2026-06-09 23:11 UTCEG score recompute
  34. 2026-06-09 10:36 UTCEG score recompute
  35. 2026-06-08 22:01 UTCEG score recompute
  36. 2026-06-08 14:17 UTCEPSS rescore
  37. 2026-06-08 14:17 UTCEPSS rescore
  38. 2026-06-08 04:45 UTCEG score recompute
  39. 2026-06-07 16:11 UTCEG score recompute
  40. 2026-06-07 15:25 UTCEPSS rescore
  41. 2026-06-07 15:25 UTCEPSS rescore
  42. 2026-06-07 03:36 UTCEG score recompute
  43. 2026-06-06 15:01 UTCEG score recompute
  44. 2026-06-06 13:47 UTCEPSS rescore
  45. 2026-06-06 13:47 UTCEPSS rescore
  46. 2026-06-06 02:26 UTCEG score recompute
  47. 2026-06-05 22:47 UTCEPSS rescore
  48. 2026-06-05 13:51 UTCEG score recompute
  49. 2026-06-05 06:10 UTCEPSS rescore
  50. 2026-06-05 06:10 UTCEPSS rescore
  51. 2026-06-05 01:16 UTCEG score recompute
  52. 2026-06-04 13:12 UTCEPSS rescore
  53. 2026-06-04 13:12 UTCEPSS rescore
  54. 2026-06-04 12:41 UTCEG score recompute
  55. 2026-06-04 00:06 UTCEG score recompute
  56. 2026-06-03 11:31 UTCEG score recompute
  57. 2026-06-02 22:55 UTCEG score recompute
  58. 2026-06-02 20:13 UTCEPSS rescore
  59. 2026-06-02 10:19 UTCEG score recompute
  60. 2026-06-01 21:44 UTCEG score recompute
  61. 2026-06-01 13:52 UTCEPSS rescore
  62. 2026-06-01 13:52 UTCEPSS rescore
  63. 2026-06-01 13:51 UTCEPSS rescore
  64. 2026-06-01 09:07 UTCEG score recompute
  65. 2026-05-31 22:30 UTCEPSS rescore
  66. 2026-05-31 22:30 UTCEPSS rescore
  67. 2026-05-31 00:16 UTCEPSS rescore
  68. 2026-05-31 00:16 UTCEPSS rescore
  69. 2026-05-31 00:16 UTCEPSS rescore
  70. 2026-05-29 13:44 UTCEPSS rescore
  71. 2026-05-29 13:44 UTCEPSS rescore
  72. 2026-05-28 13:44 UTCEPSS rescore
  73. 2026-05-28 13:44 UTCEPSS rescore
  74. 2026-05-28 13:44 UTCEPSS rescore
  75. 2026-05-27 13:40 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-41641.yaml
    First seen Jan 1, 2026

    NocoBase - SQL Injection

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41641?
CVE-2026-41641 is a high vulnerability published on May 7, 2026. NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Prior to version 2.0.39, the checkSQL() validation function that blocks dangerous SQL keywords (e.g., pgreadfile, LOAD_FILE, dblink) is applied on the collections:create and…
When was CVE-2026-41641 disclosed?
CVE-2026-41641 was first published in the National Vulnerability Database on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41641 actively exploited?
CVE-2026-41641 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 76.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41641?
CVE-2026-41641 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-41641?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41641, 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-41641

Explore →

Is Your Infrastructure Affected by CVE-2026-41641?

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

Start Free Scan →Browse All CVEs