CVE-2026-50000: freedomofpress securedrop · Incorrect Authorization
Affects freedomofpress securedropSource CVE Database V5
Not known to be exploited · CVSS 5.0 Medium : upgrade to 2.16.0 when convenient.
Data as of 30 Oct 2026, 17:18 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.0 |
|---|
- Patch
- Available – fixed in 2.16.0
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade freedomofpress securedrop to 2.16.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| freedomofpresssecuredrop | Affected
| Fixed in
|
Description
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.5.0 until 2.16.0, the `Journalist Interface` can accept an `API session` token against the `web UI` because its `SessionInterface` keeps a mutable session key prefix that changes with each request and persists across requests. API and web sessions were separated in `Redis` starting in version 2.5.0, but prefix corruption confuses those session namespaces. An attacker who already has access to the secret `Journalist Interface` onion address, the required authentication access and a recent nonexpired `API session` token can reuse that token against the `web UI` until its natural expiry, at most eight hours. The corrupted prefix can also prevent logout from deleting the correct `Redis` session, although normal expiry still applies. A compromised journalist can access encrypted submissions and perform broad actions on source submissions, but this issue does not expose plaintext submissions or affect the running system's availability. This issue is fixed in version 2.16.0.