Skip to main content
VulnerabilityPublished

CVE-2026-71863: freedomofpress securedrop · Insertion of Sensitive Information Into Sent Data

Affects freedomofpress securedropSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.6 Low : upgrade to 2.16.1 when convenient.

Data as of 6 Nov 2026, 21:04 UTC

CVSS 3.1 base score
2.6Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.12.6
Patch
Available – fixed in 2.16.1
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade freedomofpress securedrop to 2.16.1.

Affected software

ProductAffectedFixed in
freedomofpresssecuredropAffected
  • >=2.13.0 <2.16.1
Fixed in
  • 2.16.1

AI-suggested

Upgrade SecureDrop to version 2.16.1 or later, where this issue is fixed. No other mitigation is required as the vulnerability is resolved in the official patch.

Description

A vulnerability in SecureDrop versions 2.13.0 through 2.16.0 allows sensitive Onion Service client authentication credentials to be copied to the Monitor Server when the securedrop-admin install Ansible playbook is run with journalist alerts disabled. This occurs because the journalist alert key filename is left empty, causing all files in the configuration directory to be transferred. The issue is fixed in version 2.16.1.

References

Community reviews

Loading reviews…