CVE-2026-95369: Inappropriate implementation in XML

Published May 14, 2026
·
Updated

Chromium CVE-2026-95369: Inappropriate implementation in XML

Other sources

Inappropriate implementation in XML in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

— MITRE

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

— Microsoft

Credit

Google

Affected Software

3 affected componentsFixes available
Google Chrome<154.0.8037.57
154.0.8037.57
Google Chrome<154.0.8037.57
Microsoft Edge (Chromium-based)<154.0.4258.37
154.0.4258.37

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 154.0.8037.57
  2. Upgrade

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

    Fixed in 154.0.4258.37
  3. Upgrade

    Upgrade Google Chrome to a version that resolves this vulnerability.

    Fixed in 154.0.8037.57
  4. Upgrade

    Upgrade Microsoft Edge (Chromium-based) to a version that resolves this vulnerability.

    Fixed in 154.0.8037.57

Event History

May 14, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
Sep 25, 2026
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Sep 29, 2026
CVE Published
via MITRE·05:31 PM
Data Sourced
via MITRE·05:31 PM
DescriptionWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

Which installations should be investigated?

The supplied data identifies Google Chrome as the affected software, but it does not provide affected or fixed version numbers.

2

Can exposure be determined from configuration or usage details?

No. The provided information does not state whether a default configuration is affected, which XML-processing features are involved, or what attacker interaction is required.

3

What mitigation is available if an update cannot be applied immediately?

No workaround, compensating control, or detection method is provided in the supplied data.

Company

Resources

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