AWS postgres MCP read-only denylist missed set_config()
Direct answer
AWS postgres MCP read-only denylist missed set_config(), also tracked as CVE-2026-85787 is a high-severity threat campaign HOL Guard tracked from Sep 4, 2026 to Sep 8, 2026, verified against 4 primary sources and last reviewed Sep 22, 2026. Active tracking has ended and the record remains published as a permanent historical research record.
AWS says awslabs postgres-mcp-server before 1.1.7 has incomplete SQL input validation that can let crafted SQL embedded in submitted content modify data beyond the intended read-only scope when an authenticated user interacts with the MCP server. AWS fixed CVE-2026-85787 in version 1.1.7.
Also tracked as CVE-2026-85787
- First observed
- Sep 4, 2026
- Last observed
- Sep 8, 2026
- Last reviewed
- Sep 22, 2026
- Tracking ended
- Sep 8, 2026
Record exports
Uncertainty and limitations
Read the evidence limits before acting on this record.
Exposure depends on an authenticated user interacting with attacker-controlled content through the MCP server. This record does not claim a direct unauthenticated network path to the server.
- Campaign tracks CVE-2026-85787 only.
- AWS lists impacted PyPI package versions as earlier than 1.1.7 and the resolution as version 1.1.7.
- The AWS bulletin describes an unauthenticated actor placing crafted SQL in submitted content that is processed when an authenticated user interacts with the MCP server.
- HOL blog is operator guidance.
Guard coverage and policy
What Guard's reviewed assertions do and do not claim for this campaign, and the reviewed starting points for defense.
No Guard coverage mapping or campaign-specific policy guidance is published for this record.
Safe next step. Campaign guidance is defensive context. It does not auto-apply policy or claim universal campaign coverage.
Timeline
Reviewed events, oldest first, each tied to a verified source.
- Disclosure
CVE-2026-85787 AWS postgres MCP denylist bypass disclosed.
- Vendor action
AWS lists awslabs postgres-mcp-server versions before 1.1.7 as impacted and version 1.1.7 as the resolution.
Publication clock: 432.6 hours from reviewed disclosure timestamp to HOL publication; 24-hour high target; historical backfill outside target.
Sources
Every claim on this record is traceable to the sources below.
Campaign questions, answered
AWS says awslabs postgres-mcp-server before 7 has incomplete SQL input validation that can let crafted SQL embedded in submitted content modify data beyond the intended read-only scope when an authenticated user interacts with the MCP server. HOL Guard tracked the campaign from Sep 4, 2026 to Sep 8, 2026.
No. Active tracking ended Sep 8, 2026; this page remains as a labeled historical research record and does not imply the threat is currently active.
The record cites 4 primary sources, names 0 reviewed artifacts, and was last fully reviewed Sep 22, 2026 by HOL Guard Security Publishing. Its uncertainty and limitations are stated on the record itself.
Campaign guidance is defensive context. It does not auto-apply policy or claim universal campaign coverage.
The permalink above is permanent. The full record can be downloaded from this page as JSON, an artifact CSV, and a STIX 2.1 bundle, and corrections can be requested through the published correction path on the record. Exposure depends on an authenticated user interacting with attacker-controlled content through the MCP server. This record does not claim a direct unauthenticated network path to the server.
Reviewed in full by HOL Guard Security Publishing.
- Published
- Last full review
- Last modified
Record HGTC-2026-7E8F30DB