Exploitation timeline
Threadlinqs has recorded 6 The Wikimedia Foundation CVEs published between and . The busiest month was 2026-09 (6 new CVEs). None of them is listed in CISA KEV yet.
Most exploited vulnerabilities
Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 6 of 6 tracked The Wikimedia Foundation CVEs.
- CVE-2026-103045medium 6.1
- CVE-2026-103046medium 6.1
- CVE-2026-103047medium 6.1
- CVE-2026-103585low 1.2
- CVE-2026-103584low 1.1
- CVE-2026-103044
Products affected
Threadlinqs normalises CPE and CNA product records across all 6 CVEs; 6 distinct The Wikimedia Foundation products are affected. The most frequently affected:
- MediaWiki CommonsMetadata extension 1 CVE
- MediaWiki MediaSearch extension 1 CVE
- Mediawiki - CentralAuth extension 1 CVE
- Mediawiki - EasyTimeline extension 1 CVE
- Mediawiki - Refreshed skin 1 CVE
- Mediawiki - WikiLambda Extension 1 CVE
Threat activity
No tracked threat campaign references The Wikimedia Foundation products or CVEs yet. Vulnerability records are still monitored for exploitation and linked as campaigns are ingested.
How to prioritise The Wikimedia Foundation patching
This order follows the data Threadlinqs holds for The Wikimedia Foundation, not a generic severity checklist:
- No The Wikimedia Foundation CVE is in CISA KEV yet, so rank by exploit probability instead.
- 2 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.
About this data
Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-10-05 and refresh daily.