Skip to main content

NocoDB CVE-2026-116122

| EUVDEUVD-2026-109615 MEDIUM
Information Exposure (CWE-200)
2026-10-26 VulDB GHSA-cwjw-4x7p-f6xv
6.3
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach NocoDB sign-in endpoint remotely
  2. Exploit
    Manipulate salt argument to validateUser
  3. Impact
    Trigger unintended information disclosure

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets the Sign-in Endpoint specifically, via manipulation of the 'salt' argument handled by the AuthService.validateUser function in NocoDB versions up to 2026.07.0. Per the CVSS vector it is remote and unauthenticated (AV:N, PR:N, UI:N), but attack complexity is high (AC:H) and the input explicitly rates exploitability as 'difficult,' indicating conditions not fully under the attacker's control must align for success. The precise trigger beyond 'manipulation of the salt argument' is not described in the available sources, and no special configuration or deployment mode is cited as a prerequisite. The practical limiting factor is the high complexity/low reliability of the attack combined with low-only confidentiality impact (VC:L); there is no integrity or availability impact.

Impact

This is a moderate, lower-priority issue rather than an urgent one. The CVSS 4.0 base score is 6.3 (Medium), and the vector tells a consistent story: network-reachable (AV:N) and unauthenticated (PR:N, UI:N), but with explicitly high attack complexity (AC:H) and only low confidentiality impact (VC:L) with no integrity or availability impact (VI:N/VA:N). The input itself echoes this, describing exploitability as 'difficult.' There is no KEV listing and no EPSS score in the provided data, so there is no evidence of active exploitation or a high predicted exploitation probability; no public exploit or working PoC is identified in the references. The vuln.today decision label is 'this_month,' i.e. routine scheduled remediation, not act_now or emergency. The signals are internally consistent - high complexity plus low impact plus no exploitation evidence - pointing to a genuine but low-urgency information-disclosure flaw. Two caveats reduce confidence in the metadata rather than the severity: the vulnerability was reported by VulDB (a third party), and the vendor deleted the referenced GitHub issue (#14687) and did not respond to disclosure, so the mechanism and affected-version details have not been vendor-confirmed.

Exploit ScenarioDerived

A remote, unauthenticated attacker repeatedly interacts with the NocoDB sign-in endpoint, manipulating the 'salt' argument processed by AuthService.validateUser to coax the service into disclosing information it should not reveal. Because attack complexity is rated high and exploitability 'difficult,' success is not reliable and likely requires conditions outside the attacker's direct control. No public exploit or verified working PoC is identified in the available sources.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 26, 2026

Information disclosure in NocoDB through 2026.07.0 arises in the sign-in endpoint's AuthService.validateUser handling of the salt argument, enabling remote attackers to expose limited confidential data. Per the CVSS vector the issue is network-reachable and unauthenticated with no user interaction, but high attack complexity, a rating of difficult exploitability, and low-only confidentiality impact make this a moderate, lower-priority issue rather than an urgent one. No public exploit was identified at time of analysis, and no CISA KEV entry indicates active exploitation.

RemediationAI

No vendor-released patch is identified in the supplied references, and no fixed version is listed; the vendor did not respond to the disclosure and deleted the GitHub issue, so there is no exact update version to cite. Until a release beyond 2026.07.0 is published, reduce exposure by placing the NocoDB sign-in endpoint behind network allowlists, a VPN, or a zero-trust proxy so only trusted users can reach it; this will block legitimate remote sign-in unless users go through the proxy. Because the trigger beyond salt manipulation is not described, WAF signatures or parameter filtering for the salt argument cannot be reliably tuned and may break legitimate authentication. Monitor https://github.com/nocodb/nocodb/ and the VulDB entries at https://vuldb.com/vuln/426190 and https://vuldb.com/cve/CVE-2026-116122 for a fixed release and upgrade as soon as one is available.

Affected VersionsENISA

nocodb 2026.07

Affected Packages

euvd nocodb no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is classified CWE-200 (Exposure of Sensitive Information) and is located in the AuthService.validateUser function used by NocoDB's sign-in endpoint, specifically involving manipulation of the salt argument. The supplied CPE entry, cpe:2.3:a:n/a:nocodb:*:*:*:*:*:*:*:*, lists NocoDB without a version restriction, while the description bounds affected releases to 2026.07.0 and earlier. The available sources do not describe the precise trigger beyond salt manipulation, and no special configuration or deployment mode is cited as a prerequisite. The CVSS vector confirms network reachability, no required privileges, no user interaction, high attack complexity, unchanged scope, and only low confidentiality impact with no integrity or availability impact.

Know when Nocodb gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 6.3 MEDIUM
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 3.7 LOW

Remote unauthenticated sign-in endpoint (AV:N/PR:N/UI:N) but difficult to trigger (AC:H); only limited information disclosure, so C:L and I:N/A:N.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
High
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A security flaw has been discovered in NocoDB up to 2026.07.0. Impacted is the function AuthService.validateUser of the component Sign-in Endpoint. Performing a manipulation of the argument salt results in information disclosure. It is possible to initiate the attack remotely. The attack's complexity is rated as high. The exploitability is considered difficult. The vendor deleted the GitHub issue for this vulnerability without any explanation. Afterwards the vendor was contacted early about this disclosure via email but did not respond in any way.

Threat Intelligence Overview

EPSS Score
0.4%
Top 62% exploitable
Prevalence
Medium
popular open-source no-code database platform, not ubiquitous enterprise footprint
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Nocodb

View all
CVE-2026-24769 CRITICAL POC
9.0 Jan 28

NocoDB spreadsheet platform prior to 0.301.0 has a stored XSS vulnerability (CVSS 9.0) that enables code execution throu

CVE-2022-2064 HIGH POC
8.8 Jun 13

Insufficient Session Expiration in GitHub repository nocodb/nocodb prior to 0.91.7+. Rated high severity (CVSS 8.8), thi

CVE-2022-2063 HIGH POC
8.8 Jun 13

Improper Privilege Management in GitHub repository nocodb/nocodb prior to 0.91.7+. Rated high severity (CVSS 8.8), this

CVE-2023-35843 HIGH POC
7.5 Jun 19

NocoDB through 0.106.0 (or 0.109.1) has a path traversal vulnerability that allows an unauthenticated attacker to access

CVE-2022-2339 HIGH POC
7.5 Jul 07

With this SSRF vulnerability, an attacker can reach internal addresses to make a request as the server and read it's con

CVE-2022-2062 HIGH POC
7.5 Jun 13

Generation of Error Message Containing Sensitive Information in GitHub repository nocodb/nocodb prior to 0.91.7+. Rated

CVE-2023-5104 MEDIUM POC
6.5 Sep 21

Improper Input Validation in GitHub repository nocodb/nocodb prior to 0.96.0. Rated medium severity (CVSS 6.5), this vul

CVE-2022-3423 MEDIUM POC
6.5 Oct 07

Allocation of Resources Without Limits or Throttling in GitHub repository nocodb/nocodb prior to 0.92.0. Rated medium se

CVE-2026-24768 MEDIUM POC
6.1 Jan 28

NocoDB versions prior to 0.301.0 contain an open redirect vulnerability in the login flow where the `continueAfterSignIn

CVE-2025-27506 MEDIUM POC
5.4 Mar 06

NocoDB is software for building databases as spreadsheets. Rated medium severity (CVSS 5.4), this vulnerability is remot

CVE-2022-2079 MEDIUM POC
5.4 Jun 14

Cross-site Scripting (XSS) - Stored in GitHub repository nocodb/nocodb prior to 0.91.7+. Rated medium severity (CVSS 5.4

CVE-2022-2022 MEDIUM POC
5.4 Jun 07

Cross-site Scripting (XSS) - Stored in GitHub repository nocodb/nocodb prior to 0.91.7. Rated medium severity (CVSS 5.4)

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy