Securedrop
Approved changes feed: RSS · Atom
cpe:2.3:a:freedomofpress:securedrop:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Freedomofpress (16237b01-08b4-5b3b-9050-99901ddaa96c) |
|---|---|
| Product | Securedrop (b6b0149b-a16b-586c-8a9d-1fb7cfd14bac) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-71863 |
vulnerable | 2026-11-19 05:27:55.530083 |
SecureDrop: Onion Service client auth credentials copied to Monitor Server
LOW (2.6)
SecureDrop is an open-source whistleblower submission system that media organizations can use to securely accept documents from, and communicate with anonymous sources. From 2.13.0 until 2.16.1, running the securedrop-admin install Ansible playbook with journalist alerts disabled leaves the journalist alert key filename empty, causing the copy task to transfer every file in ~/.config/securedrop-admin/, including Onion Service client authentication credentials, to the Monitor Server. An attacker must first compromise the privileged Monitor Server to obtain the credentials, and the credentials remain an additional protection layer rather than sufficient access by themselves because the Journalist Interface still requires a username, passphrase, and MFA, while SSH access still requires SSH keys. This issue is fixed in version 2.16.1.
Published: 2026-11-06T20:58:10.211Z
Updated: 2026-11-10T20:13:25.018Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.