Cyber Resilience

CVE-2026-33645

Path Traversal in Shaneisrael Fireshare 1.5.1

Published
26 March 2026
Modified
30 March 2026
Patch / advisory
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
EPSS Score 0.0043 37th percentile
Risk Priority 54 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-33645 is a high-severity Path Traversal (CWE-22) vulnerability in Shaneisrael Fireshare. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-33645 is an authenticated path traversal vulnerability (CWE-22, CWE-73) affecting Fireshare version 1.5.1, a self-hosted media and link sharing application. The issue resides in the chunked upload endpoint, where the `checkSum` multipart field is used directly in filesystem path construction without sanitization or containment checks. This allows attackers to write arbitrary files outside the intended upload directory to paths writable by the Fireshare process, such as `/tmp` in containerized deployments. The vulnerability has a CVSS v3.1 base score of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L), indicating high integrity impact with low availability impact and no confidentiality impact.

An authenticated attacker with low privileges can exploit this vulnerability over the network with low complexity and no user interaction required. By manipulating the `checkSum` field during a chunked upload, they can direct file writes to arbitrary locations accessible to the process, violating filesystem integrity and potentially enabling follow-on attacks based on the deployment environment, such as overwriting configuration files or staging payloads in shared directories.

GitHub security advisories (GHSA-7q8r-vpq3-89m7) and the release notes for Fireshare version 1.5.2 confirm that the issue is fixed in the updated version, recommending an immediate upgrade to mitigate the vulnerability.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Fireshare facilitates self-hosted media and link sharing. In version 1.5.1, an authenticated path traversal vulnerability in Fireshare’s chunked upload endpoint allows an attacker to write arbitrary files outside the intended upload directory. The `checkSum` multipart field is used directly in…

more

filesystem path construction without sanitization or containment checks. This enables unauthorized file writes to attacker-chosen paths writable by the Fireshare process (e.g., container `/tmp`), violating integrity and potentially enabling follow-on attacks depending on deployment. Version 1.5.2 fixes the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1574.007 Path Interception by PATH Environment Variable Stealth
Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34745Same product: Shaneisrael Fireshare
CVE-2026-47425Shared CWE-22, CWE-73
CVE-2026-33027Shared CWE-22, CWE-73
CVE-2026-53581Shared CWE-22, CWE-73
CVE-2026-55700Shared CWE-22, CWE-73
CVE-2026-26202Shared CWE-22, CWE-73
CVE-2026-32749Shared CWE-22, CWE-73
CVE-2026-33949Shared CWE-22, CWE-73
CVE-2026-15921Shared CWE-22, CWE-73
CVE-2026-39377Shared CWE-22, CWE-73

Affected Assets

shaneisrael
fireshare
1.5.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes special path elements before pathname construction occurs.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 partial match
prevents

Least-privilege file authorization directly limits damage from externally controlled paths.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.PS-06 partial match
prevents

Secure SDLC practices include input validation and path sanitization that eliminate this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

finds

Security testing in development catches path traversal via static/dynamic analysis.

mitigates

Information access restriction limits which files an application may read or write.

References