CVE
NocoDB private key disclosure in data source reads
Only affects NocoDB before 2026.09.0 where a data source uses TLS client-certificate authentication. Fixed in 2026.09.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.09.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. NocoDB versions before 2026.09.0 The data source is configured with TLS client-certificate authentication
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.23% · 14th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
NocoDB before 2026.09.0 contains an information disclosure vulnerability that allows authenticated base Viewers to obtain TLS client private keys by reading a base's data source. The source read handler masked only the connection password, letting attackers retrieve the decrypted private key, client certificate and CA to connect directly to the external database, bypassing NocoDB permissions.
Who should check
Teams running NocoDB before 2026.09.0 that connect base data sources to external databases using TLS client-certificate authentication, and anyone granting base Viewer access.
“Affecting nocodb >= 0, < 2026.09.0”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
NocoDB versions before 2026.09.0 The data source is configured with TLS client-certificate authenticationUpgrade 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-126271 (NocoDB before 2026.09.0 TLS Private Key Exposure via Data Source Read), 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-126271 (entry last updated 2026-11-13):
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 (source: https://www.vulncheck.com/advisories/nocodb-before-2026.09.0-tls-private-key-exposure-via-data-source-read)
- The data source is configured with TLS client-certificate authentication (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-rjc4-j36j-gjjc)
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-126271 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126271 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-rjc4-j36j-gjjc
- https://www.vulncheck.com/advisories/nocodb-before-2026.09.0-tls-private-key-exposure-via-data-source-read
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-126271
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-126271"}.Public exploit activity
- EPSS: 0.23%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
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.09.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126271
Is CVE-2026-126271 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 read-only member of a base can obtain the TLS client private key, client certificate and CA for the base's external database, plus its host and username. They can then connect directly to that database, bypassing NocoDB permissions.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126271?
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 when a data source is configured with TLS client-certificate authentication. Checking the NocoDB version and whether a data source uses TLS client-certificate authentication shows which setup applies.Source: vulncheck.com, github.com
How do I fix CVE-2026-126271?
Upgrade NocoDB to 2026.09.0 or later, which is the listed fixed version. No vendor patch ids or workaround are given in the facts.Source: vulncheck.com, github.com