Answer in brief
CVE-2026-85620 records a Critical severity (CVSS 8.6) vulnerability in Postgres MCP Pro 0.3.0 Restricted-Mode Bypass via FROM-Clause Function. The current sources do not mark it as known exploited. The current feed maps crystaldba/postgres-mcp (generic), crystaldba/postgres-mcp (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps crystaldba/postgres-mcp (generic), crystaldba/postgres-mcp (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| crystaldba/postgres-mcpgeneric | 0 | Not reported |
| crystaldba/postgres-mcpgeneric | >=0 <=0.3.0 | Not reported |
Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 4, 2026
Postgres MCP Pro 0.3.0 contains a restricted-mode bypass vulnerability where function-name validation is not applied to RangeFunction nodes in FROM clauses. Attackers can execute file-reading functions like pg_read_file through FROM-clause syntax to read arbitrary files despite restricted-mode protections.
Quoted source text, attributed separately from HOL analysis.