CVE-2026-13826: Inappropriate implementation in Autofill

Published May 14, 2026
·
Updated

Chromium: CVE-2026-13826 Inappropriate implementation in Autofill

Other sources

Inappropriate implementation in Autofill in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

— 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

6 affected componentsFixes available
Google Chrome (Android)<150.0.7871.47
Google Chrome<150.0.7871.46
150.0.7871.46
All of the following
Google Chrome<150.0.7871.47
Google Android
Microsoft Edge (Chromium-based)<150.0.4078.48
150.0.4078.48
Microsoft Edge<150.0.4078.48

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

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

    Fixed in 150.0.4078.48
  3. Upgrade

    Upgrade Chromium-based browsers (Google Chrome on Android; Edge via Chromium) to a version that resolves this vulnerability.

    Fixed in 150.0.7871.47

Event History

May 14, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
Jun 30, 2026
CVE Published
via MITRE·10:37 PM
Data Sourced
via MITRE·10:37 PM
DescriptionWeakness
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeaknessAffected Software
Jul 11, 2026
Data Sourced
via Microsoft·10:40 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·10:40 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-13826?

CVE-2026-13826 has a medium severity score of 6.5 according to the CVSS 3.1 framework.

2

How do I fix CVE-2026-13826?

To fix CVE-2026-13826, update Google Chrome on Android to version 150.0.7871.47 or later.

3

What types of data can be leaked due to CVE-2026-13826?

CVE-2026-13826 may allow remote attackers to leak cross-origin data through a crafted HTML page.

4

What versions of Google Chrome are affected by CVE-2026-13826?

CVE-2026-13826 affects Google Chrome on Android versions prior to 150.0.7871.47.

5

What should I do if I suspect an attack exploiting CVE-2026-13826?

If you suspect an exploit of CVE-2026-13826, immediately update your Google Chrome to the latest version and monitor for suspicious activity.

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