Skip to main content

Wikipedia Android App EUVDEUVD-2026-87344

| CVE-2026-100379 MEDIUM
Information Exposure (CWE-200)
2026-09-25 wikimedia-foundation
5.3
CVSS 4.0 · Vendor: wikimedia-foundation
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register lookalike Wikimedia-suffix domain
  2. Delivery
    Lure user to attacker URL in app
  3. Exploit
    App matches domain via loose endsWith
  4. Execution
    CentralAuth cookies attached to request
  5. Impact
    Attacker captures session tokens

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the Wikipedia Android App's SharedPreferenceCookieManager to attach stored CentralAuth session cookies to a request destined for an attacker-controlled domain. The specific prerequisite is the flawed authority matching: the pre-fix code used domain.endsWith(domainSpec) and did not require BOTH the request domain and the cookie's stored domain to be Wikimedia authorities, so a domain crafted to end with an approved suffix (e.g. a lookalike registered domain) matches. The attacker must induce the logged-in user's app to issue a request to that domain (UI:P - passive user interaction, such as following a crafted link). Limiting factors: the user must be authenticated (holding CentralAuth cookies), the attacker must control a domain that both is reachable by the app and defeats the suffix check, and user interaction is required - there is no fully automated, zero-click remote path.

Impact

The vendor-supplied CVSS is 4.0-only (5.3, medium) with vector AV:N/AC:L/AT:N/PR:N/UI:P/VC:L - network reachable, low complexity, no privileges, but passive user interaction required and only limited confidentiality impact. There is no EPSS score, no CISA KEV listing, and no public exploit code, so this is not an urgent-priority item - it reads as a defense-in-depth cookie-scoping hardening fix rather than an actively exploited flaw. The signals are internally consistent: a medium CVSS driven down by UI:P and VC:L, with no exploitation-maturity evidence. One nuance the raw score understates: the leaked data is CentralAuth session/auth cookies, whose disclosure could enable account takeover, so real-world impact if exploited could exceed the 'VC:L' label - but this is gated behind the attacker persuading the app to contact a lookalike domain, which materially limits practicality. No SSVC decision data was provided in the input. Overall: low-to-medium real-world priority.

Exploit ScenarioDerived

An attacker registers a lookalike domain whose name ends with an approved Wikimedia authority string (the pre-fix code used a loose domain.endsWith(domainSpec) match, so e.g. 'evilwikipedia.org' satisfies the 'wikipedia.org' suffix test) and lures a logged-in Wikipedia Android App user into having the app issue a request to it. Because of the flawed authority matching, the app attaches the user's stored CentralAuth session cookies to that outbound request, disclosing them to the attacker. No public proof-of-concept exploit is identified; exploitation requires user interaction (UI:P) and an attacker-controlled domain the app can be induced to contact.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 25, 2026

The Wikipedia Android App's cookie manager could release Wikimedia CentralAuth session cookies to an attacker-controlled domain, exposing logged-in users' session tokens to interception and reuse. The flaw sits in the app's SharedPreferenceCookieManager, which matched cookie domains with a loose suffix check (domain.endsWith(domainSpec)) and did not require both the request domain and the cookie's stored domain to be genuine Wikimedia authorities, so a lookalike host such as a domain ending in wikipedia.org could match an approved suffix. Exploitation is not zero-click: it requires the target to be authenticated (holding CentralAuth cookies) and to be induced into making the app request the attacker's domain, which is why the vendor scores it 5.3 (medium) and our independent assessment lands at CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N; no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and the underlying logic is fixed by upstream pull request 6768.

RemediationAI

The upstream fix is available (PR/commit); a released patched version is not independently confirmed from the provided data - pull request 6768 (https://github.com/wikimedia/apps-android-wikipedia/pull/6768, tracked as https://phabricator.wikimedia.org/T433832) changes SharedPreferenceCookieManager.kt so cookie domains are matched exactly or as a dot-delimited subdomain (domain == domainSpec || domain.endsWith(".$domainSpec")) and so cross-authority CentralAuth transfer only occurs when the request domain itself passes Service.isWikimediaAuthority(). Until a patched build is available on the channel in use, apply compensating controls with explicit trade-offs: instruct users to avoid following untrusted or shortened links that might open URLs inside the app, since the attack requires the app to issue a request to the attacker's domain (this reduces but does not eliminate exposure, and it depends entirely on user behaviour); clear the app's stored cookies through Android's app-data settings or log out of the app to invalidate the CentralAuth values that would be leaked (this forces re-authentication on all Wikimedia properties and loses local session state); and where an organization manages the app via MDM, restrict or block usage until the fixed build is distributed. Server-side revocation of exposed CentralAuth sessions is the only reliable follow-up once a leak is suspected, because a captured token remains usable until invalidated.

Affected VersionsENISA

Wikipedia Android App main

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is org.wikipedia.dataclient.SharedPreferenceCookieManager, a Kotlin class in the Wikipedia Android app that persists OkHttp Cookie objects in Android SharedPreferences and later decides, via loadForRequest, which stored cookies to attach to an outgoing API request for a given URL authority. Because the app is used across many Wikimedia properties (wikipedia.org, wikimedia.org, wikidata.org, language subdomains and their .m. mobile variants), it deliberately transfers CentralAuth cookies - the CentralAuth_Token and CentralAuth_User values used by Wikimedia's single-sign-on - between approved authorities. The pre-fix matching logic used a bare suffix test, domain.endsWith(domainSpec), so any host whose name merely ended with an approved authority string (for example wikipedia.org.example.com) satisfied the check; the second branch also allowed transfer whenever the cookie's stored domain was a Wikimedia authority without verifying that the request domain was as well. The upstream fix in PR 6768 tightens this to exact equality or a dot-delimited subdomain match (domain == domainSpec || domain.endsWith(".$domainSpec")) and additionally requires Service.isWikimediaAuthority(domain) on the request side before any cross-authority CentralAuth transfer occurs. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) is the correct root-cause class: no memory-safety or injection primitive is involved, only an over-permissive string comparison that leaks credentials to a party that is not an authorized recipient.

Know when Wikipedia Android App gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (wikimedia-foundation) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Network-reachable, low complexity, no privileges, but requires user interaction to reach an attacker domain (UI:R); only limited cookie confidentiality exposure, no integrity/availability impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (wikimedia-foundation).

CVSS VectorVendor: wikimedia-foundation

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Wikimedia Foundation Wikipedia Android App allows Accessing/Intercepting/Modifying HTTP Cookies.

This issue affects Wikipedia Android App: main.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
High
Official Wikipedia Android app, hundreds of millions of installs across devices
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy