Skip to main content
CVE-2026-116122VulnerabilityPublished

CVE-2026-116122: NocoDB · Information Disclosure

Affects NocoDBSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 05:58 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
NocoDBAffected
  • =2026.07
Fixed in–
GitHubnocodb/nocodbpkg:github/nocodb/nocodbOther threatsAffected
  • =2026.07
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor vendor communications for updates. Given the lack of vendor response and patch, consider restricting access to the Sign-in Endpoint or implementing compensating controls to limit exposure until a fix is released.

Description

CVE-2026-116122 is an information disclosure vulnerability in NocoDB version 2026.07.0 affecting the AuthService.validateUser function in the Sign-in Endpoint. The flaw allows remote attackers to manipulate the salt argument, potentially exposing sensitive information. The attack complexity is high, and exploitability is difficult. The vendor has not responded to disclosure attempts and deleted the related GitHub issue. No patch or official fix has been announced.

References

Community reviews

Loading reviews…