CVE-2026-35465: Freedom SecureDrop Client RCE Vulnerability

CVE-2026-35465 Overview

SecureDrop Client is a desktop application used by journalists to securely communicate with sources and handle submissions on the SecureDrop Workstation. A critical path traversal vulnerability in versions 0.17.4 and below allows a compromised SecureDrop Server to achieve code execution on the Client's virtual machine (sd-app) by exploiting improper filename validation during gzip archive extraction. This flaw permits absolute paths in archive entries, enabling attackers to overwrite critical files such as the SQLite database used by the application.

Critical Impact

A compromised SecureDrop Server can achieve remote code execution on journalist workstations, potentially compromising the confidentiality, integrity, and availability of decrypted source submissions and endangering source anonymity.

Affected Products

• Freedom SecureDrop Client versions 0.17.4 and below
• SecureDrop Workstation sd-app virtual machines running vulnerable client versions
• Systems using the SecureDrop Client gzip extraction functionality

Discovery Timeline

• 2026-04-18 - CVE-2026-35465 published to NVD
• 2026-04-23 - Last updated in NVD database

Technical Details for CVE-2026-35465

Vulnerability Analysis

This vulnerability stems from improper filename validation during gzip archive extraction in the SecureDrop Client application. When processing archives received from the SecureDrop Server, the client fails to properly sanitize filenames, allowing entries with absolute paths or path traversal sequences to be extracted outside the intended directory. This flaw enables an attacker who has compromised the SecureDrop Server to craft malicious archives that overwrite critical application files upon extraction.

The attack requires prior compromise of the dedicated SecureDrop Server, which is itself a hardened system only accessible via Tor hidden services. Despite this prerequisite reducing the likelihood of exploitation, the vulnerability poses significant risk to journalist workstations if the server is compromised. The issue is related to CVE-2025-24888 but occurs through a different code path, indicating a systemic pattern in archive handling that required comprehensive remediation.

Root Cause

The root cause is classified as CWE-36 (Absolute Path Traversal). The SecureDrop Client's gzip archive extraction routine does not adequately validate or sanitize filenames within archive entries before writing them to disk. This allows archive entries containing absolute paths (e.g., /home/user/.config/securedrop/app.db) to be written directly to those locations rather than being constrained to the intended extraction directory.

Attack Vector

The attack vector is network-based and requires user interaction. An attacker must first compromise the SecureDrop Server, which serves as the intermediary between anonymous sources and journalists. Once the server is under attacker control, they can craft malicious gzip archives containing entries with absolute path filenames. When a journalist downloads and processes these submissions through the SecureDrop Client, the vulnerable extraction routine writes files to attacker-controlled locations on the sd-app virtual machine.

The most impactful target for overwriting is the application's SQLite database, which stores metadata about sources, submissions, and decrypted content. By replacing this database, an attacker could inject malicious content, corrupt evidence chains, or trigger further code execution through application logic that processes database contents.

Detection Methods for CVE-2026-35465

Indicators of Compromise

• Unexpected file modifications in critical application directories outside the normal submission extraction path
• SQLite database files with anomalous modification timestamps or unexpected content
• Archive entries containing absolute paths or ../ sequences in extraction logs
• Unusual file creation events in /home/user/.config/securedrop/ or system directories

Detection Strategies

• Monitor file system activity on sd-app virtual machines for writes to directories outside the expected submission storage locations
• Implement integrity monitoring for critical application files including the SQLite database
• Analyze network traffic from SecureDrop Servers for anomalous archive sizes or patterns
• Review application logs for extraction errors or unusual filename patterns in processed submissions

Monitoring Recommendations

• Deploy SentinelOne agents on journalist workstations to detect anomalous file system activity and potential code execution attempts
• Implement file integrity monitoring (FIM) for the SecureDrop Client application directory and configuration files
• Enable verbose logging for archive extraction operations to capture filename validation failures
• Monitor virtual machine snapshots for unexpected state changes that could indicate compromise

How to Mitigate CVE-2026-35465

Immediate Actions Required

• Upgrade SecureDrop Client to version 0.17.5 immediately on all journalist workstations
• Verify the integrity of existing SQLite databases and application files before and after upgrade
• Review SecureDrop Server logs for signs of compromise that could have enabled exploitation
• Consider rotating credentials and reviewing source communications if server compromise is suspected

Patch Information

Freedom of the Press Foundation has released version 0.17.5 of the SecureDrop Client to address this vulnerability. The fix implements more robust filename validation during gzip archive extraction, preventing absolute paths and path traversal sequences from being honored. A comprehensive fix has also been implemented in the replacement SecureDrop Inbox codebase for long-term remediation.

For detailed patch information, see the GitHub Security Advisory GHSA-2jrc-x8fq-prvc and the commit implementing the fix. The changelog documents the security fix in version 0.17.5.

Workarounds

• If immediate upgrade is not possible, temporarily disable automatic processing of submissions until patched versions can be deployed
• Implement additional network isolation for sd-app virtual machines to limit potential lateral movement
• Manually inspect downloaded archives before extraction using tools that can display entry filenames
• Consider reverting to clean virtual machine snapshots and processing only verified submissions until the patch is applied