Google announced a Chrome 155 desktop update on October 13, 2026, addressing 37 security issues. Google listed versions 155.0.8059.79/.80 for Windows and macOS and 155.0.8059.79 for Linux, with distribution planned over the following days or weeks.
NewsEditorialSource: Chrome Releases
Google patches 37 Chrome 155 security flaws
Why it matters
Teams should prioritize updating developer workstations and browser testing environments, then check the running browser version after restarting. They should also check browser executables used by continuous integration, containers and cached test installations; a workstation update does not establish their patch status. The research relied on indexed excerpts because full-page retrieval failed, and those excerpts do not establish whether any of the flaws have been exploited.
Attribution
Sources
- 1Chrome ReleasesStable Channel Update for DesktopSource published (UTC)
- 2SecurityWeekChrome, Firefox Updates Patch 114 Flaws as Mozilla Unveils Firefox Enterprise
- 3Impress Watch「Google Chrome 155」にセキュリティ更新、「Critical」7件を含む37件の脆弱性を修正
Read the original source for full details and context.
EditorialSource: KrakenD
KrakenD releases Enterprise 2.13.11 security backport and Community and Enterprise 3.0.1
KrakenD released Enterprise Edition 2.13.11 as a recommended security backport on October 13, 2026, according to its changelog. [1] The changelog also lists Community and Enterprise Edition 3.0.1 releases that day. [1] It says the backport upgrades Go to 1.26.9 and updates amqp and OpenTelemetry dependencies for listed security issues. [1] According to Red Hat, CVE-2026-97032 lets an unauthenticated remote attacker crash Go’s HTTP/2 server if they win an HPACK encoder race. [2] KrakenD says affected versions are exposed when the gateway accepts HTTP/2 through Transport Layer Security negotiation or use_h2c. [3]
EditorialSource: Adobe
Adobe fixes critical vulnerabilities in Experience Manager
Adobe released fixes for critical and medium-severity vulnerabilities in Adobe Experience Manager (AEM) on October 13, 2026. [1] Adobe’s advisory lists arbitrary code execution, security-feature bypass and privilege escalation as possible impacts and assigns deployment priority 2. [1] Zero Day Initiative reported 33 distinct CVEs, explaining that Adobe’s table has 34 entries because CVE-2026-106631 appears twice. [2] According to Adobe, three incorrect-authorization flaws score 10.0 on the Common Vulnerability Scoring System and allow code execution over a network without privileges or user interaction. [1] Adobe reported no known exploitation at publication. [1]
EditorialSource: Microsoft
Microsoft releases October security updates for .NET and .NET Framework
Microsoft’s October servicing announcement lists .NET updates dated October 13, 2026, alongside new .NET Framework security and non-security updates. [1] The .NET releases—10.0.13, 9.0.21 and 8.0.32—include security and non-security fixes. Microsoft’s announcement links to release notes, installers, binaries and container images. [1] Microsoft’s .NET 10 release notes list fixes for information disclosure and denial of service. [3] BleepingComputer reported that the updates also address CVE-2026-108398, a .NET Framework security-feature bypass publicly disclosed before patching. [2]