CVE-2022-29107 [Medium] | Security Bypass in 365 Apps

CVE-2022-29107 is rated Moderate Risk (48/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 2.63%). Review affected assets and schedule remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	5.85%	2.63%	-3.22%
2	2026-06-09	7.73%	5.85%	-1.89%
3	2026-04-08	—	7.73%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

5.85%

2.63%

-3.22%

2026-06-09

7.73%

5.85%

-1.89%

2026-04-08

—

7.73%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	1.8	3.6	[email protected]
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	1.8	3.6	[email protected]
4.3	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:P/I:N/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:N) No integrity impact. Availability impact (A:N) No availability impact.	8.6	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

1.8

3.6

[email protected]

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

1.8

3.6

[email protected]

4.3

2.0

MEDIUM

AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:N): No integrity impact.
Availability impact (A:N): No availability impact.

8.6

2.9

[email protected]

Affected software / configurations for CVE-2022-29107

Vendor	Product	Version	Raw CPE
microsoft	365_apps	—	cpe:2.3:a:microsoft:365_apps:-::::enterprise::x64:*
microsoft	365_apps	—	cpe:2.3:a:microsoft:365_apps:-::::enterprise::x86:*
microsoft	office	2019	cpe:2.3:a:microsoft:office:2019::::::x64:
microsoft	office	2019	cpe:2.3:a:microsoft:office:2019::::::x86:
microsoft	office_long_term_servicing_channel	2021	cpe:2.3:a:microsoft:office_long_term_servicing_channel:2021::::::x64:
microsoft	office_long_term_servicing_channel	2021	cpe:2.3:a:microsoft:office_long_term_servicing_channel:2021::::::x86:
microsoft	publisher	2016	cpe:2.3:a:microsoft:publisher:2016::::::x64:
microsoft	publisher	2016	cpe:2.3:a:microsoft:publisher:2016::::::x86:
microsoft	word	2013	cpe:2.3:a:microsoft:word:2013:sp1:::::x64:*
microsoft	word	2013	cpe:2.3:a:microsoft:word:2013:sp1:::::x86:*
microsoft	word	2013	cpe:2.3:a:microsoft:word:2013:sp1:::rt:::*
microsoft	word	2016	cpe:2.3:a:microsoft:word:2016::::::x64:
microsoft	word	2016	cpe:2.3:a:microsoft:word:2016::::::x86:

References for CVE-2022-29107

URL	Tags
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-29107
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-29107	Patch Vendor Advisory

URL

CVE-2022-29107 | Microsoft Office Security Feature Bypass Vulnerability

Exploit prediction scoring system (EPSS) score for CVE-2022-29107

Common vulnerability scoring system (CVSS) metrics for CVE-2022-29107

Weakness enumeration for CVE-2022-29107

Affected software / configurations for CVE-2022-29107

References for CVE-2022-29107