Skip to main content
VulnerabilityPublished

CVE-2026-7788: Axle-Bucamp MCP-Docusaurus · Path Traversal

Affects Axle-Bucamp MCP-DocusaurusSource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Axle-BucampMCP-DocusaurusAffected
  • =404bc028e15ec304c9a045528560f4b5f27a17e0
Fixed in–

AI-suggested

Since the vendor has not responded or provided a fix, users should monitor the project repository for updates. Until a fix is available, consider implementing access controls or input validation at the deployment environment level to restrict path traversal attempts. Avoid exposing vulnerable endpoints to untrusted networks if possible.

Description

CVE-2026-7788 is a path traversal vulnerability in Axle-Bucamp MCP-Docusaurus affecting functions that handle document paths. The flaw allows remote attackers to manipulate the DOCS_DIR/path argument to access unauthorized files. The vulnerability has a medium severity with a CVSS 4.0 score of 6.9. The project uses a rolling release model, so specific affected or fixed versions are not clearly identified. The vendor has not yet responded or provided a patch. Exploit code has been publicly released, but no known active exploitation in the wild has been reported.

References

Community reviews

Loading reviews…