Skip to main content
Menu
CVEs

CVE

NocoDB webhook credential exposure in plugin list endpoint

Affects NocoDB versions before 2026.09.0, where a user with the workspace Creator role could read plaintext notification webhook URLs. Fixed in 2026.09.0.

CVE-2026-130708EUVD-2026-128780GHSA-8XRQ-5WQW-QQVQPublished Updated Summary written by a model

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 2026.09.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2026.09.0.

Summary

NocoDB before 2026.09.0 contains an improper authorization vulnerability that allows workspace Creator users to read plaintext notification webhook URLs by querying the webhook plugin listing endpoint. Attackers can replay exposed Slack, Teams, Discord and Mattermost webhook URLs directly against messaging providers to post arbitrary messages into organization chat channels.

Who should check

Teams running NocoDB below 2026.09.0 that have workspace Creator users, especially those with Slack, Teams, Discord or Mattermost notification webhooks configured.

“Affected versions < 2026.09.0”

github.com

cve.now Index

29Pcve.now Index 29 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • 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 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

What to do

  • Upgrade 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-130708 (NocoDB before 2026.09.0 Webhook Credential Exposure via Plugin List Endpoint), 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-130708 (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 are affected. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-pfc5-x523-xcj4)
- The attacker must hold the workspace Creator role on a workspace. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-pfc5-x523-xcj4)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130708 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130708 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-pfc5-x523-xcj4
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-130708
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-130708"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • nocodb nocodb

    fixed in 2026.09.0

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nocodb/nocodb · Advisory GHSA-pfc5-x523-xcj4
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130708
RecordNVD · CVE-2026-130708

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130708

Is CVE-2026-130708 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 user with the Creator role on any workspace could read every notification webhook URL configured on the instance in plaintext. Those URLs (Slack, Teams, Discord, Mattermost) work as bearer tokens and can be used outside NocoDB to post messages into the organization's chat channels.Source: github.com

Which versions are affected by CVE-2026-130708?

nocodb: before 2026.09.0.Source: cve.now feed data

Am I affected, and how do I check?

NocoDB versions before 2026.09.0 are affected. The exposure involves instances with notification webhooks configured and users holding the Creator role on a workspace. Check the NocoDB version number of your instance against 2026.09.0.Source: github.com

How do I fix CVE-2026-130708?

Upgrade NocoDB to version 2026.09.0 or later, which is the fixed version listed for this vulnerability.Source: github.com

More CVEs