CVE-2026-46548: NocoDB SSRF protection bypass in notification webhook plugins

CVE-2026-46548 · Severity: medium · CVSS 4.3 · Published 2026-06-23

NocoDB is a popular open-source database tool with a web-based interface that allows users to create automation webhooks for notifications to Slack, Discord, Mattermost, and Teams. A flaw in the webhook implementation allows authenticated users with editor privileges to bypass security controls and send requests to internal servers—including cloud infrastructure metadata endpoints—potentially exposing sensitive configuration and credentials. This could allow an attacker to discover and interact with internal systems that should not be directly accessible.

Technologies: nocodb (npm). Vendors: npm.

Quick answers

Is CVE-2026-46548 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46548 being exploited in the wild.
How severe is CVE-2026-46548?
Medium severity, with a CVSS score of 4.3, published 23 June 2026.
Which products and versions are affected?
nocodb (npm) <= 0.301.3, SEMVER:introduced=0,last_affected=0.301.3.
Is there a fix for CVE-2026-46548?
A patch was published on 2026-04-01: Fix released in version 2026.04.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46548 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-46548?
Check whether you run nocodb (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a Server-Side Request Forgery (SSRF) weakness in NocoDB's notification webhook plugins for Slack, Discord, Mattermost, and Teams. The root cause is a misplacement of axios HTTP(S) agent configuration: the httpAgent and httpsAgent objects are passed in the request data body (second argument to axios.post) instead of the config object (third argument), causing them to be JSON-serialized as body content rather than used for connection filtering. An authenticated user with Editor+ role and webhook-creation permission can create a webhook with a notification.payload.channels[].webhook_url pointing to an internal host (e.g., 169.254.169.254 for cloud metadata, or private services). When the webhook triggers, WebhookInvoker.invoke() calls the plugin's sendMessage() which executes the axios.post without SSRF filtering, allowing the attacker to reach internal targets. Response bodies can be exfiltrated if verbose logging (NC_AUTOMATION_LOG_LEVEL=ALL) is enabled. The vulnerability was patched in version 2026.04.1.

Affected products

  • NocoDB nocodb < 2026.04.1

Identifiers

  • CVE-2026-46548
  • GHSA-2c5x-4jgf-88mj

Timeline

  • 2026-05-21: disclosed: Security advisory published
  • 2026-04-01: patched: Fix released in version 2026.04.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.