CVE-2026-119715 NocoDB before 2026.08.0 Clickjacking via Missing Frame-Control Headers
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-119715 and fix it if it is affected.
What it is: CVE-2026-119715 is a medium-severity vulnerability in nocodb, published on 30 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-119715 in the wild and no public exploit code.
Affected product: nocodb. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-119715/ (Markdown: https://insights.sbomify.com/CVE-2026-119715/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119715?
CVE-2026-119715 is a medium-severity vulnerability in nocodb, published on 30 Oct 2026.
Official description
NocoDB before 2026.08.0 contains a clickjacking vulnerability that allows any origin to frame the authenticated interface because no X-Frame-Options or CSP frame-ancestors headers are sent. Attackers can overlay a signed-in user's session from a malicious page, tricking clicks that modify or delete records, change sharing settings, or invite collaborators.
Weakness: CWE-1021
Which versions are affected by CVE-2026-119715?
How do I fix CVE-2026-119715?
No fix has been published for CVE-2026-119715 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119715 being exploited?
There is no known exploitation of CVE-2026-119715 in the wild and no public exploit code.
Sources
Also known as GHSA-2jgj-7q9p-vq8v, GHSA-3rj6-rvwh-j2xg.