CVE-2026-70096: Windows Rich Text Edit Control Remote Code Execution Vulnerability

Published Oct 13, 2026
·
Updated

Heap-based buffer overflow in Windows Rich Text Edit Control allows an unauthorized attacker to execute code over a network.

Other sources

Windows Rich Text Edit Control Remote Code Execution Vulnerability

— Microsoft

Affected Software

40 affected componentsFixes available
Microsoft Windows Server 2025<10.0.26100.33650
10.0.26100.33650
Microsoft Windows Server 2016<10.0.14393.9612
10.0.14393.9612
Microsoft Windows Server 2016<10.0.14393.9612
10.0.14393.9612
Microsoft Windows Server 2012 R2<6.3.9600.23470
6.3.9600.23470
Microsoft Windows Server 2012<6.2.9200.26434
6.2.9200.26434
Microsoft Windows Server 2012<6.2.9200.26434
6.2.9200.26434
Microsoft Windows Server 2025<10.0.26100.33650
10.0.26100.33650
Microsoft Windows Server 2012 R2<6.3.9600.23470
6.3.9600.23470
Microsoft Windows Server 2019<10.0.17763.9376
10.0.17763.9376
Microsoft Windows Server 2022<10.0.20348.5761
10.0.20348.5761
Microsoft Windows Server 2022<10.0.20348.5761
10.0.20348.5761
Microsoft Windows Server 2019<10.0.17763.9376
10.0.17763.9376
Microsoft Rich Text Edit Control
Microsoft Office 365 for Mac<16.114.26101123
16.114.26101123
Microsoft Office LTSC for Mac 2024<16.114.26101123
16.114.26101123
Microsoft Office LTSC for Mac 2021<16.114.26101123
16.114.26101123
Microsoft Windows 11=23H2, >=10.0.22631<10.0.22631.7652
10.0.22631.7652
Microsoft Windows 11=25H2, >=10.0.26200<10.0.26200.9711
10.0.26200.9711
Microsoft Windows 10=21H2, >=10.0.19044<10.0.19044.7807
10.0.19044.7807
Microsoft Windows 10=1607, >=10.0.14393<10.0.14393.9612
10.0.14393.9612
Microsoft Windows 11=26H1, >=10.0.28000<10.0.28000.3231
10.0.28000.3231
Microsoft Windows 11=24H2, >=10.0.26100<10.0.26100.9711
10.0.26100.9711
Microsoft Windows 11=26H1, >=10.0.28000<10.0.28000.3231
10.0.28000.3231
Microsoft Windows 11=24H2, >=10.0.26100<10.0.26100.9711
10.0.26100.9711
Microsoft Windows 10=1607, >=10.0.14393<10.0.14393.9612
10.0.14393.9612
Microsoft Windows 11=23H2, >=10.0.22631<10.0.22631.7652
10.0.22631.7652
Microsoft Windows 11=25H2, >=10.0.26200<10.0.26200.9711
10.0.26200.9711
Microsoft Windows 10=22H2, >=10.0.19045<10.0.19045.7807
10.0.19045.7807
Microsoft Windows 10=22H2, >=10.0.19045<10.0.19045.7807
10.0.19045.7807
Microsoft Windows 10=21H2, >=10.0.19044<10.0.19044.7807
10.0.19044.7807
Microsoft Windows 10=21H2, >=10.0.19044<10.0.19044.7807
10.0.19044.7807
Microsoft Windows 10=22H2, >=10.0.19045<10.0.19045.7807
10.0.19045.7807
Microsoft Windows 10=1809, >=10.0.17763<10.0.17763.9376
10.0.17763.9376
Microsoft Office LTSC 2021<16.0.14334.20974
16.0.14334.20974
Microsoft Office LTSC 2024<16.0.17932.21056
16.0.17932.21056
Microsoft Windows 10=1809, >=10.0.17763<10.0.17763.9376
10.0.17763.9376
Microsoft Windows 11=26H2, >=10.0.26300<10.0.26300.9711
10.0.26300.9711
Microsoft Office LTSC 2024<16.0.17932.21056
16.0.17932.21056
Microsoft Office LTSC 2021<16.0.14334.20974
16.0.14334.20974
Microsoft Windows 11=26H2, >=10.0.26300<10.0.26300.9711
10.0.26300.9711

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.33650Patch KB5126646
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.9612Patch KB5126868
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.23470Patch KB5126836
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.26434Patch KB5126835
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.9376Patch KB5126651
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.5761Patch KB5126655
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.114.26101123
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.7652Patch KB5126653
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26200.9711Patch KB5127648
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.7807Patch KB5126657
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.28000.3231Patch KB5127646
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.9711Patch KB5127648
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.7807Patch KB5126657
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.0.14334.20974
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.0.17932.21056
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26300.9711Patch KB5127648

Event History

Oct 13, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·06:59 PM
Data Sourced
via MITRE·06:59 PM
DescriptionSeverity
Data Sourced
via NVD·07:19 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which systems are in scope?

The affected software list includes Microsoft Windows 10, Windows 11, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2025.

2

Does exploitation require an authenticated account or user interaction?

No. The supplied severity vector indicates network attack access, low attack complexity, no privileges required, and no user interaction required.

3

What could a successful exploit allow?

A successful heap-based buffer overflow exploit could allow an unauthorized attacker to execute code. The severity vector indicates high potential impact to confidentiality, integrity, and availability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203