Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-19324 low CVSS 3.3

Path Traversal in HelloGGX shadcn-vue-mcp (CVE-2026-19324)

Summary

Path traversal in HelloGGX shadcn-vue-mcp (CVE-2026-19324). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

A weakness has been identified in HelloGGX shadcn-vue-mcp up to e170e277b94235cde627803277fc8c41103a4d38. Affected by this issue is the function fs.promises.readFile of the file src/server/callback-server.ts. This manipulation of the argument filepath causes path traversal. The attack is restricted to local execution. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-19324 has been found in HelloGGX shadcn-vue-mcp.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "HelloGGX shadcn-vue-mcp CVE-2026-19324" on the vendor's site.

CVE-2026-19324 (HelloGGX shadcn-vue-mcp) — CWE-22 / CVSS v3 3.3
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in HelloGGX shadcn-vue-mcp.

📍 Affected scope

Check the vendor advisory for the affected versions of HelloGGX shadcn-vue-mcp.

🔥 Severity

Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで HelloGGX shadcn-vue-mcp を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details