CVE-2026-46548: NocoDB Webhook SSRF Vulnerability – Patch & Detection Guide

Technical summary

NocoDB versions prior to 2026.04.1 fail to enforce SSRF protections in the notification webhook plugins for Slack, Discord, Mattermost, and Teams. The vulnerability arises because httpAgent and httpsAgent parameters—which control proxy and certificate validation behavior—are incorrectly passed within the request body instead of the axios HTTP client configuration object. An authenticated attacker can manipulate these parameters to direct outbound POST requests to arbitrary internal IP addresses or hostnames, circumventing network segmentation policies. The attack requires valid credentials and hook-creation permissions within the NocoDB instance.

Business impact

While the CVSS score is moderate (4.3), the practical impact depends on deployment context. In environments where NocoDB instances have network access to sensitive internal services (databases, APIs, administrative interfaces), a compromised or malicious user with webhook creation privileges could reconnaissance or interact with those backends without direct access. In cloud or shared hosting scenarios, this could enable lateral movement. Organizations using NocoDB in air-gapped or heavily segmented networks face lower risk. The requirement for authentication limits exposure to insider threats or credential compromise scenarios.

Affected systems

NocoDB installations prior to version 2026.04.1 are affected. The vulnerability is specific to the four notification webhook plugins (Slack, Discord, Mattermost, Teams) and requires the attacker to hold webhook creation permissions within a NocoDB instance. Community deployments, self-hosted instances, and managed NocoDB services running unpatched versions are all susceptible. No vendor advisory indicates widespread pre-release exploitation.

Exploitability

Exploitation requires valid NocoDB user credentials and explicit permission to create webhooks—typically a privilege restricted to workspace administrators or designated integrators. The attack is not remotely exploitable without authentication. No public exploit code or weaponized proof-of-concept has been disclosed as of the advisory date. An attacker would need to craft a webhook request with malformed agent parameters and have detailed knowledge of target internal infrastructure to succeed. The barrier to exploitation is moderate: authentication plus privilege requirements, but straightforward once those preconditions are met.

Remediation

Upgrade NocoDB to version 2026.04.1 or later, which corrects the HTTP agent configuration to properly pass these settings through the axios client options rather than the request body. For organizations unable to patch immediately, restrict webhook creation permissions to fully trusted administrators and implement egress firewall rules to prevent NocoDB instances from reaching sensitive internal services. Monitor webhook creation and modification events for suspicious activity.

Patch guidance

Apply NocoDB version 2026.04.1 or newer through your standard deployment mechanism (Docker image update, npm package upgrade, or managed service upgrade if applicable). Verify the patch is in place by checking the running version in the NocoDB admin interface or application logs. No special migration or configuration changes are required post-upgrade. Test webhook functionality with Slack, Discord, Mattermost, and Teams integrations after patching to confirm normal operations are restored.

Detection guidance

Monitor NocoDB webhook logs and activity for unusual webhook creation or modification by non-administrative users. Flag webhook requests that target internal IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or localhost. Examine HTTP access logs on internal services for unexpected POST requests originating from NocoDB instances. Alert on webhook plugins that fail with suspicious timing or frequency. Implement network-layer detection by alerting on outbound connections from NocoDB to internal-only network segments.

Why prioritize this

Although CVSS scoring is moderate, prioritize patching in the following order: (1) NocoDB instances with administrative users or high-privilege accounts, particularly if those users are contractors or temporary staff; (2) instances with network visibility to production databases, APIs, or administrative consoles; (3) environments where webhook creation is broadly permitted. Lower priority for air-gapped deployments, single-admin environments with strong access controls, or instances without internal network reach.

Risk score, explained

The CVSS v3.1 score of 4.3 (MEDIUM) reflects a network-accessible attack requiring authentication and low privileges, resulting in confidentiality impact but no integrity or availability loss. The score appropriately captures that this is an internal reconnaissance vector rather than a critical system compromise. However, organizational risk is context-dependent: in zero-trust or highly segmented networks, actual risk is lower; in flat networks with permissive webhook policies, risk is elevated.

Frequently asked questions