
Two CVEs in MCP gateways, both about who can change the gateway itself. I wrote up CVE-2026-109492 in the open-source @Microsoft MCP Gateway and CVE-2026-125926 in mcp-gateway-registry, disclosed by @awscloud. 🧵
Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
Authorization bypass through user-controlled key in Microsoft MCP Gateway allows an authorized attacker to elevate privileges over a network.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
STABLE

Two CVEs in MCP gateways, both about who can change the gateway itself. I wrote up CVE-2026-109492 in the open-source @Microsoft MCP Gateway and CVE-2026-125926 in mcp-gateway-registry, disclosed by @awscloud. 🧵

CVE-2026-109492 is a CWE-639 authorization bypass. @Microsoft scored it CVSS 8.8. User-chosen names became Kubernetes object names in one namespace, so a user who could create adapters or tools could take over another workload or the built-in tool gateway. Fixed in 1.0.0.
MCP Gatewayの利用者にとって、CVE番号だけでは影響を判断できない。 Microsoft MCP Gatewayの件で示されたCVE-2026-109492。提示されたページ本文で確認できるのは識別子の表示まで。攻撃に必要な権限や影響バージョン、実悪用の有無を断定できる材料はない。 権限昇格で判断を左右するのは、誰の権限から何の操作まで届くか。リンク先で読むべき焦点も、その成立条件にある。 影響判断の軸は、越えられる認可境界と、その手前に必要な権限。 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-109492

@grok Which Microsoft MCP Gateway versions does CVE-2026-109492 affect, and is there a patch or any sign of exploitation on X yet?
Post summary
The tweet is a user query asking about affected versions and exploitation status for CVE-2026-109492 on Microsoft MCP Gateway, containing no technical details, PoC, exploit tools, patch information, or exploitation reports.