# CVE-2026-44719: Mathesar: Missing collaborator checks allowed access to database-scoped Mathesar metadata

> Authenticated users can access unauthorized database metadata and form tokens due to missing collaborator checks, potentially allowing form submissions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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:** 15 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-jh9v-hqw8-5cq8

## What is CVE-2026-44719?

CVE-2026-44719 is a medium-severity missing authorization vulnerability in mathesar-foundation mathesar, published on 15 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mathesar is a web application that makes working with PostgreSQL databases both simple and powerful. From 0.2.0 to before 0.10.0, collaborators.list, tables.metadata.list, explorations.list, and forms.list accept a database_id without verifying that the requesting user was a collaborator on that database. An authenticated user on the same Mathesar installation could use these methods to view Mathesar-managed metadata for databases where they were not a collaborator. Depending on the database and features in use, exposed metadata could include collaborator mappings, table metadata, saved exploration metadata, and form metadata. For forms, the exposed metadata included form tokens. For public forms, possession of the token is equivalent to possession of the public form link, which allows submission to the form under the form’s configured PostgreSQL role. This vulnerability is fixed in 0.10.0.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-44719 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44719 is a medium-severity missing authorization vulnerability in mathesar-foundation mathesar, published on 15 May 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-44719 in the wild and no public exploit code.

Affected product: mathesar-foundation mathesar. 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-44719/ (Markdown: https://insights.sbomify.com/CVE-2026-44719/index.md)
```

## Sources

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

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