7893 matches found
CVE-2026-14016
An insufficient policy enforcement flaw was found in the SVG component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=517234388...
CVE-2026-14041
An insufficient policy enforcement flaw was found in the Serial component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=497544822...
CVE-2026-14052
An insufficient policy enforcement flaw was found in the FileSystem component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=501810874...
CVE-2026-14054
An insufficient policy enforcement flaw was found in the Network component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=501851312...
CVE-2026-14073
An insufficient policy enforcement flaw was found in the WebXR component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=507237563...
CVE-2026-14053
An insufficient policy enforcement flaw was found in the Extensions component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=501836539...
CVE-2026-14050
An insufficient policy enforcement flaw was found in the Passwords component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=501708647...
CVE-2026-14092
An insufficient policy enforcement flaw was found in the Privacy component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=513212892...
CVE-2026-14109
An insufficient policy enforcement flaw was found in the Mojo component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=513694957...
CVE-2026-14057
An insufficient policy enforcement flaw was found in the FedCM component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=502212647...
CVE-2026-14081
An insufficient policy enforcement flaw was found in the DevTools component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=513030698...
CVE-2026-14105
An insufficient policy enforcement flaw was found in the Speech component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=513528117...
CVE-2026-14059
An insufficient policy enforcement flaw was found in the Related-Website-Sets component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=502363986...
CVE-2026-15130
An insufficient policy enforcement flaw was found in the Navigation component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=526541544...
CVE-2026-15775
An insufficient policy enforcement flaw was found in the V8 component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=531319201...
CVE-2026-15124
An insufficient policy enforcement flaw was found in the Passwords component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=523735038...
CVE-2026-15768
An insufficient policy enforcement flaw was found in the HTML-in-Canvas component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=517931625...
Closing the Sovereignty Gap: Bringing Active API Protection to Self-Managed Environments
How Thales is bringing active API protection to self-managed environments, without compromising digital sovereignty. APIs Changed Faster Than Security Architectures Organizations have invested heavily in discovering APIs, classifying sensitive data, and understanding API risk. That's progress. Bu...
PT-2026-65571
Name of the Vulnerable Software and Affected Versions CRIU affected versions not specified Description An issue exists in the handling of restartable sequences rseq during the checkpoint/restore process. A malicious process within a container can register an rseq critical section to hijack the...
CVE-2026-18029: Improper Enforcement of Behavioral Workflow
Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...