<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:pgedge:postgres_mcp:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3apgedgepostgres_mcp/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 10 Nov 2026 18:59:43 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3apgedgepostgres_mcp/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>pgEdge Postgres MCP Server: Login rate limiting bypass (CVE-2026-125321)</title><link>https://feed.craftedsignal.io/briefs/2026-11-pgedge-mcp-rate-limit-evasion/</link><pubDate>Tue, 10 Nov 2026 18:59:43 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-pgedge-mcp-rate-limit-evasion/</guid><description>pgEdge Postgres MCP Server versions prior to 1.1.0 contain a vulnerability where an attacker can bypass login rate limiting by manipulating the X-Forwarded-For HTTP header.</description><content:encoded><![CDATA[<p>pgEdge Postgres MCP Server versions prior to 1.1.0 contain a vulnerability (CVE-2026-125321) in the login rate limiting mechanism. The implementation relies on the leftmost value of the caller-supplied 'X-Forwarded-For' header to identify the client IP address. An attacker can manipulate this header to rotate perceived IP addresses, thereby evading rate limiting or exhausting the rate limit bucket of other users. This issue is reachable when the HTTP transport is enabled, especially if the deployment configuration appends rather than replaces the 'X-Forwarded-For' header.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to bypass login rate limits, facilitating brute-force or credential stuffing attacks against the Postgres MCP server.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade pgEdge Postgres MCP Server to version 1.1.0 or later immediately.</li>
<li>Review ingress and proxy configurations to ensure that 'X-Forwarded-For' headers are sanitized and correctly replaced by trusted upstream proxies before reaching the application.</li>
<li>Audit logs for repeated login failures originating from diverse or suspicious 'X-Forwarded-For' header values.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category></item></channel></rss>