CVE
NocoDB credential exposure in connection test endpoint
Affects NocoDB versions before 2026.10.1 for callers already authorized on an integration. CVSS scores it 7.1 (high). Fixed in 2026.10.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.10.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. NocoDB versions before 2026.10.1 Caller must already be authorized on an integration (authorized integration user)
Summary
NocoDB before 2026.10.1 contains a credential exposure vulnerability in the connection-test endpoint that allows authorized integration users to redirect stored credentials by overriding connection host, port, and user fields. Attackers can point the test at a server they control to capture offline-crackable PostgreSQL md5 or MySQL handshakes and recover the stored database password.
Who should check
Teams running NocoDB before 2026.10.1 that have integrations with saved database connections, in both Community and Enterprise editions.
“Affected versions < 2026.10.1”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
NocoDB versions before 2026.10.1 Caller must already be authorized on an integration (authorized integration user)Upgrade to a fixed version: 2026.10.1.
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-130696 (NocoDB before 2026.10.1 Credential Exposure via Connection Test 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-130696 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.10.1
Fixed versions: 2026.10.1.
Conditions (all must be true for the bug to be hit):
- NocoDB versions before 2026.10.1 (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-jcc2-3vff-7867)
- Caller must already be authorized on an integration (authorized integration user) (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-jcc2-3vff-7867)
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-130696 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130696 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-jcc2-3vff-7867
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-130696
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-130696"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nocodb nocodb
fixed in 2026.10.1
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-jcc2-3vff-7867 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130696 |
| Record | NVD · CVE-2026-130696 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130696
Is CVE-2026-130696 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 caller already authorized on an integration can point its stored credentials at a server it controls. It can then capture the stored database password through PostgreSQL md5 or MySQL challenge-response handshakes, which can be cracked offline.Source: github.com
Which versions are affected by CVE-2026-130696?
nocodb: before 2026.10.1.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.10.1 are in scope, and the issue applies to callers already authorized on an integration. To check a installation, compare its NocoDB version with 2026.10.1.Source: github.com
How do I fix CVE-2026-130696?
Upgrade NocoDB to 2026.10.1 or later, which is the listed fixed version.Source: github.com