Cross-Site Scripting (XSS) in Fileserver upload API (CVE-2026-101158)
Summary
Cross-site scripting in Fileserver upload API (CVE-2026-101158). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
A missing input validation vulnerability in the Fileserver upload API allows an authenticated attacker with file upload privileges to execute stored cross-site scripting (XSS). Successful exploitation could enable the attacker to hijack another CloudVision user's web session, potentially granting full access to their account and administrative permissions.
Source: NIST National Vulnerability Database 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-101158 has been found in Fileserver upload API.
Successful exploitation can lead to full system takeover. CVSS score: 8.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Fileserver upload API CVE-2026-101158" on the vendor's site.
CVE-2026-101158 (Fileserver upload API) — CWE-79 / CVSS v3 8.4
Attack vector: remote (network-reachable)
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.
Cross-site scripting (XSS) (CWE-79) exists in Fileserver upload API.
Check the vendor advisory for the affected versions of Fileserver upload API.
Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Fileserver upload API を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web psirt@arista.com
- web nvd.nist.gov
- web github.com