Skip to content
KitploitKITPLOIT
उपकरणएक्सप्लॉइटब्लॉग
Log in
जमा करें
उपकरणएक्सप्लॉइटब्लॉग
जमा करें

हैकिंग, पेनटेस्ट और साइबर सुरक्षा उपकरण आपके सुरक्षा शस्त्रागार के लिए!

Kitploit हैकिंग, साइबर सुरक्षा और पेंटेस्टिंग टूल्स की एक निर्देशिका है। कमजोरियों को खोजने, सिस्टम का विश्लेषण करने, परीक्षण को स्वचालित करने और अपनी सुरक्षा को मजबूत करने के लिए नवीनतम प्रोजेक्ट अपडेट खोजें।

फ़ीडसंपर्कगोपनीयता© 2026 Kitploit

टूल निर्देशिका

श्रेणियाँ

सभी श्रेणियाँ देखें
Loading categories
mcp-remote-oauth-security — Forensic audit of mcp-remote OAuth trust boundaries: seven advisories and five CVE records covering SSRF via server-selected metadata URLs, redirect bypass and token storage, with loopback-canary reproductions. | Kitploit
उपकरण/GitHubGitHub/playb0t/mcp-remote-oauth-security
Vulnerability AnalysisInformation GatheringWeb SecurityPapers & ResearchCurated Resources
GitHubplayb0t/mcp-remote-oauth-security

mcp-remote-oauth-security

Forensic audit of mcp-remote OAuth trust boundaries: seven advisories and five CVE records covering SSRF via server-selected metadata URLs, redirect bypass and token storage, with loopback-canary reproductions.

रिपॉजिटरी देखें
3349घं 25मि पहलेअभी तक समीक्षित नहीं
वेबसाइट
साझा करें
अनुरोधित भाषा में सामग्री उपलब्ध नहीं है। अंग्रेज़ी संस्करण दिखाया जा रहा है।

Stylized OAuth trust-boundary cover for mcp-remote security research

mcp-remote OAuth Trust-Boundary Security Advisories

Five published CVE records, all scored by CISA-ADP, up to 9.8 Critical.
In the 19 November 2026 loopback runs, published CLI 0.16.7 reaches the server-selected metadata paths of CVE-2026-51994 and CVE-2026-51995; all seven original findings remain present.

CVE records CISA-ADP score Tested through Latest release Impact record

Research dossier, 9 October 2026 · 0.15.1 follow-up, 15 October 2026 · 0.15.2 / 0.16.0 follow-up, 3 November 2026 · 0.16.3 / 0.16.4 / 0.16.5 follow-up, 7 November 2026 · 0.16.6 assessment, 14 November 2026 · 0.16.7 assessment, 19 November 2026 · Procedure v2 and seven-version backfill, 7 November 2026 · MCP Host Matrix, 25 October 2026 · Advisory index · Impact ledger

Research update: 19 November 2026

All seven original findings remain in their recorded states and evidence classes on mcp-remote 0.16.7. The eleven credential-destination scenarios retain 9 PASS / 2 FAIL, and the initial/cache-r2/cache-r3 counts match 0.16.6, including the known fixture/postcondition errors. The release separates cache namespaces by expanded header value and retains portless loopback registrations. In a parser-to-provider control with B metadata supplied directly, the retained registration permits B to receive the client secret and refresh token assigned to A; the wrong-port control removes it on both versions. Both F-11 transport repeats observe no cross-origin Bearer transfer; F-04 and F-11 retain their hardening classifications. Results, redacted traces and limits. The full-CLI addendum confirms actual discovery, refresh credential receipt at B and a returned MCP initialize result for the portless 0.16.7 case. Its missing query channel is explicitly qualified: three direct FAIL and four INCONCLUSIVE.

Static-header update: 9 November 2026

In the static Bearer profile, published CLI 0.14.3 and 0.16.5 followed 401-selected metadata to a second loopback origin and, after the MCP POST was challenged, repeated the metadata requests carrying the configured Bearer. The no-resource_metadata controls did not contact the selected endpoints. Two-version static-header results are separate from earlier client-credentials profiles and do not change official CVE ranges.

Vendor response: WinCC OA, 9 November 2026

WinCC OA revised its assessment of CVE-2026-51995, published v1.5.3 documentation and closed issue #40 after release. The bridge remains pinned to 0.14.3 until a verified upstream fix; this vendor-case closure does not mean mcp-remote is fixed. Vendor statements, release and limits.

