Skip to content
Fencer Intel
low 3.5

CVE-2025-13640 json

Inappropriate implementation in Passwords in Google Chrome prior to 143.0.7499.41 allowed a local attacker to bypass authentication via phy…

published 11mo ago modified 4mo ago also EUVD-2025-200297

cvss
3.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

Inappropriate implementation in Passwords in Google Chrome prior to 143.0.7499.41 allowed a local attacker to bypass authentication via physical access to the device. (Chromium security severity: Low)

Patch / fix

  • google chrome 143.0.7499.40, 143.0.7499.41
  • chromium Debian 12 143.0.7499.40-1~deb12u1
  • chromium Debian 13 143.0.7499.40-1~deb13u1
  • chromium Debian 14 143.0.7499.40-1

debian advisories DEBIAN-CVE-2025-13640

  • chromium openSUSE Leap 16.0 143.0.7499.192-bp160.1.1
  • chromium openSUSE Tumbleweed 143.0.7499.40-2.1

opensuse advisories openSUSE-SU-2026:20020-1openSUSE-SU-2025:15794-1

Is CVE-2025-13640 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 Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-13640 updated cvss 4.3

chromium-browser: Inappropriate implementation in Passwords

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
11mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 3.5 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA 3.1 3.5 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected products

  • Google Chrome

Classification

Technology feeds

References

Sources

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.