Google fixes 353 security flaws in Chrome 156, six of them critical
Google has released Chrome 156 with 353 security fixes, six of them critical, that could allow code execution through a crafted web page. Chrome on Windows, Mac and Linux before version 156.0.8078.47 is affected, and NVD also lists Android- and iOS-specific components.
What happened
According to Google's advisory, Chrome 156 was promoted to the stable channel for Windows, Mac and Linux on Tuesday, 20 October 2026, with 353 security fixes. The fixed versions are 156.0.8078.47 on Linux and 156.0.8078.47/.48 on Windows and Mac. The release will roll out gradually over the coming days or weeks, and Google will keep technical details restricted until most users have updated.
Most of the flaws involve memory corruption, use-after-free bugs and improper input validation. According to the NVD entries, a remote attacker could execute arbitrary code inside the browser sandbox if a victim opens a crafted HTML page.
The most serious flaws
Google rates six vulnerabilities as critical. They were found by Google itself, by Anthropic researchers assisted by the company's Claude model, and by OpenAI's Codex Security tool:
Among the issues Google rates as high severity are three in V8, the JavaScript engine (CVE-2026-113044, CVE-2026-113193 and CVE-2026-113222), numerous flaws in the ANGLE graphics layer, and CVE-2026-113101 in SiteIsolation, which earned a USD 10,000 bounty. NVD scores every published entry at CVSS 8.8, but Google rates several of them as low severity, such as CVE-2026-112994 and CVE-2026-113156. Where the two disagree, the vendor's assessment takes precedence.
- CVE-2026-113341: memory corruption in Skia (graphics engine)
- CVE-2026-113279: memory corruption in Accessibility
- CVE-2026-113271: use-after-free in Accessibility
- CVE-2026-113072: memory corruption in CSS
- CVE-2026-113280: memory corruption in Paint
- CVE-2026-113303: memory corruption in WebRTC
Who is affected and exploitation status
All Google Chrome installations older than version 156.0.8078.47 are affected. Several NVD entries refer to components specific to Android (Omnibox, CustomTabs, Toolbar) and iOS (iOSWeb). Google's advisory covers desktop only and does not list fixed mobile versions.
None of these vulnerabilities is in CISA's KEV catalogue, and Google's advisory does not mention active exploitation. Even so, the number and severity of the flaws, combined with an easy attack vector (simply visiting a website), make prompt updating advisable.
What to do
We recommend updating Chrome on every device across the organisation without waiting for the automatic rollout.
- Update desktop Chrome to 156.0.8078.47 (Linux) or 156.0.8078.47/.48 (Windows and Mac), then restart the browser, which is required for the fix to take effect.
- In managed environments, use Chrome enterprise policies to force the update and relaunch.
- Check the installed version under Settings > About Chrome.
- Update Chrome on Android and iOS through the official app stores as soon as version 156 is available.
- If you use other Chromium-based browsers, follow their vendors' advisories.
Fixed identifiers
Besides the six critical flaws, Chrome 156 fixes the vulnerabilities with the following identifiers:
- CVE-2026-112992, CVE-2026-112993, CVE-2026-112994, CVE-2026-112995, CVE-2026-112996, CVE-2026-112997, CVE-2026-112998, CVE-2026-112999, CVE-2026-113000, CVE-2026-113001, CVE-2026-113003, CVE-2026-113004, CVE-2026-113005, CVE-2026-113006, CVE-2026-113007, CVE-2026-113008, CVE-2026-113009, CVE-2026-113011, CVE-2026-113012, CVE-2026-113013, CVE-2026-113014, CVE-2026-113015, CVE-2026-113016, CVE-2026-113017, CVE-2026-113018, CVE-2026-113019, CVE-2026-113020, CVE-2026-113021, CVE-2026-113022, CVE-2026-113023, CVE-2026-113024, CVE-2026-113025, CVE-2026-113027, CVE-2026-113028, CVE-2026-113029, CVE-2026-113031, CVE-2026-113032, CVE-2026-113033, CVE-2026-113034, CVE-2026-113036, CVE-2026-113037, CVE-2026-113039, CVE-2026-113040, CVE-2026-113041, CVE-2026-113042, CVE-2026-113043, CVE-2026-113044, CVE-2026-113046, CVE-2026-113048
- CVE-2026-113049, CVE-2026-113052, CVE-2026-113053, CVE-2026-113055, CVE-2026-113056, CVE-2026-113058, CVE-2026-113059, CVE-2026-113060, CVE-2026-113061, CVE-2026-113062, CVE-2026-113063, CVE-2026-113064, CVE-2026-113065, CVE-2026-113067, CVE-2026-113068, CVE-2026-113069, CVE-2026-113071, CVE-2026-113073, CVE-2026-113074, CVE-2026-113075, CVE-2026-113076, CVE-2026-113078, CVE-2026-113079, CVE-2026-113080, CVE-2026-113081, CVE-2026-113082, CVE-2026-113083, CVE-2026-113084, CVE-2026-113085, CVE-2026-113086, CVE-2026-113087, CVE-2026-113088, CVE-2026-113089, CVE-2026-113090, CVE-2026-113091, CVE-2026-113092, CVE-2026-113093, CVE-2026-113094, CVE-2026-113095, CVE-2026-113096, CVE-2026-113097, CVE-2026-113098, CVE-2026-113099, CVE-2026-113100
- CVE-2026-113101, CVE-2026-113103, CVE-2026-113104, CVE-2026-113105, CVE-2026-113106, CVE-2026-113107, CVE-2026-113108, CVE-2026-113109, CVE-2026-113110, CVE-2026-113111, CVE-2026-113112, CVE-2026-113113, CVE-2026-113114, CVE-2026-113115, CVE-2026-113116, CVE-2026-113117, CVE-2026-113118, CVE-2026-113119, CVE-2026-113120, CVE-2026-113121, CVE-2026-113123, CVE-2026-113124, CVE-2026-113125, CVE-2026-113126, CVE-2026-113127, CVE-2026-113130, CVE-2026-113131, CVE-2026-113132, CVE-2026-113133, CVE-2026-113134, CVE-2026-113135, CVE-2026-113136, CVE-2026-113138, CVE-2026-113140, CVE-2026-113141, CVE-2026-113145, CVE-2026-113146, CVE-2026-113147, CVE-2026-113148, CVE-2026-113149, CVE-2026-113150, CVE-2026-113152, CVE-2026-113153, CVE-2026-113154, CVE-2026-113155, CVE-2026-113156
- CVE-2026-113158, CVE-2026-113160, CVE-2026-113161, CVE-2026-113162, CVE-2026-113163, CVE-2026-113164, CVE-2026-113165, CVE-2026-113166, CVE-2026-113167, CVE-2026-113168, CVE-2026-113169, CVE-2026-113170, CVE-2026-113171, CVE-2026-113172, CVE-2026-113173, CVE-2026-113174, CVE-2026-113175, CVE-2026-113176, CVE-2026-113177, CVE-2026-113179, CVE-2026-113180, CVE-2026-113181, CVE-2026-113182, CVE-2026-113183, CVE-2026-113184, CVE-2026-113185, CVE-2026-113186, CVE-2026-113187, CVE-2026-113188, CVE-2026-113189, CVE-2026-113190, CVE-2026-113191, CVE-2026-113192, CVE-2026-113193, CVE-2026-113194, CVE-2026-113195, CVE-2026-113197, CVE-2026-113198, CVE-2026-113200, CVE-2026-113202, CVE-2026-113203, CVE-2026-113204, CVE-2026-113205, CVE-2026-113206, CVE-2026-113207, CVE-2026-113208, CVE-2026-113210
- CVE-2026-113211, CVE-2026-113213, CVE-2026-113214, CVE-2026-113215, CVE-2026-113216, CVE-2026-113217, CVE-2026-113218, CVE-2026-113219, CVE-2026-113220, CVE-2026-113221, CVE-2026-113222, CVE-2026-113225, CVE-2026-113226, CVE-2026-113227, CVE-2026-113234, CVE-2026-113235, CVE-2026-113236, CVE-2026-113241, CVE-2026-113242, CVE-2026-113244, CVE-2026-113245, CVE-2026-113247, CVE-2026-113248, CVE-2026-113252, CVE-2026-113253, CVE-2026-113254, CVE-2026-113260, CVE-2026-113261, CVE-2026-113263, CVE-2026-113266, CVE-2026-113268, CVE-2026-113269, CVE-2026-113270, CVE-2026-113273, CVE-2026-113274, CVE-2026-113283, CVE-2026-113284, CVE-2026-113285, CVE-2026-113286, CVE-2026-113287, CVE-2026-113288, CVE-2026-113291, CVE-2026-113292, CVE-2026-113293, CVE-2026-113294, CVE-2026-113298, CVE-2026-113299, CVE-2026-113300, CVE-2026-113305, CVE-2026-113306, CVE-2026-113313, CVE-2026-113314, CVE-2026-113315, CVE-2026-113316, CVE-2026-113317, CVE-2026-113322, CVE-2026-113324, CVE-2026-113328, CVE-2026-113330, CVE-2026-113331, CVE-2026-113334, CVE-2026-113336, CVE-2026-113339, CVE-2026-113342
Sources
Affected technologies
Google ChromeGoogle Chrome for AndroidGoogle Chrome for iOS
Vulnerabilities (297)
| CVE | Severity | Active exploitation | Published | NVD status |
|---|---|---|---|---|
| CVE-2026-112994 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-112996 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-112998 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113013 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113017 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113021 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113024 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113025 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113029 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113036 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113039 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113046 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113048 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113061 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113063 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113067 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113074 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113080 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113083 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113085 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113088 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113107 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113121 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113125 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113130 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113132 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113140 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113145 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113152 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113156 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113167 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113173 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113180 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113182 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113184 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113226 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113227 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113241 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113244 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113245 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113247 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113248 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113254 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113260 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113268 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113269 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113274 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113286 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113287 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113288 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113291 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113292 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113294 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113299 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113306 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113313 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113314 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113330 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113331 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-112993 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-112995 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-112997 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-112999 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113000 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113001 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113003 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113004 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113005 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113006 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113008 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113009 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113011 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113012 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113015 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113016 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113018 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113019 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113022 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113027 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113028 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113031 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113032 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113033 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113034 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113037 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113040 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113041 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113042 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113043 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113044 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113049 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113052 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113053 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113055 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113058 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113059 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113060 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113062 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113064 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113065 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113068 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113069 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113071 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113073 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113075 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113076 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113079 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113081 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113086 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113087 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113090 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113091 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113092 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113093 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113094 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113095 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113096 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113097 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113099 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113100 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113101 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113103 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113104 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113105 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113106 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113108 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113109 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113110 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113111 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113112 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113113 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113114 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113115 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113117 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113118 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113119 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113120 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113123 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113124 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113127 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113131 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113133 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113134 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113135 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113136 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113141 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113146 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113147 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113148 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113149 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113150 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113153 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113154 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113155 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113158 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113160 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113161 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113162 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113163 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113164 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113165 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113166 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113168 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113170 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113172 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113174 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113175 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113176 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113177 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113179 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113181 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113183 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113185 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113187 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113188 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113190 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113191 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113192 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113194 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113195 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113197 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113198 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113200 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113202 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113203 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113204 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113205 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113206 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113207 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113208 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113210 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113213 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113214 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113215 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113216 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113217 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113218 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113219 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113220 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113221 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113228 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113229 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113230 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113231 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113232 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113233 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113234 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113236 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113238 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113239 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113240 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113242 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113243 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113249 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113250 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113251 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113253 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113255 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113256 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113257 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113258 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113259 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113262 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113265 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113266 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113267 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113271 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113272 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113273 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113275 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113276 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113278 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113279 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113280 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113281 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113282 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113284 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113285 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113289 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113290 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113293 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113298 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113301 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113302 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113303 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113305 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113307 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113308 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113311 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113312 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113315 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113316 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113317 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113318 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113319 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113320 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113321 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113323 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113324 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113327 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113332 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113334 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113335 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113337 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113338 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113339 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113343 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-113344 | High (8.8) | — | 10/20/2026 | Received |
| CVE-2026-112992 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113007 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113014 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113020 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113023 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113056 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113072 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113078 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113084 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113089 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113116 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113126 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113138 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113169 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113171 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113186 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113189 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113211 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113222 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113235 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113252 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113261 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113263 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113270 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113283 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113300 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113328 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113336 | Critical (9.6) | — | 10/20/2026 | Received |
| CVE-2026-113342 | Critical (9.6) | — | 10/20/2026 | Received |
Written automatically from NVD, CISA KEV and vendor advisory data. Always check affected versions and patches in the vendor's official advisory before acting.