CVE-2026-46548: NocoDB SSRF Protection Bypass Vulnerability
MODERATECVE-2026-46548 is a MODERATE (CVSS 4.3) ssrf protection bypass vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting NocoDB libraries in the npm ecosystem. The issue involves ssrf protection bypass in notification webhook plugins (slack, discord, mattermost, teams). Remediation is available in the latest vendor maintenance releases.
CVE-2026-46548 at a Glance
Security Impact
CVSS: 4.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2026-46548
To remediate this vulnerability, upgrade all affected NocoDB dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install nocodb@Latest secure releaseRun the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls nocodbHow to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-46548, inspect your project dependencies using npm:
npm ls nocodbAnalyze the terminal output to locate any version of NocoDB in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The npm ls nocodb command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In NocoDB, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-46548 Affected NocoDB Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
nocodb
|
npm |
≤ 0.301.3
|
|
References
Frequently Asked Questions
What is CVE-2026-46548?
Which NocoDB versions are affected?
What version fixes CVE-2026-46548?
Is nocodb affected?
What is the CVSS score of CVE-2026-46548?
What CWE is associated with CVE-2026-46548?
How can I check npm dependencies for CVE-2026-46548?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2c5x-4jgf-88mj",
"modified" : "2026-07-20T21:16:00Z",
"published" : "2026-05-21T20:34:28Z",
"aliases" : [ "CVE-2026-46548" ],
"summary" : "NocoDB: SSRF Protection Bypass in Notification Webhook Plugins (Slack, Discord, Mattermost, Teams)",
"details" : "### Summary\n\nThe `request-filtering-agent` SSRF protection was non-functional in the four notification webhook plugins (Slack, Discord, Mattermost, Teams) because `httpAgent` / `httpsAgent` were passed as part of the request **body** rather than the axios **config**. An authenticated user with hook-creation permission could direct outbound POST requests to arbitrary internal hosts.\n\n### Details\n\n`axios.post(url, data, config)` expects connection agents in the third (config) argument. In all four plugins, the agents were placed in the second (data) argument and serialised as JSON body content:\n\n```ts\n// packages/nocodb/src/plugins/slack/Slack.ts (and Discord / Mattermost / Teams — identical pattern)\nreturn await axios.post(webhook_url, {\n text,\n httpAgent: useAgent(webhook_url), // wrong position — serialised, not used\n httpsAgent: useAgent(webhook_url),\n});\n```\n\nThe webhook flow: an Editor+ user creates a webhook with `notification.payload.channels[].webhook_url` pointing to an internal host; on trigger, `WebhookInvoker.invoke()` calls the plugin's `sendMessage()` which performs the outbound `axios.post` with no SSRF filtering applied.\n\nThis is distinct from GHSA-xr7v-j379-34v9, which covers a blind SSRF via HEAD in the upload-by-URL path.\n\n### Impact\n\n- Authenticated user (Editor+) can reach cloud-metadata endpoints (`169.254.169.254`) and internal services.\n- Combined with verbose hook logging (`NC_AUTOMATION_LOG_LEVEL=ALL`), response bodies may be exfiltrated.\n\n### Credit\n\nThis issue was reported by [@ik0z](https://github.com/ik0z).",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "nocodb"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "0.301.3"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/nocodb/nocodb/security/advisories/GHSA-2c5x-4jgf-88mj"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46548"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/nocodb/nocodb"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-21T20:34:28Z",
"nvd_published_at" : "2026-06-23T21:16:58Z"
}
}