Executive summary

mcp-remote bridges stdio-only MCP clients to remote MCP servers and runs OAuth discovery on their behalf. That makes remote-server metadata a security boundary: a server-selected URL, redirect or credential destination must not become trusted because it appeared during discovery.

Seven advisories document the review of the release current at disclosure, 0.1.38: two localhost-canary reproductions, three bounded source reviews, two hardening records corrected in v1.0.1. The private report went to the maintainer on 17 February 2026; the public disclosure followed on 31 July after no acknowledgement; MITRE published five CVE records on 24 September 2026, and CISA-ADP scored all five. On 9 October 2026 the published 0.14.3 CLI, run in full in three local stdio scenarios, reproduced the F-01 / F-02 request path, HTTP 302 redirect included, and the discovery helpers executed in all 58 stable releases from 0.1.32 to 0.14.3. Between the private report and 7 October 2026 npm served 19,060,907 downloads of the package. The five follow-up releases 0.16.1 to 0.16.5 do not name the five records or announce a release addressing them; the ten selected first-party helpers are unchanged in the source comparisons, and 0.16.5 was compared in source/distribution and run through the original procedure, with all three CLI attempts stopping at its unchanged assertion. Release 0.16.6 of 11 November constrained credential-bearing grant redirects. Release 0.16.7 of 19 November names none of the five research records; in the 19 November runs all seven original findings remain in their recorded evidence classes. Its two cache changes are measured in the 0.16.7 assessment, including the separately bounded portless-registration path. On 14 October 2026 the maintainer published four releases, 0.14.4 through 0.15.1; none of them names a record. On 15 October the 9 October procedure was repeated on 0.15.1. It recorded the same F-01 / F-02 request paths. In the full trace it also recorded a token request, carrying an Authorization header, to the authorization server named by the server's own metadata, as it does in 0.14.3 runs under the same environment.

From 7 November 2026, procedure v2 is the primary local regression procedure. It checks credentials against a predeclared issuer and receiver policy after the trace is settled, with OAuth client authentication separate from resource Bearer. The seven-version backfill preserves the original procedure and its stops, and records execution outcomes separately from credential-destination verdicts.

टूल डाउनलोड करें

सबसे लोकप्रिय

सभी देखें →

हमारे समुदाय द्वारा सबसे अधिक उपयोग किए जाने वाले उपकरण खोजें।

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 अंतिम OSINT टूलकिट: जाँच ग्राफ़, विश्वास स्कोरिंग, उपनाम परिवार, मानचित्र, टाइमलाइन और रिपोर्ट। 49 मॉड्यूल, 400+ साइटें, किसी API कुंजी की आवश्यकता नहीं।

    927
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # घोस्टलॉक वन-टैप निष्पादन ऐप (CVE-2026-43499)

    555
  • 3

    redforge

    cybersecurity91/redforge

    ब्राउज़र-साइड रेड टीम टूलकिट, जिसमें रेकॉन, पेलोड जनरेशन, क्रेडेंशियल हमलों, क्रिप्टो, एन्कोडिंग और एंगेजमेंट रिपोर्टिंग के लिए 102 ऑफ़लाइन टूल्स हैं।

    360
  • 4

    ARTEX

    baarai/artex

    प्लानर/वर्कर एजेंट, एसेट और एक्सप्लोरेशन ग्राफ़, MITM ट्रैफ़िक रिकॉर्डिंग, और भेद्यता पुनःपरीक्षण के साथ LLM मल्टी-एजेंट स्वायत्त पेनेट्रेशन टेस्टिंग प्लेटफ़ॉर्म।

    357
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT प्लेटफ़ॉर्म जो Shadowserver रिपोर्ट्स को MongoDB में इनजेस्ट करता है और उन्हें इंटरैक्टिव मैप्स, विश्लेषण, निष्कर्षों, सलाहों और कार्यकारी डैशबोर्ड के रूप में पुनः प्रस्तुत करता है।

    324
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI-मूल साइबरसुरक्षा के लिए कार्रवाई की प्रणाली—जहाँ इरादा नियंत्रित निष्पादन बन जाता है, साक्ष्य परिचालन स्मृति बन जाता है, और हर ऑपरेशन अगले को बेहतर बनाता है।

    289

सभी उपकरण खोजें

हमारे उपकरणों का संग्रह ब्राउज़ करें

सभी उपकरण देखें →