{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-44719 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44719 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-44719 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-44719 in the wild and no public exploit code.\n\nAffected product: mathesar-foundation mathesar. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44719/ (Markdown: https://insights.sbomify.com/CVE-2026-44719/index.md)","id":"CVE-2026-44719","markdown":"https://insights.sbomify.com/CVE-2026-44719/index.md","name":"CVE-2026-44719","record":{"aliases":["GHSA-jh9v-hqw8-5cq8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Mathesar web application","requires_auth":"low_privilege","summary":"Authenticated users can access unauthorized database metadata and form tokens due to missing collaborator checks, potentially allowing form submissions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Mathesar: Missing collaborator checks allowed access to database-scoped Mathesar metadata","id":"CVE-2026-44719","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OpenLearnX: Critical Authentication Bypass via JWT Signature Verification Disabled Leading to Account Takeover","id":"CVE-2026-44720"},"packages":[],"prev":{"headline":"Mathesar: Missing collaborator checks allowed access to saved explorations in other databases","id":"CVE-2026-44718"},"products":["mathesar"],"published":"2026-05-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-15","vendors":["mathesar-foundation"]},"summary":"Authenticated users can access unauthorized database metadata and form tokens due to missing collaborator checks, potentially allowing form submissions.","url":"https://insights.sbomify.com/CVE-2026-44719/"}