# CVE-2026-55664: Grist: Insufficient access control in the /forms endpoint exposes table metadata

> Attackers with partial read access can view hidden table and column metadata via the /forms endpoint, bypassing document access rules.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-w2hc-w6cg-xvh9

## What is CVE-2026-55664?

CVE-2026-55664 is a medium-severity missing authorization vulnerability in gristlabs grist-core, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grist is spreadsheet software using Python as its formula language. Prior to 1.7.15, the GET /forms endpoint read table and column metadata without applying the document's access rules and did not check that the requested section was actually a form. A user with only partial read access, including public access on a publicly viewable document, could request the metadata of any widget and reveal table and column structure that access rules would otherwise hide, even in documents that contain no forms. This issue is fixed in version 1.7.15.

Weakness: CWE-285 (Improper Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

No fix has been published for CVE-2026-55664 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55664 being exploited?

There is no known exploitation of CVE-2026-55664 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55664 and fix it if it is affected.

What it is: CVE-2026-55664 is a medium-severity missing authorization vulnerability in gristlabs grist-core, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55664 in the wild and no public exploit code.

Affected product: gristlabs grist-core. 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-55664/ (Markdown: https://insights.sbomify.com/CVE-2026-55664/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55664
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55664
- OSV: https://osv.dev/vulnerability/CVE-2026-55664

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55664/
Summaries are generated and may contain mistakes; the official description above is the record.