CVE-2026-41102
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 · uneditedImproper access control in Microsoft Office PowerPoint allows an authorized attacker to perform spoofing locally.
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 confidenceThis is an improper access control vulnerability in Microsoft Office PowerPoint that allows an authorized attacker to perform local spoofing. The exact mechanism is not detailed, but access control flaws typically involve insufficient validation of user permissions or content origin, potentially allowing manipulation of presentation content or credentials within the PowerPoint application.
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< 16.0.19822.20190CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Check installed PowerPoint versionOpen PowerPoint, go to File > Account > About PowerPoint. Alternatively, open the app and go to File > Account > Product Information to view the version number.Affected if The displayed version is lower than 16.0.19822.20190 (e.g., 16.0.xxxx.xxxx where the build number is below 19822)
-
Verify Office update channelIn PowerPoint, go to File > Account > Update Options. Check if updates are set to automatic or manual.Affected if Updates are not configured or the channel is not receiving current patches, resulting in the vulnerable version remaining installed
-
Confirm PowerPoint is in useThis vulnerability affects local spoofing within the PowerPoint application. Determine if PowerPoint is deployed or used in your environment.Affected if PowerPoint is installed and in use, and the version check shows a version below 16.0.19822.20190
You are affected if your installed PowerPoint version is below 16.0.19822.20190 and the application is in use by authorized users who could trigger the local spoofing flaw.
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 · scoped16.0.19822.20190
Apply Microsoft security updates for Office PowerPoint once released; in the interim, enforce least-privilege access and restrict PowerPoint file handling to trusted, authorized users only.
Microsoft 365/Office 365 with updates applied to reach version 16.0.19822.20190 or later
- Open Microsoft PowerPoint
- Click on File > Account > Update Options
- Select 'Update Now' to check for and install the latest updates
- Alternatively, go to Microsoft Update or use Windows Update to ensure Office is updated to version 16.0.19822.20190 or later
- Verify the installed version by going to File > Account > About PowerPoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation5.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 $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41102 — 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-41102 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