- Products & ServicesProducts & Services
- SolutionsSolutions
- PricingPricing
- CompanyCompany
- ResourcesResources
en
en
Severity across 927 analyzed records
As of 09/12/2026, within CyStack's analyzed data, Chrome has 812 security vulnerabilities published in the last 90 days. Of these, 321 are rated High or Critical. Notably, 2 of these vulnerabilities are listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Chrome and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-87593 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87430 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87544 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87601 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87602 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87437 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87608 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87551 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87477 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87571 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87575 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87489 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87469 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87631 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87461 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87473 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87509 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87583 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87490 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87605 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87624 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87597 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87565 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87523 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87617 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87545 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87538 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87546 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87463 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87459 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87448 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87502 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87620 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87592 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87595 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87627 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87511 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87656 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityUnknown |
CVE-2026-87568 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87522 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87543 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87519 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87598 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87561 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87619 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87614 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-87618 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87429 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87634 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87653 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87629 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87626 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87610 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87609 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87526 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87591 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87455 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87638 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87566 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87623 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87528 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87632 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87584 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87586 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87470 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87529 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87637 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87531 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-87435 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87510 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87563 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87468 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87625 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87493 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87431 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87641 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87635 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87533 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87644 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87535 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87616 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87454 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87483 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87494 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-87550 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87530 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87484 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87589 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87518 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87594 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87540 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87622 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87505 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87450 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87439 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87532 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87600 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87555 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-87570 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-87451 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan