CVE-2026-34088
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Wikimedia Foundation MediaWiki. This issue affects MediaWiki: from * before 1.43.7, 1.44.4, 1.45.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInformation disclosure vulnerability in MediaWiki allowing unauthorized actors to access sensitive data. Affects versions prior to 1.43.7, 1.44.4, and 1.45.2. Exploitable over network without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.43.7>= 1.44.0, < 1.44.4>= 1.45.0, < 1.45.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed MediaWiki versionAccess the Special:Version page on your wiki (go to /wiki/Special:Version) or check the includes/Defines.php file for the $wgVersion variableAffected if The version shown is less than 1.43.7, or between 1.44.0 and 1.44.4, or between 1.45.0 and 1.45.2
-
Confirm network exposureVerify that your MediaWiki installation is accessible over the network (not localhost-only or behind strict firewall)Affected if The wiki is reachable from untrusted networks without authentication
-
Check for sensitive data access attemptsReview web server access logs for unusual requests to API endpoints or special pages that may indicate information disclosure probingAffected if Log analysis shows unauthorized access attempts to sensitive data endpoints
You are affected if your MediaWiki version falls within the vulnerable ranges (< 1.43.7, 1.44.0-1.44.4, or 1.45.0-1.45.2) and the installation is network-accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.43.71.44.41.45.2
Update MediaWiki to version 1.43.7, 1.44.4, or 1.45.2 or later to patch the vulnerability.
Upgrade to MediaWiki 1.45.2 (or 1.44.4 for 1.44.x users, or 1.43.7 for 1.43.x users)
- Backup your MediaWiki database and files before proceeding
- Download MediaWiki 1.45.2 (or the appropriate version for your branch: 1.43.7 or 1.44.4) from the official MediaWiki releases page
- Extract the new version to a temporary location
- Replace the existing MediaWiki files with the new version, preserving your LocalSettings.php and any custom extensions
- Run the database update script: php maintenance/update.php
- Clear all MediaWiki caches (run php maintenance/resetUserTokens.php if applicable, clear opcache, CDN caches, and any local cache directories)
- Verify the installation by accessing your wiki and checking Special:Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34088 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34088 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data