Back to the CVE list
CVE-2026-50000

SecureDrop: API session token reuse against the Journalist Interface web UI

CVSS score

5.0

EPSS probability

—

Risk score

0.5

Published

2 h ago

Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach AI Explanation

Verified against sources

SecureDrop: API Session Token Reuse Against the Journalist Interface Web UI

Sources read

1

Source agreement

Tam uyum

Evidence confidence

%55

Short explanation

SecureDrop's Journalist Interface allows API session tokens to be reused against the web UI due to a session key prefix corruption in SessionInterface.

Why does it matter?

An authorized attacker can reuse an acquired API session token against the web UI to perform broad actions on source submissions.

What should be done?

  • Follow vendor advisories
  • Update to fixed versions
  • Review session configurations
Chain of evidence and sources2 verified claims

SecureDrop 2.5.0 ile 2.16.0 sürümleri arasında Journalist Interface web arayüzü API oturum jetonunu kabul edebilir.

Saldırgan onion adresine, kimlik doğrulama erişimine ve geçerli bir API oturum jetonuna sahip olmalıdır.

Show the technical text from the sources

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.

CVSS vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:N

CWE: CWE-863

This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-50000 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1freedomofpresssecuredrop View
Total affected vendors: 1|Products: 1

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
5.0CVSS V3_1MEDIUMCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:NCVE CNA
5.0CVSS V31MEDIUMCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:NNVD

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-50000 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-50000 weaknesses.

Attack Vector and Accessibility

ExposureAğ üzerinden
PermissionsHigh
UserGerekmiyor

Official Sources and Advisories

CVSS Vector Radar Chart

5.0 / 10
Attack VectorNetworkComplexityHighPrivilegesHighUser Interact.NoneConfidentialityHighIntegrityNoneAvailabilityNone

Vulnerability Scoring Details

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:N
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredHigh privileges
User InteractionNone required
Confidentiality (Gizlilik)High
Integrity (Bütünlük)None
Availability (Erişilebilirlik)None

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

Weakness Type (CWE & CAPEC)

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-50000"
CVE-2026-50000 · SecureDrop: API session token reuse against…