CISA ADP Vulnrichment

Answer in brief

CVE-2026-79534 records a Medium severity (CVSS 5.9) vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 29, 2026Updated Sep 30, 2026Source checked Sep 30, 2026First seen by HOL Sep 29, 2026Material review Sep 30, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.9
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
n/a/n/ageneric	n/a	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for n/a/n/a.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 29, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 29, 2026

Sources and claim methodology

Source referencetraceforce.ai

Upstream source description

mark3labs mcp-filesystem-server v0.11.1 is vulnerable to Directory Traversal due to an improper link resolution in validatePath (filesystemserver/handler/helper.go). When filepath.EvalSymlinks returns os.IsNotExist for a dangling symlink, the fallback validates only the parent directory and returns the unresolved path, so write_file (and modify_file, copy_file, move_file, create_directory) follows a pre-existing dangling symlink located inside an allowed directory and creates a file outside the configured allowed directories.

Quoted source text, attributed separately from HOL analysis.