Skip to main content
VulnerabilityPublished Updated

CVE-2026-34884: Apache SkyWalking MCP · Server-Side Request Forgery (SSRF)

Affects Apache SkyWalking MCPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical · fixed in 0.2.0 : patch Apache SkyWalking MCP as a priority.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.2.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Software FoundationApache SkyWalking MCPAffected
  • =0.1.0
Fixed in–
Mavenorg.apache.skywalking/mcppkg:maven/org.apache.skywalking/mcpOther threatsAffected
  • =0.1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache SkyWalking MCP from version 0.1.0 to version 0.2.0, which contains the official fix for these vulnerabilities.

Description

Apache SkyWalking MCP version 0.1.0 contains a critical Server-Side Request Forgery (SSRF) vulnerability and a GraphQL expression injection issue. These vulnerabilities allow an attacker to manipulate server requests and inject malicious GraphQL expressions. The issue is fixed in version 0.2.0, which users are advised to upgrade to.

References

Community reviews

Loading reviews…