CVE
NocoDB code execution via template injection in webhook helpers
Affects NocoDB before 2026.09.0 with webhooks enabled, where webhook creation and update are limited to the Creator or Owner base role. Fixed in 2026.09.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.09.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. NocoDB versions before 2026.09.0 with webhooks enabled Attacker must hold an authenticated account with the Creator or Owner base role, since webhook creation and update are restricted to those roles
Summary
NocoDB before 2026.09.0 contains a server-side template injection vulnerability that allows authenticated Creator or Owner users to execute JavaScript by abusing Handlebars webhook helpers. Attackers can supply property paths like constructor.constructor to pluck, sortBy, filter, or withSort helpers to reach the Function constructor and run operating-system commands.
Who should check
Teams running NocoDB before 2026.09.0 with webhooks, where users with Creator or Owner base roles can create or edit webhooks.
“Affected versions < 2026.09.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
NocoDB versions before 2026.09.0 with webhooks enabled Attacker must hold an authenticated account with the Creator or Owner base role, since webhook creation and update are restricted to those rolesUpgrade to a fixed version: 2026.09.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130709 (NocoDB before 2026.09.0 Server-Side Template Injection via Webhook Helpers), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130709 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.09.0
Fixed versions: 2026.09.0.
Conditions (all must be true for the bug to be hit):
- NocoDB versions before 2026.09.0 with webhooks enabled (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-72fw-g74f-8mwr)
- Attacker must hold an authenticated account with the Creator or Owner base role, since webhook creation and update are restricted to those roles (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-72fw-g74f-8mwr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130709 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130709 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nocodb/nocodb/security/advisories/GHSA-72fw-g74f-8mwr
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130709
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130709"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- nocodb nocodb
fixed in 2026.09.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-72fw-g74f-8mwr |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130709 |
| Record | NVD · CVE-2026-130709 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130709
Is CVE-2026-130709 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted webhook template can run arbitrary JavaScript in the NocoDB server process and, through it, operating-system commands with the server's privileges. The flaw is a server-side template injection in the webhook helpers.Source: github.com
Which versions are affected by CVE-2026-130709?
nocodb: before 2026.09.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 2026.09.0 with webhooks enabled are affected. Only accounts with the Creator or Owner base role can create or update webhooks, so that role is required. To check, compare the installed NocoDB version with 2026.09.0 and see whether webhooks are configured.Source: github.com
How do I fix CVE-2026-130709?
Upgrade NocoDB to 2026.09.0 or later, which is the fixed version listed for this vulnerability.Source: github.com