HighCVE-2026-130007

    Reza-gholizade K8s-mcp-server: Missing Authentication for Critical Function (CVE-2026-130007)

    Published Last modified Sources: EUVD, OSV, Hersteller, CVE.org

    Share

    What is affected, what to do

    Update Reza-gholizade K8s-mcp-server to version 1.1.0.

    Affected
    • Reza-gholizade K8s-mcp-server lt *..1.1.0
    Fixed in
    • Reza-gholizade K8s-mcp-server 1.1.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.9

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    7.9

    CVSS v4

    Severity High on the scale from 0 to 10.

    Source: EUVD, OSV, Hersteller, CVE.org

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 31.6

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    77.49 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.9 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.9
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    31.6
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-306

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Summary

    When k8s-mcp-server runs in its default SSE transport mode, the MCP tools/call endpoint is dispatched with no authentication, session token, or Origin check. Any client that can reach the listening port can enumerate and invoke the server's Kubernetes tools (including destructive/write tools) without credentials, executing with the server's configured cluster privileges.

    Affected

    Commit be87a6dd72bb6ec1d4886b8548843b99a4638b12 (Merge PR #130) MCP library: github.com/mark3labs/mcp-go v0.57.0 Default mode: sse (SERVER_MODE default), default port 8080, bind 0.0.0.0

    Root cause (static trace: handleSSE -> handleMessage -> tools/call)

    • main.go L129: server.NewSSEServer(s) is created with no auth option and no contextFunc; L130 sse.Start(":"+port) binds all interfaces (0.0.0.0).
    • mcp-go sse.go handleSSE (GET /sse): no auth header check; the server mints a sessionId for any caller. The sessionId is a correlation value, not a credential.
    • handleMessage (POST /message): the only gates are method==POST and a loadable sessionId. No Authorization/Bearer/token/Origin/CSRF check before s.server.HandleMessage(ctx, rawMessage) dispatches to the tools/call handler.
    • Only Access-Control-Allow-Origin: * is present (CORS relaxation, not auth). Write tools (Create/Delete/RolloutRestart, Helm Install/Upgrade/Uninstall/Rollback) are all registered unless -read-only is set (default readOnly=false).

    Runtime reproduction (no auth headers on any request)

    Started: k8s-mcp-server -mode sse -port 8080 with a dummy non-routable KUBERNETES_SERVER=https://127.0.0.1:1 (no real cluster touched).

    GET /sse -> HTTP 200; server mints /message?sessionId=93b3... POST /message initialize -> HTTP 202; result returned over SSE POST /message tools/list -> HTTP 202; FULL tool list returned (incl. destructive) POST /message tools/call getAPIResources -> HTTP 202; handler EXECUTED: error -32603 "... Get https://127.0.0.1:1/api...: dial tcp 127.0.0.1:1: connect"

    The tools/call response is NOT HTTP 401/403 but an in-handler cluster-connection error, proving the RPC passed any authorization gate and reached the getAPIResources handler. With a valid kubeconfig, the same path returns real cluster data. ss -ltnp confirms LISTEN *:8080 (all interfaces, externally exposed).

    Impact

    An unauthenticated attacker with network reach to the port can enumerate tools and invoke Kubernetes operations with the server's privileges — cluster read and, with default readOnly=false, state-changing operations (Create/Delete/Helm). CWE-306 (Missing Authentication for Critical Function).

    Why this is a defect, not by-design

    Default mode is HTTP (sse) on 0.0.0.0:8080, containerized deployment is the normal scenario, and there is no "trusted client only" / auth-required note in the docs. MCP HTTP transports are expected to be loopback-only or gated; this one is neither.

    Suggested fix

    • Add an authorization gate before tools/call on the HTTP transports: e.g. WithSSEContextFunc to validate an Authorization bearer/token, or fail-closed when no token is configured in HTTP mode.
    • Default the bind to 127.0.0.1 and require explicit opt-in for external binding.
    • Document that HTTP mode must sit behind an authenticating proxy; recommend STDIO by default.

    Reproduction was done against the actual built binary and the shipped SSE path (not an extract).

    Credit

    bebold6133

    Source: ENISA EUVD, OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, CVE.org (MITRE), NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    reza-gholizadek8s-mcp-server
    • < 1.1.0
    • 1.1.0
    gogithub.com/reza-gholizade/k8s-mcp-server
    • < 1.1.0
    • —
    • 1.1.0
    • 1.1.0

    Vendors and products

    Weakness classes (CWE)

    • CWE-306Missing Authentication for Critical Function

      Base

      The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

      Entry at MITRE CWE-306

    References & sources

    • github.comreza-gholizade/k8s-mcp-server/commit/817d81005369837e0c03496278…x_refsource_MISC, euvd, web
    • github.comreza-gholizade/k8s-mcp-server/issues/131x_refsource_MISC, euvd, web
    • github.comreza-gholizade/k8s-mcp-server/pull/134x_refsource_MISC, euvd, web
    • github.comreza-gholizade/k8s-mcp-server/releases/tag/v1.1.0x_refsource_MISC, euvd, web
    • github.comreza-gholizade/k8s-mcp-server/security/advisories/GHSA-m932-63j…x_refsource_CONFIRM, euvd, web
    • NVD (NIST)vuln/detail/CVE-2026-130007advisory, euvd
    • github.comreza-gholizade/k8s-mcp-serverpackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. ReceivedGitHub

      Show 9 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      k8s-mcp-server manages Kubernetes clusters through the Model Context Protocol. Prior to 1.1.0, SERVER_MODE defaults to SSE, with the listener on 0.0.0.0:8080, but main.go creates the SSE server without an authentication option or context function. The GET /sse handler creates a sessionId that is only a correlation value, and the POST /message handler accepts a loadable sessionId without an authorization or Origin check before dispatching tools/call; consequently, any client able to reach the port can enumerate and invoke registered Kubernetes tools without credentials. Read-only mode is disabled by default, leaving write-capable Kubernetes tools available to run with the server's configured cluster privileges. This issue is fixed in version 1.1.0.
      CVSSadded
      —
      AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      Weakness type (CWE)added
      —
      CWE-306
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/130xxx/CVE-2026-130007.json">CVE-2026-130007</a>
      Referenceadded
      —
      https://github.com/reza-gholizade/k8s-mcp-server/commit/817d81005369837e0c034962785851ca4dec9a76
      Referenceadded
      —
      https://github.com/reza-gholizade/k8s-mcp-server/issues/131
      Referenceadded
      —
      https://github.com/reza-gholizade/k8s-mcp-server/pull/134
      Referenceadded
      —
      https://github.com/reza-gholizade/k8s-mcp-server/releases/tag/v1.1.0
      Referenceadded
      —
      https://github.com/reza-gholizade/k8s-mcp-server/security/advisories/GHSA-m932-63jc-4jqq

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-130007
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-130007"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-130007.svg?lang=en" alt="CVE-2026-130007 – NEOSEC Intel" height="20"></a>