{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-125320 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-125320 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-125320 is a medium-severity vulnerability in pgedge-postgres-mcp, published on 10 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-125320 and fix it if it is affected.\n\nWhat it is: CVE-2026-125320 is a medium-severity vulnerability in pgedge-postgres-mcp, published on 10 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-125320 in the wild and no public exploit code.\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-125320/ (Markdown: https://insights.sbomify.com/CVE-2026-125320/index.md)","id":"CVE-2026-125320","markdown":"https://insights.sbomify.com/CVE-2026-125320/index.md","name":"CVE-2026-125320","record":{"aliases":["GHSA-6hg5-9f3w-c886"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, the HTTP transport did not validate the Origin header on incoming requests. A user who visited an attacker-controlled page could be targeted through DNS rebinding, allowing the page to reach a locally running server and read schemas and query results from configured databases. The issue affected deployments with the HTTP transport enabled on a machine that also ran a browser, while the default stdio transport was not reachable through this path. This issue is fixed in version 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 did not validate the Origin header, allowing DNS rebinding","id":"CVE-2026-125320","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"pgEdge Postgres MCP Server login rate limiting can be evaded by a caller-supplied header","id":"CVE-2026-125321"},"nickname":null,"packages":[],"prev":{"headline":"AsiaInfo Business Support System (BSS) Missing JWT Signature Verification","id":"CVE-2026-125298"},"products":["pgedge-postgres-mcp"],"published":"2026-11-10","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-10","vendors":["pgEdge"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-125320/"}