VDB

CVE-2025-13640

CVE-2025-13640 PUBLISHED CVSS 3.5 LOW

Reported by chrome · Published December 2, 2025

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)

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
chromiumWolfi143.0.7499.109-r0
chromiumChainguard143.0.7499.109-r0
chromegoogle143.0.7499.41, 143.0.7499.40

Risk scores

CVSS 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

VendorProductVersions
GoogleChrome143.0.7499.41
GoogleChrome143.0.7499.41

Timeline

  • Dec 2, 2025 CVE Published
  • Dec 2, 2025 PoC Published (3 in total, the first dated here)
  • Dec 3, 2025 EPSS Score (30 in total, the first dated here)
  • Jun 2, 2026 Security Advisory (17 in total, the first dated here)
  • Jun 23, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-13640
vulnetix vdb fixes CVE-2025-13640

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-13640/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›