CVE-2026-96872 is an improper access-control vulnerability in the Wikimedia Foundation MediaWiki WikiLambda extension before version 1.47.0 on Linux, macOS, and Windows. The extension improperly handles insufficient permissions or privileges, allowing functionality to be accessed without being properly constrained by applicable access-control lists.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This two-file repository contains a Python proof of concept and supporting README for CVE-2026-96872, an authorization bypass in the MediaWiki WikiLambda extension before 1.47.0. The PoC first queries the supplied MediaWiki api.php endpoint to verify that WikiLambda is enabled. It then starts a local threaded HTTP capture service bound to 127.0.0.1 on port 4020 by default, submits a rejected control wikifunctions_run request, and submits a second crafted Z825 request containing nested ZObject function data and unsaved Python source. On a vulnerable target configured to use the local capture server as its orchestrator, the nested request is forwarded despite the unsaved-code restriction. The script verifies forwarding and the random harmless source marker. The repository is a controlled validation PoC, not a host-RCE exploit: it neither executes system commands nor establishes that the evaluator's WASM isolation can be escaped.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.