{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-126198 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-126198 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-126198 is a low-severity missing authorization vulnerability in pgedge-postgres-mcp, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-126198 and fix it if it is affected.\n\nWhat it is: CVE-2026-126198 is a low-severity missing authorization vulnerability in pgedge-postgres-mcp, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-126198 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: pgedge-postgres-mcp. 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-126198/ (Markdown: https://insights.sbomify.com/CVE-2026-126198/index.md)","id":"CVE-2026-126198","markdown":"https://insights.sbomify.com/CVE-2026-126198/index.md","name":"CVE-2026-126198","record":{"aliases":["GHSA-v44x-hxg7-5cgc"],"analysis":{"component_type":"developer_tool","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP database server","requires_auth":"none","requires_specific_call":false,"summary":"Custom MCP tools in pgEdge Postgres MCP Server ran writes without user confirmation, letting models or instructions modify database data.","user_interaction":"required","vuln_class":"missing_authorization","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-357","name":"Insufficient UI Warning of Dangerous Operations"}],"description":"pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, the bundled clients, including the CLI and web client, decided whether to request write confirmation by checking only for the query_database tool name instead of server-published write annotations. Custom pl-do, pl-func, and writing sql tools therefore ran without confirmation on allow_writes connections, including when a model followed instructions in retrieved content. The affected control is a bundled-client warning rather than a server authorization boundary, and other MCP clients do not inherit that prompt. This issue is fixed in 1.1.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":"pgEdge Postgres MCP Server custom tools performed writes without user confirmation","id":"CVE-2026-126198","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"pgEdge Postgres MCP Server write confirmation skipped for writes that begin with a reading keyword","id":"CVE-2026-126199"},"nickname":null,"packages":[],"prev":{"headline":"pgEdge Postgres MCP Server SQL injection through custom pl-do tool parameters","id":"CVE-2026-126197"},"products":["pgedge-postgres-mcp"],"published":"2026-11-12","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-12","vendors":["pgEdge"]},"summary":"Custom MCP tools in pgEdge Postgres MCP Server ran writes without user confirmation, letting models or instructions modify database data.","url":"https://insights.sbomify.com/CVE-2026-126198/"}