CVE-2022-41104 json
Microsoft Excel Security Feature Bypass Vulnerability
published 4y ago modified 2mo ago also EUVD-2022-44347
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
Microsoft Excel Security Feature Bypass Vulnerability
Patch / fix
- Microsoft Microsoft Excel 2013 Service Pack 1 15.0.5501.1000
- Microsoft Microsoft Excel 2016 16.0.5369.1000
Is CVE-2022-41104 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
Affected products
- Microsoft Microsoft 365 Apps for Enterprise
- Microsoft Microsoft Excel 2013 Service Pack 1
- Microsoft Microsoft Excel 2016
- Microsoft Microsoft Office 2019
- Microsoft Microsoft Office LTSC 2021
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2022-41104
vendor-advisory, patch
Sources
- CVE List CVE-2022-41104
- NVD CVE-2022-41104
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.