dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-44719

MEDIUM · 5.3 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Mathesar versions 0.2.0 through 0.10.0 contain an IDOR vulnerability where the collaborators.list, tables.metadata.list, explorations.list, and forms.list API endpoints accept a database_id parameter without verifying the requesting user has collaborator access to that database, allowing authenticated users to view sensitive metadata including collaborator mappings, table metadata, exploration metadata, and form tokens for databases they are not authorized to access.

MitigationUpgrade to Mathesar 0.10.0 or later which implements proper authorization checks for all database metadata endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mathesar version
    Locate and determine the installed Mathesar version in your environment using your package manager, container labels, or installation documentation
    Affected if The installed version falls between 0.2.0 and 0.10.0 inclusive
  2. Confirm API endpoints are exposed
    Verify whether the API endpoints collaborators.list, tables.metadata.list, explorations.list, and forms.list are accessible in your deployment
    Affected if Any of these four endpoints are exposed and reachable
  3. Check authentication is enabled
    Determine if user authentication is configured and functional in your Mathesar instance
    Affected if Users can authenticate to the system, as the vulnerability requires an authenticated user context
  4. Test database_id parameter authorization
    Using an authenticated session, attempt to access one of the affected endpoints with a database_id for a database the user should not have access to
    Affected if The endpoint returns metadata for databases the authenticated user is not authorized to access

Your environment is affected if Mathesar version 0.2.0 through 0.10.0 is installed, the affected API endpoints are exposed, and users can access metadata for databases they are not authorized to view.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Mathesar 0.10.0 or later which implements proper authorization checks for all database metadata endpoints.

Recommended fix High confidence

0.10.0

  1. Identify the currently installed Mathesar version using the deployment method (e.g., docker images, package manager, or configuration files)
  2. Stop the Mathesar service to prevent access during the upgrade
  3. Back up the Mathesar database and configuration files
  4. Upgrade Mathesar to version 0.10.0 using the appropriate method (e.g., docker pull mathesar/mathesar:0.10.0, pip install mathesar==0.10.0, or Helm upgrade for Kubernetes deployments)
  5. Verify the upgrade was successful by checking the version number
  6. Restart the Mathesar service
  7. Verify that the authorization checks now properly validate user collaboration status before returning metadata

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44719 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data