{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-126196 in the wild and no public exploit code.","exposure":"Only installations with a non-default setting turned on are exposed.","fix":"No fix has been published for CVE-2026-126196 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-126196 is a high-severity security feature bypass vulnerability in pgedge-postgres-mcp, published on 12 Nov 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-126196 and fix it if it is affected.\n\nWhat it is: CVE-2026-126196 is a high-severity security feature bypass vulnerability in pgedge-postgres-mcp, published on 12 Nov 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-126196 in the wild and no public exploit code.\nExposure: Only installations with a non-default setting turned on are exposed.\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-126196/ (Markdown: https://insights.sbomify.com/CVE-2026-126196/index.md)","id":"CVE-2026-126196","markdown":"https://insights.sbomify.com/CVE-2026-126196/index.md","name":"CVE-2026-126196","record":{"aliases":["GHSA-j7mp-839j-jrm7"],"analysis":{"component_type":"developer_tool","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Postgres MCP server","requires_auth":"low_privilege","requires_specific_call":false,"summary":"Callers can smuggle SQL through query_database on read-only connections to modify data and leave later calls writable; pgEdge users should care.","user_interaction":"not_required","vuln_class":"security_feature_bypass","vulnerable_functions":["query_database"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, query_database on a read_only connection could send unrecognized statements through pgx Exec without bind parameters, selecting PostgreSQL's simple query protocol and allowing multiple semicolon-separated statements in one request. A caller could combine transaction or session state changes with database writes, and pooled session state could leave later calls writable, when the connecting role held write privileges. The flaw affected deployments relying on read_only as a safety boundary, could compromise integrity and availability, and did not add confidentiality impact beyond the reads already permitted by the connection. 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 read-only mode can be bypassed by SQL statement smuggling through query_database","id":"CVE-2026-126196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"pgEdge Postgres MCP Server SQL injection through custom pl-do tool parameters","id":"CVE-2026-126197"},"nickname":null,"packages":[],"prev":{"headline":"Denial of service in soupsieve","id":"CVE-2026-126193"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-12","vendors":["pgEdge"]},"summary":"Callers can smuggle SQL through query_database on read-only connections to modify data and leave later calls writable; pgEdge users should care.","url":"https://insights.sbomify.com/CVE-2026-126196/"}