Skip to main content
VulnerabilityPublished

CVE-2026-130707: nocodb · Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

Affects nocodbSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 2026.10.1 when convenient.

Data as of 18 Nov 2026, 12:19 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.02.3
CNA (VulnCheck)CVSS 3.14.2
Patch
Available – fixed in 2026.10.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 17 Nov 2026.

What to do

Upgrade nocodb to 2026.10.1.

Affected software

ProductAffectedFixed in
nocodbnocodbAffected
  • >=0.301.4 <2026.10.1
Fixed in
  • 2026.10.1

AI-suggested

Upgrade NocoDB to version 2026.10.1 or later, where the nc_token session cookie is set with the Secure attribute. This ensures the cookie is only transmitted over HTTPS, preventing exposure over plain HTTP. No other mitigation is required as the issue is fixed in the official release.

Description

NocoDB versions from 0.301.4 up to but not including 2026.10.1 have a vulnerability where the nc_token session cookie is set without the Secure attribute in HTTPS sessions. This allows network attackers to potentially capture the session token by observing or inducing plain HTTP requests to HTTPS instances, enabling session impersonation until the token expires. The issue is fixed in version 2026.10.1.

References

Community reviews

Loading reviews…