Skip to main content
VulnerabilityPublished

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

Affects Apache SkyWalking MCPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High · fixed in 0.2.0 : patch Apache SkyWalking MCP soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% 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:L/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Apr 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 30 Oct 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 of Apache SkyWalking MCP version 0.1.0 should upgrade to version 0.2.0, which contains the fix for this SSRF vulnerability. Patch status is confirmed by the vendor's recommendation to upgrade. No additional mitigation guidance is provided.

Description

Server-Side Request Forgery via SW-URL Header vulnerability in Apache SkyWalking MCP. This issue affects Apache SkyWalking MCP: 0.1.0. Users are recommended to upgrade to version 0.2.0, which fixes this issue.

References

Community reviews

Loading reviews…