AMAZON WEB SERVICESAMAZON-WEB-SERVICES-B858CA8C95AC467E
Amazon Bedrock continues to expand its open weight model portfolio with the same security and governance that customers rely on. Today, Kimi K3 from Moonshot AI is generally available on Amazon Bedrock, giving you a powerful new option for coding and knowledge work. According to Moonshot AI, Kimi K3 is its most capable model and the first open model to reach 2.8 trillion parameters. It combines native vision capabilities with a 1-million-token context window, making it well suited to long-running coding sessions across large repositories, multi-document analysis including scanned pages and screenshots, and extended agent workflows. Moonshot AI reports an approximate 2.5x improvement in scaling efficiency over Kimi K2. On Amazon Bedrock, Kimi K3 runs within the same security boundary as proprietary models, and the same controls for access, encryption, and auditing across your model portfolio. Kimi K3 is the first open weight model on Amazon Bedrock to support explicit prompt caching , helping reduce latency and input costs when reusing context across model calls. Kimi K3 is available in all AWS Regions where Amazon Bedrock is available through cross-Region inferencing. To get started, visit the Amazon Bedrock Console . To learn more, see the Amazon Bedrock documentation and read the launch blog post.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →AMAZON WEB SERVICESAMAZON-WEB-SERVICES-DA2F01B80ABB0FDF
The next generation of AWS Resilience Hub is a central location in the AWS that helps platform engineering and site reliability teams assess and strengthen the resilience of their workloads running on AWS. It provides automated dependency discovery, generative AI-powered failure mode analysis, modular resilience policies, resilience testing, and organization-wide resilience posture reporting. Today, AWS Resilience Hub adds three new capabilities: EKS labels support for service input sources, dependency insights, and resilience policy sharing through AWS Organizations. EKS labels support for service input sources. Resilience Hub now supports EKS labels within a namespace as a service input source, allowing customers to use their existing Kubernetes labeling conventions to scope exactly which resources Resilience Hub discovers and uses during failure mode analysis. This ensures assessments stay aligned with how teams organize their EKS workloads. Dependency insights. Customers who enable dependency discovery can now generate dependency insights, a new generative AI-powered capability that analyzes discovered application dependencies and highlights meaningful patterns. Dependency insights surfaces new dependencies, identifies cross-Region dependencies, and flags unusual usage patterns. This helps teams accelerate dependency analysis and identify potential new risks. Resilience policy sharing through AWS Organizations. Resilience Hub now supports sharing resilience policies through AWS Organizations, enabling central teams to build and manage policies that can be applied across multiple accounts. This provides organization-wide observability into which services are using each policy, making it easier to monitor adoption and ensure consistent resilience posture across the organization. To get started, visit the AWS console . To learn more, see the product page or visit the documentation .
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →AMAZON WEB SERVICESAMAZON-WEB-SERVICES-E57311302437C582
AWS PrivateLink customers can now use VPC endpoint to privately and securely access network segments in another VPC/account. They can use a ‘tunnel’ endpoint, a new type of VPC endpoint, to tunnel into the network segment and access resources located within it. AWS PrivateLink is a highly available and scalable technology that enables private access across VPC and account boundaries to load balanced services, appliances, and resources such as databases and domains. Prior to this launch, customers who wanted to share their resources with another party such as an external vendor had to do it one at a time by creating a Resource Configuration for every resource. Now, customers can create a Resource Configuration to represent a CIDR range in their network, and share it with a vendor via AWS Resource Access Manager (RAM). The vendor can then create a tunnel endpoint and use GENEVE encapsulation to tunnel through it into the customer’s VPC to access resources located in CIDR range specified by the customer. There is an hourly charge for the tunnel endpoint and a per-GB charge for data processed through it. Please refer to the pricing page for AWS PrivateLink . The capability is available in the following AWS Regions : US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Canada West (Calgary), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Paris), Europe (Spain), Europe (Stockholm), Europe (Zurich), Mexico (Central), South America (São Paulo). To learn more about this capability and get started, please refer to the AWS PrivateLink documentation .
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →AMAZON WEB SERVICESAMAZON-WEB-SERVICES-F608A427B12B484E
Today, AWS announces the availability of the next generation of AgentCore Runtime , the serverless microVM compute within Amazon Bedrock AgentCore. The new Runtime delivers elastic memory management that reclaims unused memory throughout the session so you pay for actual usage rather than the peak, and consistent cold start times regardless of container image size or concurrency. You get the serverless model you already rely on: no pre-provisioning, scale to zero, hardware-enforced session isolation, and pay only for what you use - now with lower costs and faster starts. With the new Runtime, each session starts with a small, efficient memory profile. Additional memory is allocated on demand as the workload needs it, and memory that is no longer actively used is reclaimed rather than held until the session ends. For cold starts, the new Runtime prepares the agent environment once and snapshots it. Every new instance restores from that snapshot instead of repeating the full startup sequence, keeping start times consistent regardless of image size. In testing, the new Runtime delivered a P75 cold start of 1.9 to 2.0 seconds for container images from 200 MB to 2 GB, compared to 5.4–30 seconds with V1. The new AgentCore Runtime is available in the following regions: us-east-1, us-east-2, us-west-2, eu-west-1, and ap-northeast-1. To get started, set platformVersion to V2 when creating or updating a runtime. To learn more, visit the AgentCore Runtime documentation or the AWS News Blog . For pricing details, visit AgentCore pricing .
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →ANSIBLEANSIBLE-CORE-2.22.0
Changelog See the full changelog for the changes included in this release. Release Artifacts Built Distribution: ansible_core-2.22.0b1-py3-none-any.whl - 2477326 bytes 3e635a2a6489f104723c5c673c89fcf22742f057e6a4bb64e882497dcef3a25b (SHA256) Source Distribution: ansible_core-2.22.0b1.tar.gz - 3475528 bytes 6be052c36d0f6a9f176f00bc18bc770e1eddb037287e972af71fb5de23b9a72a (SHA256)
Published Never · Source checked 28 Sep 2026
Release notes and known issues →CLOUDFLARECLOUDFLARE-B529AF879ABE0466
Cloudflare's global network is immense but not limitless. As we look for small ways to trim our resource usage, we sometimes get lucky and we can cut significantly more. Here’s how we reduced one of our Pingora-based service's RAM usage with statistics.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-096CE8528CB75123
The Dev channel has been updated to 156.0.8063.3 for Windows, Mac and Linux. A partial list of changes is available in the Git log . Interested in switching release channels? Find out how . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Chrome Release Team Google Chrome
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-156.0.8063.0
Hi everyone! We've just released Chrome Dev 156 (156.0.8063.0) for Android. It's now available on Google Play . You can see a partial list of the changes in the Git log . For details on new features, check out the Chromium blog , and for details on web platform updates, check here . If you find a new issue, please let us know by filing a bug . Chrome Release Team Google Chrome
Published 18 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-156.0.8063.3
The Dev channel has been updated to 156.0.8063.3 for Windows, Mac and Linux. A partial list of changes is available in the Git log . Interested in switching release channels? Find out how . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Chrome Release Team Google Chrome
Published 18 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-8404D9BBD2C4C236
Hi everyone! We've just released Chrome Dev 156 (156.0.8063.0) for Android. It's now available on Google Play . You can see a partial list of the changes in the Git log . For details on new features, check out the Chromium blog , and for details on web platform updates, check here . If you find a new issue, please let us know by filing a bug . Chrome Release Team Google Chrome
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-WORKSPACE-7C4D978D0C52551B
Set up sharing boundaries for Google Drive with unified data protection rules We’re introducing a new capability that allows Google Workspace administrators to configure audience sharing and sensitivity-based data conditions in a single, unified rule. This unified rule flow helps organizations elevate their security posture to proactively mitigate insider risks, prevent data exfiltration, and safely unblock collaboration for high-sensitivity environments. | Learn more . Gmail Search’s AI Overviews now available globally Starting today, we are expanding access to AI Overviews in Gmail search to global users (with paid plans) who have their Gmail language set as English. Previously, this was only available to users in the US with their language set as English. | Learn more . Connect to more tools with Gemini in Google Workspace Users will now be able to use Gemini in Workspace to directly interact with Asana, Atlassian Rovo, HubSpot, Intuit Mailchimp, Intuit QuickBooks, Monday, and Salesforce through Model Context Protocol (MCP) integrations. This will enable them to access information directly without needing to switch tabs, download files, or interrupt workflows across our Google Workspace apps including Sheets, Gmail, Drive, Docs, Chat, and more. | Learn more . Connect to Google Meet hardware with room codes now generally available Google Meet users can now connect to nearby conference room hardware by entering a 5-character room code on their personal device. Building on the recent Connect Room launch that uses proximity-based detection to identify nearby hardware, this update provides a reliable manual fallback when ultrasound is unavailable or disabled. | Learn more . Data regions support for Google Apps Script now generally available Data regions are critical for helping organizations meet internal compliance, legal, regulatory, and data sovereignty obligations by controlling the geographic location of covered data at rest and through data processing. Expanding these controls to Apps Script allows organizations—including those in highly regulated industries and the public sector—to build, deploy, and automate enterprise workflows with confidence that their script data and executions remain within designated geographic boundaries. | Learn more . View conference room and meeting location details directly on the Google Meet homepage Starting today, we’re enhancing the Meet homepage experience by displaying conference room and physical meeting locations directly on upcoming meeting cards. For in-office users this update allows them to see where they need to go directly on their Meet landing page, streamlining their workflow before and between meetings. | Learn more . Introducing Expert Intelligence in Gemini Notebook We’re introducing Expert Intelligence, a cross Google initiative that helps users engage with trusted sources through Google AI products, starting with Gemini Notebook. Featuring more than 100,000 books from major publishers, employees and students can now incorporate insights from leading authors, publications, and domain experts directly into Gemini Notebook. | Learn more . Automate workflows with custom starters and steps, third-party integrations, and webhooks in Workspace Studio To expand the capabilities of Workspace Studio and help teams build powerful, custom automations, we are introducing four new features for flows in Workspace Studio: custom starters, custom steps, third-party (3P) integrations, and webhooks. These new capabilities empower users to seamlessly connect custom Google Apps Script functions, integrate third-party services, and trigger external webhooks directly within flows in Workspace Studio. | Learn more . Notebooks in Gemini: a dedicated workspace for focused, organized work, now for schools and organizations In April, we announced notebooks in Gemini as a dedicated, focused space for individual users to organize their projects and conversations. Now, students of all ages, educators, a
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-WORKSPACE-8F31B2615868AEC4
We’re introducing several updates to Gemini Notebook that give users a more personalized and powerful learning experience. Audio recorder: Users can now use a new audio recorder in the Gemini Notebook mobile app ( Android / iOS ) to capture lectures or record thoughts on the go, with these notes living directly alongside their sources for easy citation and ongoing edits. Real-time conversation with notebooks: Users 18 years or older can now have a real-time conversation with their notebooks using the Gemini Notebook mobile app ( Android / iOS ) in nearly 100 languages. Because every response is grounded in their sources, users can get step-by-step guidance, ask questions, and interrupt at any time just by speaking. Interactive learning overviews: To help users maintain focus during study sessions, we’re introducing interactive learning overviews under Reports, which weave together summaries and studio outputs like quizzes, flashcards, and mind maps. Improved exam prep tools: We’re expanding exam prep tools with the following updates: New quiz formats include short answer, multiple choice, and fill in the blank. Users can chat with their notebook about their performance on the most recently completed quiz and flashcard set to help determine where to focus their attention next. Quizzes and flashcards can be customized by adding or editing questions. Short Video Overviews for learning: Users can also create engaging Short Video Overviews in more than 80 languages and even share them with classmates or other people. These bite-sized ~60-second videos combine narrative overviews with educational animations to help make complex formulas, diagrams, and scientific concepts easier to digest. Getting started Admins: These features will be available to users who are in a group or organizational unit with Gemini Notebook set to On. Visit the Help Center to learn more about turning Gemini Notebook on or off for users . End users: There are no end user settings for these features. Visit the Help Center to learn more about Gemini Notebook . Rollout pace Rapid Release and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) started on September 15, 2026 Availability Available to all Google Workspace customers, Workspace Individual subscribers, and users with personal Google accounts Resources News from Google: Sharpen your study routine with new Gemini Notebook tools Google Workspace Admin Help: Turn Gemini Notebook on or off for users Gemini Notebook Help: Generate reports in Gemini Notebook
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →OPEN HOME FOUNDATIONHOME-ASSISTANT-2026.9.3
Fix EnergyZero market price regression ( @klaasnicolaas - #181230 ) ( energyzero docs ) Require the IRK in the Private BLE Device config flow ( @frenck - #181969 ) ( private_ble_device docs ) Keep the known Bond host when zeroconf still announces it ( @frenck - #181975 ) ( bond docs ) Fix function name in external statistics mean_type message ( @Booyaka101 - #182031 ) ( recorder docs ) Fix Matter cover entity not created when tilt attribute is null for Shelly devices ( @jowi24 - #182042 ) ( matter docs ) Bump holidays to 0.104 ( @gjohansson-ST - #182044 ) ( workday docs ) ( holiday docs ) (dependency) Bump pylutron to 0.4.4 ( @cdheiser - #182049 ) ( lutron docs ) (dependency) Make Nest climate turn_on idempotent ( @allenporter - #182086 ) ( nest docs ) Increase Hot Spring polling interval to 60 seconds ( @Moustachauve - #182150 ) ( hotspring docs ) Fix Google Tasks error handling on DNS failure ( @joostlek - #182195 ) ( google_tasks docs ) Fix Alexa doorbell raises error in state report becase the return status is NO_CONTENT ( @jbouwh - #182209 ) ( alexa docs ) Bump hassil to 3.12.1 ( @synesthesiam - #182213 ) ( conversation docs ) ( assist_satellite docs ) (dependency) Encrypt and decrypt supervisor.tar in backup rewrites ( @agners - #182220 ) ( backup docs ) Bump waterfurnace to 1.9.2 ( @sdague - #182019 ) ( waterfurnace docs ) (dependency) Bump waterfurnace to 1.9.7 ( @sdague - #182263 ) ( waterfurnace docs ) (dependency) Redact the AirVisual API key in debug logging ( @frenck - #182280 ) ( airvisual docs ) Fix Spotify reauth crash when config entry data lacks "id" ( @joostlek - #182290 ) ( spotify docs ) Validate username during onboarding before creating a new user ( @edenhaus - #182320 ) ( onboarding docs ) Fix missing f-string prefix in wiz error message ( @David-Wu1119 - #182363 ) ( wiz docs ) Fix IMAP custom data event template option not reset when cleared ( @jbouwh - #182377 ) ( imap docs ) Fix duplicate devices in Airthings BLE on incomplete read ( @joostlek - #182417 ) ( airthings_ble docs ) Log exception when api fails in WAQI ( @chemelli74 - #182419 ) ( waqi docs ) bump aioamazondevices to 15.2.0 ( @jamesonuk - #182204 ) ( alexa_devices docs ) (dependency) Bump aioamazondevices to 16.3.0 ( @chemelli74 - #182438 ) ( alexa_devices docs ) (dependency) Bump reolink_aio to 0.21.17 ( @starkillerOG - #182472 ) ( reolink docs ) (dependency)
Published Never · Source checked 28 Sep 2026
Release notes and known issues →VEEAMKB2804
Veeam Agent for Linux - veeamsnap and blksnap Extended Linux Distribution Support KB ID: 2804 Product: Veeam Agent for Linux | 6.3.2 | 13.1 Published: 2018-11-29 Last Modified: 2026-09-25 This article provides supplementary information regarding the compatibility of the veeamsnap and blksnap kernel modules with various Linux distributions and kernel versions. It specifically addresses distributions and versions that are not explicitly listed in the System Requirements for Veeam Agent for Linux . Important Note: The absence of a Linux distribution or version from the tables in this article does not indicate that it is unsupported or supported. This article exists solely to provide more granular kernel compatibility information for reference purposes. For determining supported platforms, always refer to the Veeam Agent for Linux User Guide . The veeamsnap and blksnap kernel modules are used for Volume-Level Backup (excluding btrfs volumes) and File-level Backup (excluding Snapshot-Less File-Level Backup). For more information, review the following: Veeam Agent for Linux - Considerations and Limitations Veeam Agent for Linux 13.1.1 blksnap kernel module In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose: snapshot creation. Veeamsnap module is supported up to Linux kernel 5.18 The Blksnap module is supported for Linux kernels starting from 5.10 The default installed module is listed in the Details column for each supported distribution and version. Version Max Supported Kernel VAL Build Shipped with VBR Build Red Hat Enterprise Linux (RHEL) / Rocky / Alma Only Rocky/Alma 8.10 and 9.4 or higher are supported. 10.0-10.2 6.12.0-211.56.1.el10_2 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the blksnap kernel module. 9.0-9.8 5.14.0-687.51.1.el9_8 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the blksnap kernel module. 8.4-8.10 4.18.0-553.168.1.el8_10 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the veeamsnap kernel module. 7.9 ELS RHEL Only 3.10.0-1160.164.1.el7 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the veeamsnap kernel module. Oracle Linux 10.0-10.2 (RHCK) 6.12.0-211.56.1.el10_2 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the blksnap kernel module. 10.0-10.1 (UEK8) 6.12.0-206.104.4.4.el10uek 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the blksnap kernel module. 9.0-9.8 (RHCK) 5.14.0-687.51.1.el9_8 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the blksnap kernel module. 9.5-9.7 (UEK8) 6.12.0-206.104.4.4.el9uek 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the blksnap kernel module. Note: Building the veeamblksnap kernel module on Oracle Linux 9 with UEK R8 kernel requires additional steps. For more information, refer to KB4732 9.0-9.7 (UEK7) 5.15.0-324.217.5.3.el9uek 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the blksnap kernel module. 8.0-8.10 (RHCK) 4.18.0-553.168.1.el8_10 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the veeamsnap kernel module. 8.5-8.10 (UEK7) 5.15.0-324.217.5.3.el8uek 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the veeamsnap kernel module. Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394 8.1-8.10 (UEK6) 5.4.17-2136.359.3.2.el8uek 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the veeamsnap kernel module. 7.7-7.9 (UEK6) 5.4.17-2136.338.4.2.el7uek 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the veeamsnap kernel module. 7.5-7.9 (UEK5) 4.14.35-2047.542.2.el7uek 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the veeamsnap kernel module. 7.1-7.9 (UEK4) 4.1.12-124.93.1.el7uek 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the veeamsnap kernel module. SUSE Linux Enterprise (SLES) 16.0 6.12.0-160000.38 13.1.1.4 Veeam Backup & Replication 13.1.1.18 Uses the blksnap kernel module. 15 SP7 6.4.0-150700.53.81 13.1.1.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →VEEAMKB4098
Veeam Backup for Microsoft 365 Upgrade Paths KB ID: 4098 Product: Veeam Backup for Microsoft 365 | 8 | 8.1 | 8.2 | 8.3 | 8.4 | 8.5 | 8.6 Published: 2021-02-09 Last Modified: 2026-09-18 Shared Server with Veeam Backup & Replication If Veeam Backup & Replication is installed on the same server as Veeam Backup for Microsoft 365 , upgrade Veeam Backup for Microsoft 365 before upgrading Veeam Backup & Replication. Shared Server Compatibility of Veeam Backup for Microsoft 365 and Veeam Backup & Replication Purpose This article documents the upgrade path to be taken to get to the most recent version of Veeam Backup for Microsoft 365 . Solution Consider the following when planning for an upgrade: All backup jobs are stopped during the upgrade process. After the upgrade, backup jobs settings and global configuration options (e.g., notifications and file exclusions) will be preserved. After the upgrade, Repositories , Proxy Servers , and Proxy Pools may require manual interaction to upgrade. Veeam Explorers must be upgraded along with Veeam Backup for Microsoft 365 . End of Support Upgrade Path If you are using a version of Veeam Backup for Microsoft 365 (VB365) that has reached its End of Support (EOS) and cannot be directly upgraded to a supported version, you will need to install a new instance of VB365 using the latest VB365 version . Clarification: If the Upgrade Instructions in the User Guide for a currently supported version of VB365 include an upgrade path from an older, unsupported version, this upgrade pathway is still considered supported. This article provides details on upgrade processes for such situations, provided that a currently supported version of VB365 supports a direct upgrade from these older versions. For example: When VB365 versions 7 and 7a were supported, they provided an upgrade path from VB365 versions 5 and 6. However, VB365 version 8 does not support upgrading directly from those versions. As a result, after VB365 versions 7 and 7a reached EOS, the upgrade paths for VB365 versions 5 and 6 were removed from this document. VB365 version 8.4, which is currently supported, allows upgrading directly from VB365 versions 7 and 7a. Thus, although VB365 7 and 7a are no longer supported themselves, the upgrade details for 7 and 7a are included in this document because an upgrade to VB365 8.4 from those versions is officially supported. 7 to 8.6 Path: 7 (7.0.x) → 8.4 → 8.6 Upgrade to Veeam Backup for Microsoft 365 8.4 Upgrade Proxies and Repositories Upgrade to Veeam Backup for Microsoft 365 8.6 Review the " What You Do After Upgrade " section of the user guide. 7a to 8.6 Path: 7a (7.1.x) → 8.4 → 8.6 Upgrade to Veeam Backup for Microsoft 365 8.4 Upgrade Proxies and Repositories Upgrade to Veeam Backup for Microsoft 365 8.6 Review the " What You Do After Upgrade " section of the user guide. 8.0 to 8.6 Path: 8.0 (8.0.x) → 8.6 Upgrade to Veeam Backup for Microsoft 365 8.6 Review the " What You Do After Upgrade " section of the user guide. 8.1 to 8.6 Path: 8.1 (8.1.x) → 8.6 Upgrade to Veeam Backup for Microsoft 365 8.6 Review the " What You Do After Upgrade " section of the user guide. 8.2 to 8.6 Path: 8.2 (8.2.x) → 8.6 Upgrade to Veeam Backup for Microsoft 365 8.6 Review the " What You Do After Upgrade " section of the user guide. 8.3 to 8.6 Path: 8.3 (8.3.x) → 8.6 Upgrade to Veeam Backup for Microsoft 365 8.6 Review the " What You Do After Upgrade " section of the user guide. 8.4 to 8.6 Path: 8.4 (8.4.x) → 8.6 Upgrade to Veeam Backup for Microsoft 365 8.6 Review the " What You Do After Upgrade " section of the user guide. 8.5 to 8.6 Path: 8.5 (8.5.x) → 8.6 Upgrade to Veeam Backup for Microsoft 365 8.6 Review the " What You Do After Upgrade " section of the user guide. What You Do After Upgrade After upgrading Veeam Backup for Microsoft 365 , be sure to review the " What You Do After Upgrade " section of the user guide. More Information Veeam Backup for Microsoft 365 System Requirements Build numbers and versions of Vee
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →VEEAMKB4875
How to Configure HTTP Proxy for Windows-based Veeam Components KB ID: 4875 Product: Veeam Backup & Replication Veeam ONE Veeam Agent for Microsoft Windows Veeam Cloud Connect Published: 2026-07-14 Last Modified: 2026-09-18 Purpose This article explains how to configure an HTTP proxy for Windows-based Veeam components when the server must reach the internet through a proxy. It applies to Veeam products installed on Windows, including Veeam Backup & Replication, Veeam Cloud Connect, Veeam ONE, Veeam Service Provider Console, and Veeam Agent for Microsoft Windows . Note: This article covers Windows-based components only. For Linux-based components (the Veeam Software Appliance and JeOS-deployed appliances), see KB4807 . Connecting to a Veeam Cloud Connect Provider A tenant's Veeam Backup & Replication server cannot reach a Veeam Cloud Connect provider through an HTTP or HTTPS proxy. Cloud Connect traffic from the tenant's backup server is not HTTP(S)-based and therefore ignores proxy settings. Veeam Service Provider Console 9.3 and Later Starting with Veeam Service Provider Console 9.3, the WinHTTP, Internet Options, and environment variable proxy methods described below have no effect on the Veeam Service Provider Console Server, Web UI, REST API, or Management Agent clients. These components read their own HttpClient_UseProxy setting, which is disabled by default. For information about configuring HTTP proxy with Veeam Service Provider Console 9.3, review KB4930 . Solution Summary Configuring an HTTP proxy for Veeam components on Windows requires setting the proxy in up to three different places: WinHTTP is used by various Veeam components and is configured with netsh . WinINET (Internet Options) is used by components that rely on Windows Internet and is configured per user account. System-wide environment variables ( HTTP_PROXY , HTTPS_PROXY , and NO_PROXY ) are new in Veeam Backup & Replication 13. In Veeam Backup & Replication 13, many components were moved to modern .NET Core, and as such, they read their proxy configuration from environment variables first, falling back to WinINET (Internet Options) only when no environment variables are set. These components will not read the WinHTTP ( netsh ) configuration at all. HTTP Proxy Authentication Is Not Supported Proxy authentication is not supported. Because WinHTTP cannot authenticate to a proxy, the HTTP proxy must not require authentication. Use a proxy that permits connections without credentials, for example one that authorizes clients by source IP address. Configure WinHTTP Proxy System-Wide Configuration This change is system-wide and will affect all applications that use WinHTTP, including other third-party or Windows services that use WinHTTP (e.g., Windows Update). Check Current WinHTTP Proxy Settings This command will display the current WinHTTP settings: netsh winhttp show proxy Copy Set WinHTTP Proxy Settings This command can be used to set a WinHTTP proxy: netsh winhttp set proxy proxy-server= "<proxy>:<port>" Copy Note: Replace <proxy> and <port> in quotes with the actual proxy server's hostname or IP and the port it uses. For example, this command would set the proxy for all protocols to use proxy.domain.tld (192.168.111.111) port 8080: netsh winhttp set proxy proxy-server="192.168.111.111:8080" netsh winhttp set proxy proxy-server="proxy.domain.tld:8080" A more advanced example using a specific protocol and exclusions: netsh winhttp set proxy proxy-server="http=proxy.domain.tld:8080" bypass-list="*.labdomain.tld;*.devlab.tld" Reset WinHTTP Proxy This command can be used to reset the WinHTTP settings back to default (no proxy). netsh winhttp reset proxy Copy Configure Internet Options (WinINET) Proxy Proxy settings within Internet Options are configured per user. While the account you are logged in as may be able to access the internet through the proxy, the backup service account may not have access if that account hasn't had its internet connection settings c
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →VEEAMKB4930
How to Configure HTTP Proxy for Veeam Service Provider Console 9.3+ KB ID: 4930 Product: Veeam Service Provider Console | 9.3 Published: 2026-09-18 Last Modified: 2026-09-18 Purpose This article explains how to configure an HTTP proxy for Veeam Service Provider Console 9.3 and later, which introduced a dedicated proxy configuration mechanism that is disabled by default and does not use the WinHTTP, Internet Options, or environment variable proxy settings described in KB4875 . If a proxy is required to reach the internet and this mechanism is not configured, product update, license auto-update, and single sign-on features fail. Typical entries appear in Server.log : VeeamAutoLk>>AutoLkClient: Failed to get data from the AutoLk service ... A connection attempt failed ... (vac.butler.veeam.com:443) Saml2IdentityProvider: Failed to retrieve data from 'https://login.microsoftonline.com/...' due network error. Exception: System.Net.WebException: The operation has timed out. In versions prior to Veeam Service Provider Console 9.3, the software had no dedicated proxy setting and always used the .NET defaults: the HTTPS_PROXY / HTTP_PROXY environment variables first, then the Internet Options (WinINET) proxy of the service account, as described in KB4875 . Solution Summary Veeam Service Provider Console 9.3 introduced a central HttpClient configuration section. All HTTP clients created by the Veeam Service Provider Console Server, Web UI, REST API, and Management Agent read from it, and the default value of HttpClient_UseProxy is False . Until this key is set to True , every outbound connection is sent directly, regardless of OS-level proxy settings. Configuration Key Reference Key Type Default Description HttpClient_UseProxy Boolean False Master switch. False : no proxy is used, and OS-level settings are ignored. True : uses HttpClient_ProxyAddress if set, otherwise the OS proxy. HttpClient_ProxyAddress String Proxy URI, for example http://proxy.corp.example:8080 Empty: the OS proxy is used, as described in Option 2 below (see also KB4875 ). Set: the proxy is configured directly in Veeam Service Provider Console, as described in Option 1 below. The settings below apply only when HttpClient_ProxyAddress is set, and do not affect the legacy OS proxy settings ( KB4875 ). HttpClient_ProxyBypassOnLocal Boolean True Sends local destinations directly rather than through the proxy. HttpClient_ProxyBypassList List | -separated Regular expressions for additional destinations that bypass the proxy. HttpClient_ProxyUsername String Proxy user. Credentials are sent only when this is non-empty. HttpClient_ProxyPassword String Proxy password. Stored in clear text in the configuration file. Swipe to show more of the table Part 1: Identify Configuration File Location The HttpClient_* keys are added to one of two JSON files, depending on which Veeam Service Provider Console component is being configured: Veeam Service Provider Console Server, Web UI, and REST API: %ProgramData%\Veeam\Veeam Availability Console\Configuration\Service\configuration.overrides.json Veeam Service Provider Console Management Agent: %ProgramData%\Veeam\Veeam Availability Console\Configuration\Agent\configuration.overrides.json The same folder can also contain incremental configuration files named configuration.overrides.NNNNNNNN.json . Those files are generated and merged automatically, and should not be edited manually. Part 2: Add the Keys to the Configuration File Add the HttpClient_* keys to the GeneratedConfiguration object in the file identified above. Keep any existing keys already present in the file. Every value, including Boolean values, must be written as a quoted JSON string, for example "True" , not true . Option 1: Use Modern Built-In Proxy Client (Recommended) This mode is recommended because it does not depend on Windows Internet Options, and unlike legacy proxy methods, it supports proxy authentication. Configuration Example { "GeneratedConfiguration" : { "Http
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-0AD787B16D5D49FC
Microsoft Foundry now exposes enable and disable actions for Foundry agent objects within the Agent 365 governance surface in Microsoft Admin Center, generally available. Administrators can control whether a Foundry agent is available for use across their
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-350888CA43F083D9
Updated troubleshooting guidance is now available for Azure Database for PostgreSQL flexible server. You can use the expanded documentation to diagnose high CPU, memory, IOPS, temporary file usage, and autovacuum issues, helping you identify root causes a
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-3D26AFFDD0CF7203
Azure Database for PostgreSQL elastic clusters now support PostgreSQL 18, bringing the latest PostgreSQL capabilities to distributed, cloud-scale workloads. You can build new applications or modernize existing ones with the performance, reliability, and d
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-7AE57ABD007CCBA0
In public preview, Foundry Agent Service adds Foundry Routines, a native trigger primitive for running published agents automatically. Production agents often need to run on a schedule or when a business event occurs, and today that means assembling exter
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-9923E0BBAA8316B7
In public preview, Microsoft Foundry now lets customers govern the outbound connections a hosted agent can make. Customers author ordered rules matched on destination host, including FQDN with wildcards such as *.contoso.com, with actions to allow, deny,
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-A9FBE9852ADC4B4C
You can now monitor the synchronization status of your logical replication slots in Azure Database for PostgreSQL – Flexible Server using the new logical_replication_slot_sync_status metric. This Azure Monitor metric shows whether each logical replication
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-A9FEDB9861551492
Publishing Microsoft Foundry agents to Microsoft 365 Copilot and Teams is now generally available. An agent only delivers value once it reaches the people who need it, and Foundry developers previously had no native path to make their agents operational a
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-C38BD72DDA10BFA8
The Mdsv4 and Msv4 Series are memory-optimized virtual machine series built on 6th Generation Intel® Xeon® Scalable processors and enhanced with advanced security capabilities and the latest Azure Boost technologies. Designed for demanding memory-intensiv
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →HASHICORPNOMAD-2.0.7
IMPROVEMENTS: dependency: Upgrade to the latest buf (1.72.0), protoc-gen-go (1.36.6), and protoc-gen-go-grpc (1.5.1) [ GH-28525 ] services: the default workload identity policy now allows using wildcard namespace queries for Nomad native services [ GH-28534 ] ui: fixed accessibility color contrast issues [ GH-28022 ] BUG FIXES: api: Fix job statuses error when request body is empty using HTTP2 [ GH-28541 ] client: Fixed a bug where task restart skipped shutdown_delay [ GH-25289 ] core: Fixed a bug where re-submitting an otherwise unchanged job with a different ACL token created a new job version and deployment [ GH-26810 ] deployments: Fixed a bug where system job updates would not result in a new deployment if the prior deployment failed [ GH-28545 ] docker: Fixed a bug where image_pull_timeout was not respected if more than 5min [ GH-28543 ] identity: Fixed a bug where clients would not attempt to recreate expired node identities [ GH-28566 ] namespaces: Fixed a bug where an invalid replication token could delete namespaces in a federated follower region [ GH-28552 ] namespaces: Fixed a bug where namespaces could stop replicating between federated regions [ GH-28552 ] node pools: Fixed a bug where an invalid replication token could delete node pools in a federated follower region [ GH-28552 ] node pools: Fixed a bug where blocking queries would not unblock if a node pool was added automatically by registering a node [ GH-28552 ] node pools: Fixed a bug where node pools could stop replicating between federated regions [ GH-28552 ]
Published Never · Source checked 28 Sep 2026
Release notes and known issues →HASHICORPPACKER-1.16.1
1.16.1 (September 18, 2026) FEATURES: plugin/getter: add support for installing plugins from non-GitHub HTTPS sources, including mirrors and artifact repositories that expose the HashiCorp release directory format. GH-13691 IMPROVEMENTS: communicator/winrm: add configurable connection timeout and retry interval settings. GH-13701 build: update Go to 1.26.8 . GH-13701 BUG FIXES: core/hcl2: pass user variable values to builders, provisioners, and post-processors as packer_user_variables , restoring legacy {{ user "name" }} interpolation in plugin-managed templates. GH-13686 post-processor/shell-local: execute inline scripts through the shell to avoid intermittent ETXTBSY errors. GH-13701 build: bump github.com/shoenig/go-m1cpu to v0.2.2 to prevent segmentation faults on Apple M5 hardware. GH-13696 SECURITY: deps: bump google.golang.org/grpc to v1.83.2 in Packer and the plugin tester to reject requests missing both the :authority and Host headers. GH-13704 GH-13707 DEPENDENCIES: deps: bump github.com/hashicorp/packer-plugin-sdk to v0.6.11 . GH-13701 deps: bump github.com/hashicorp/go-getter/v2 to v2.2.4 . GH-13701 deps: bump github.com/hashicorp/hcp-sdk-go to v0.175.0 , github.com/go-git/go-git/v5 to v5.19.2 , and github.com/klauspost/compress to v1.18.7 . GH-13689 deps: bump golang.org/x/crypto to v0.56.0 , golang.org/x/net to v0.58.0 , and google.golang.org/grpc to v1.83.2 . GH-13701 GH-13707 deps: bump go.opentelemetry.io/otel , go.opentelemetry.io/otel/metric , and go.opentelemetry.io/otel/trace to v1.45.0 , and github.com/go-logr/logr to v1.4.4 . GH-13710 deps: update additional Go module dependencies in Packer and the plugin tester. GH-13689 GH-13701 INTERNAL: docs: update the README contribution link to use the main branch. GH-13700 compliance: update copyright headers. GH-13699
Published Never · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-RU-2026-23847-1
Official SUSE recommended update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-RU-2026-4262-1
Official SUSE recommended update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-RU-2026-4263-1
Official SUSE recommended update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-23875-1
Official SUSE security update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-23876-1
Official SUSE security update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-2685-2
Official SUSE security update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4261-1
Official SUSE security update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4264-1
Official SUSE security update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4265-1
Official SUSE security update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4268-1
Official SUSE security update.
Published 18 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →VUE.JSVUE-3.6.0-RC.9
For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.
Published Never · Source checked 28 Sep 2026
Release notes and known issues →PROMETHEUSALERTMANAGER-0.34.1
[BUGFIX] inhibit: Fix several issues related to inhibitions that caused alerts to be improperly un-muted in some cases. #5542 , #5449 , #5559
Published Never · Source checked 28 Sep 2026
Release notes and known issues →DENODENO-2.9.7
2.9.7 / 2026.09.16 fix(audit): honor configured CA stores ( #36728 ) fix(cache): make HTTP authority paths unambiguous ( #36356 ) fix(cli): accept all valid sys permission descriptors ( #36753 ) fix(cli): don't duplicate passthrough args for deno deploy/sandbox ( #36722 ) fix(cli): generate valid bash completions ( #36736 ) fix(cli): preserve double dash before the entrypoint ( #36835 ) fix(cli): restore optional-value semantics for deno bundle --sourcemap ( #36723 ) fix(completions): keep the dash on short flags in zsh completions ( #36720 ) fix(desktop): complete deferred window close and fix NAPI symbol export on Linux ( #36718 ) fix(ext/http): extract traceparent from Deno.serve regardless of header name case ( #36840 ) fix(ext/node): allow repeated child process signals ( #36644 ) fix(ext/node): check resolved IP against net deny list in tcp_wrap bind ( #36482 ) fix(ext/node): don't panic on prime sizes below 2 bits ( #36400 ) fix(ext/node): improve node:dns error codes and lookupService/setLocalAddress compat ( #36552 ) fix(ext/node): normalize resourceUsage maxRSS on macOS ( #36784 ) fix(install): validate lockfile tarball registry paths ( #36473 ) fix(lsp): resolve the newest prerelease of jsr packages that have no stable release ( #36655 ) fix(net): check permissions for multicast membership ( #36529 ) fix(node): align IncomingMessage header map prototypes ( #36438 ) fix(node): preserve AsyncLocalStorage exit context ( #36464 ) fix(npm): correct the pnpm lockfile import against real-world lockfiles ( #36727 ) fix(npm): validate lockfile tarball origins ( #36430 ) fix(permissions): fold unix socket paths for case-insensitive filesystems ( #36553 ) fix(permissions): parse unix: net rules as POSIX paths ( #36785 ) fix(process): clear supplementary groups before changing identity ( #36433 ) fix(sqlite): refuse symlink database paths ( #36357 ) fix(transpile): don't report diagnostics from bundled assets in declaration emit ( #36716 ) fix(web): avoid flushing compression streams on every write ( #36744 ) fix: add missing property desktop.app.identifier ( #36774 ) fix: hash source contents for V8 code cache ( #36743 ) fix: point JSON schema $id values at the maintained GitHub raw endpoint ( #36747 ) fix: toplevel fetch/cron leak its spans ( #36757 ) fix: validate --ignore-scripts package selectors ( #36742 ) perf(core): drop dead module-graph retention ( #36683 ) perf(core): make extension op tables const in static memory ( #36696 ) perf(core): split OpCtx into shared OpCommonCtx + borrowed op declarations ( #36693 ) perf(ext/node): Buffer hex paths via native Uint8Array toHex/setFromHex ( #36531 )
Published Never · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-152.0.7977.134
The Extended Stable channel has been updated to 152.0.7977.134 for Windows and Mac which will roll out over the coming days/weeks. A full list of changes in this build is available in the log . Interested in switching release channels? Find out how here . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Srinivas Sista Google Chrome
Published 17 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-153.0.8010.52
The Stable channel has been updated to 153.0.8010.52/.53 for Windows and Mac and 153.0.8010.52 to Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes 16 security fixes. Please see the Chrome Security Page for more information. [TBD][ 500417361 ] Critical CVE-2026-93374: Use after free in Dawn. Reported by Florian Schweitzer on 2026-04-08 [N/A][ 548085797 ] Critical CVE-2026-93372: Buffer overflow in WebGL. Reported by Google on 2026-08-17 [$3,000][ 550839154 ] High CVE-2026-93375: Incorrect reference resolution in Tracing. Reported by M. Fauzan Wijaya (Gh05t666nero) on 2026-08-22 [TBD][ 541707261 ] High CVE-2026-93382: Use after free in PDFium. Reported by WinD39 - Huynh Dinh Vu on 2026-08-02 [N/A][ 553130676 ] High CVE-2026-93387: Improper state validation in Skia. Reported by Google on 2026-08-26 [N/A][ 553132214 ] High CVE-2026-93373: Use after free in Extensions. Reported by Google on 2026-08-26 [TBD][ 556853443 ] High CVE-2026-93381: Buffer overflow in PDFium. Reported by SeungMyung Lee (@sm1ee), Siung kim (@ksw9722) on 2026-09-03 [TBD][ 560039872 ] High CVE-2026-93379: Incorrect authorization in ORB. Reported by OGINOME Tomohito on 2026-09-11 [N/A][ 560121552 ] High CVE-2026-93377: Type confusion in V8. Reported by Google on 2026-09-11 [N/A][ 498411599 ] Medium CVE-2026-93380: Race condition in FileSystem. Reported by Google on 2026-04-01 [N/A][ 511832293 ] Medium CVE-2026-93384: Server-side request forgery in Omnibox. Reported by Google on 2026-05-10 [N/A][ 515493668 ] Medium CVE-2026-93383: Information leak in Permissions. Reported by Google on 2026-05-22 [N/A][ 520521197 ] Medium CVE-2026-93376: Out of bounds read in DataTransfer. Reported by Google on 2026-06-05 [N/A][ 540051167 ] Medium CVE-2026-93378: Missing authorization in Storage. Reported by Google on 2026-07-28 [N/A][ 553136980 ] Medium CVE-2026-93385: Information leak in Paint. Reported by Google on 2026-08-26 [N/A][ 513996595 ] Low CVE-2026-93386: UI misrepresentation in WebAppInstalls. Reported by Google on 2026-05-17 We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. Many of our security bugs are detected using AddressSanitizer , MemorySanitizer , UndefinedBehaviorSanitizer , Control Flow Integrity , libFuzzer , or AFL . Interested in switching release channels? Find out how here . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Srinivas Sista Google Chrome
Published 17 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-16820.2.0
The Dev channel is being updated to OS version 16820.2.0 (Browser version 155.0.8059.0) for most ChromeOS devices. If you find new issues, please let us know one of the following ways File a bug Visit our ChromeOS communities General: Chromebook Help Community Beta Specific: ChromeOS Beta Help Community Report an issue or send feedback on Chrome Interested in switching channels? Find out how . Andy Wu, Google ChromeOS
Published 17 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-26D0D4EE1DA64FE2
The Stable channel has been updated to 153.0.8010.52/.53 for Windows and Mac and 153.0.8010.52 to Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes 16 security fixes. Please see the Chrome Security Page for more information. [TBD][ 500417361 ] Critical CVE-2026-93374: Use after free in Dawn. Reported by Florian Schweitzer on 2026-04-08 [N/A][ 548085797 ] Critical CVE-2026-93372: Buffer overflow in WebGL. Reported by Google on 2026-08-17 [$3,000][ 550839154 ] High CVE-2026-93375: Incorrect reference resolution in Tracing. Reported by M. Fauzan Wijaya (Gh05t666nero) on 2026-08-22 [TBD][ 541707261 ] High CVE-2026-93382: Use after free in PDFium. Reported by WinD39 - Huynh Dinh Vu on 2026-08-02 [N/A][ 553130676 ] High CVE-2026-93387: Improper state validation in Skia. Reported by Google on 2026-08-26 [N/A][ 553132214 ] High CVE-2026-93373: Use after free in Extensions. Reported by Google on 2026-08-26 [TBD][ 556853443 ] High CVE-2026-93381: Buffer overflow in PDFium. Reported by SeungMyung Lee (@sm1ee), Siung kim (@ksw9722) on 2026-09-03 [TBD][ 560039872 ] High CVE-2026-93379: Incorrect authorization in ORB. Reported by OGINOME Tomohito on 2026-09-11 [N/A][ 560121552 ] High CVE-2026-93377: Type confusion in V8. Reported by Google on 2026-09-11 [N/A][ 498411599 ] Medium CVE-2026-93380: Race condition in FileSystem. Reported by Google on 2026-04-01 [N/A][ 511832293 ] Medium CVE-2026-93384: Server-side request forgery in Omnibox. Reported by Google on 2026-05-10 [N/A][ 515493668 ] Medium CVE-2026-93383: Information leak in Permissions. Reported by Google on 2026-05-22 [N/A][ 520521197 ] Medium CVE-2026-93376: Out of bounds read in DataTransfer. Reported by Google on 2026-06-05 [N/A][ 540051167 ] Medium CVE-2026-93378: Missing authorization in Storage. Reported by Google on 2026-07-28 [N/A][ 553136980 ] Medium CVE-2026-93385: Information leak in Paint. Reported by Google on 2026-08-26 [N/A][ 513996595 ] Low CVE-2026-93386: UI misrepresentation in WebAppInstalls. Reported by Google on 2026-05-17 We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. Many of our security bugs are detected using AddressSanitizer , MemorySanitizer , UndefinedBehaviorSanitizer , Control Flow Integrity , libFuzzer , or AFL . Interested in switching release channels? Find out how here . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Srinivas Sista Google Chrome
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-3ABD6F7B26EB859C
The Dev channel is being updated to OS version 16820.2.0 (Browser version 155.0.8059.0) for most ChromeOS devices. If you find new issues, please let us know one of the following ways File a bug Visit our ChromeOS communities General: Chromebook Help Community Beta Specific: ChromeOS Beta Help Community Report an issue or send feedback on Chrome Interested in switching channels? Find out how . Andy Wu, Google ChromeOS
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-4EA595B8E28D424B
The Extended Stable channel has been updated to 152.0.7977.134 for Windows and Mac which will roll out over the coming days/weeks. A full list of changes in this build is available in the log . Interested in switching release channels? Find out how here . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Srinivas Sista Google Chrome
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-75F09C950287BFAD
Hi, everyone! We've just released Chrome 153 (153.0.8010.52) for Android. It'll become available on Google Play over the next few days. This release includes stability and performance improvements. You can see a full list of the changes in the Git log . If you find a new issue, please let us know by filing a bug . Android releases contain the same security fixes as their corresponding Desktop releases (Windows 153.0.8010.52/.53) unless otherwise noted. Harry Souders Google Chrome
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-WORKSPACE-B47AA38E50EBEA4C
In April, we announced notebooks in Gemini as a dedicated, focused space for individual users to organize their projects and conversations. Now, students of all ages, educators, and professionals can access notebooks to keep conversations about a topic organized in one place. For example: Students can upload all of their materials for a specific course into a single notebook to turn Gemini into a personalized, course-aware study partner that can generate custom practice quizzes and simplify complex topics. Educators can upload their curriculum standards, assignment rubrics, and lesson templates to rapidly generate aligned coursework, differentiated learning materials, and targeted student feedback. Professionals can upload product information, project details, research reports, and strategy notes for a specific topic into a notebook to synthesize key insights and draft deliverables. This tool also combines two of Google’s most powerful AI tools, the Gemini app and Gemini Notebook, to unlock new ways of working and studying. For example, if you’re a student, try adding class notes to a notebook and using Gemini Notebook to create a Cinematic Video Overview. The next day, open the notebook in the Gemini app and ask it to create a study guide based on that same material. Getting started Admins: Access to Notebooks in Gemini is on by default, and is controlled using the Gemini App and Gemini Notebook access settings. As an administrator of your organization's Google Accounts, you can control who can use Notebooks in Gemini. Notebooks in Gemini are available to users who are in a group or OU with both Gemini Notebook and Gemini set to On. Visit the Help Center to learn more about turning Gemini and Gemini Notebook on or off for users. End users: Open the left side panel in the Gemini app and click “New notebook” to start adding your sources and focus area. You can add up to 10 sources to your notebook. Visit the Help Center to learn more . Rollout pace Rapid Release and Scheduled Release domains: Gradual rollout (up to 15 days for feature visibility) started on September 14, 2026 Availability Available to all Google Workspace customers and Workspace Individual subscribers outside of the European Economic Area (EEA), as well as users with personal Google accounts globally Resources News from Google: Try notebooks in Gemini to easily keep track of projects Gemini Notebooks Help: Notebooks in Gemini Apps Google Workspace Admin Help: Turn the Gemini App on or off
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-WORKSPACE-B8A5134D8C4587D2
Users will now be able to use Gemini in Workspace to directly interact with Asana, Atlassian Rovo, HubSpot, Intuit Mailchimp, Intuit QuickBooks, Monday, and Salesforce through Model Context Protocol (MCP) integrations . This will enable them to access information directly without needing to switch tabs, download files, or interrupt workflows across our Google Workspace apps including Sheets, Gmail, Drive, Docs, Chat, and more. Getting started Admins: This feature will be ON by default for users with Gemini for Google Workspace access, and can be managed at the domain, organizational unit (OU), or group level in the Admin console under Apps > Google Workspace > Gemini for Workspace > Third-Party Connectors. Admins can control which third-party connectors are enabled for their organization and manage access policies. Visit the Help Center to learn more about managing third-party connectors for Gemini . End users : Once enabled by an admin, end users can access third-party connectors through the Gemini side panel in Docs, Sheets, and Slides, as well as in Google Chat. Visit the Help Center to learn more about third party integrations with Gemini in Google Workspace . Rollout pace Rapid Release and Scheduled Release domains: Available now Availability Business: Business, Standard, and Plus Enterprise: Enterprise, Standard, and Plus Consumer: Google AI , Pro, and Ultra Other Editions: Enterprise Essentials Plus Education Add-ons: Google AI Pro for Education; Teaching and Learning; Endpoint Education Resources Google Workspace Admin Help: Managing third-party connectors for Gemini Google Help: Collaborate with Gemini in Google Sheets Google Help: Get started with Ask Gemini in Google Chat
Published 15 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-WORKSPACE-D5601C107DE280B1
To expand the capabilities of Workspace Studio and help teams build powerful, custom automations, we are introducing four new features for flows in Workspace Studio: custom starters, custom steps, third-party (3P) integrations, and webhooks. These new capabilities empower users to seamlessly connect custom Google Apps Script functions, integrate third-party services, and trigger external webhooks directly within flows in Workspace Studio. All of these features are backed by granular enterprise security controls that allow admins to safely enable and adopt agentic capabilities across their organizations. Custom starters: Build and publish custom, real-time triggers to run flows based on events in other applications. Custom starter that triggers a Studio Flow from an external application Custom steps: Build and run custom logic (e.g. using Apps Script) and tailor flows to advanced business needs. Create custom steps using Apps Script Third-party integrations (Beta): Connect third-party applications and services to pass data effortlessly between Workspace and external tools to automate your business flows. The following integrations are available: Asana Confluence Hubspot Jira Mailchimp Quickbooks Salesforce Slack Step to add a Jira comment in Studio Flows Webhooks: Send HTTP requests to external endpoints and trigger actions in them. On supported editions, admins can set an URL allowlist for webhook access. Webhook step in Studio Flows Getting started Admins: These features are OFF by default. Admins can enable them in the Workspace Admin Console under Apps > Google Workspace > Workspace Studio: Custom steps settings Integration settings Webhook settings Admins can change the human approval requirements in the Workspace Admin Console under Apps > Google Workspace > Workspace Studio > Approvals. Custom steps and Integration have their own approval settings, while Webhooks respect the approval settings for Sensitive Steps . Visit the Admin Help Center to learn more about setting up Workspace Studio , allowing or blocking custom starters and steps , allowing or blocking integration steps , and allowing or blocking send a webhook . End users: Try the new features in Google Workspace Studio . Learn more by reviewing the Help Center articles for Custom Starters and Steps , Third-party Integrations , and Webhooks Rollout pace Admin console settings Rapid and Scheduled Release domains: Full rollout (1-3 days for feature visibility) starting on September 17, 2026 End-user visible features Rapid Release domains: Full rollout (1-3 days for feature visibility) starting on September 21, 2026 Scheduled Release domains: Gradual rollout (up to 15 days for feature visibility) starting on September 30, 2026 Availability Business: Business Starter, Standard, and Plus Enterprise: Enterprise Standard and Plus Education: Education Fundamentals, Standard, and Plus Education Add-ons: Google AI Pro for Education; Teaching and Learning Other Add-ons: AI Expanded Access *Webhook URL allowlist functionality is available for Business Plus; Enterprise Standard and Enterprise Plus; Education Standard and Education Plus Resources Google Workspace Admin Help: Workspace Studio Workspace Studio Help: Get Started with Workspace Studio YouTube: Workspace Studio Playlist Discord: Workspace Studio Channel
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-WORKSPACE-DDF7CF9A9B19B271
We’re introducing Expert Intelligence , a cross Google initiative that helps users engage with trusted sources through Google AI products, starting with Gemini Notebook. Featuring more than 100,000 books from major publishers, employees and students can now incorporate insights from leading authors, publications, and domain experts directly into Gemini Notebook. Users will be able to add compatible ebooks they’ve purchased from Google Play Books directly to a Gemini Notebook, making it simple for them to ask questions about a book and receive responses grounded directly in its text. Readers can also use Gemini Notebooks to help you understand books in new ways, for example, by generating Infographics, Audio Overviews, Quizzes, or more. We’re also providing a book on us for users 18 years or older in the U.S. while supplies last. Even better, employees and students can combine an author’s expertise with a variety of other sources, including their own information. For example: A student can upload their class syllabus and lecture notes alongside a purchased book to generate an Audio Overview and practice quizzes to prepare for final exams. A manager can ask Gemini Notebook to help brainstorm strategies on how to best give employees feedback and navigate tough conversations by consulting a book on management best practices. Note: To interact with an ebook in a shared notebook—such as asking questions or creating artifacts—recipients must also have purchased an eligible Play Book ebook. Getting started Admins: In order for end users to access this feature, they must be in an OU with Gemini Notebook, Google Play, and Google Books set to On. Visit the Help Center to learn more about turning Gemini Notebook and Google Play and Google Books on or off for users. Tip: For students who need access only to specific books, admins can purchase books using Buy for Groups and allocate to the students without needing to provide Google Play access (available to organizations with Google Workspace for Education Plus or a Teaching & Learning add-on). End users: There is no end user setting for this feature. To see if a book is eligible for Expert Intelligence, visit Google Play Books. If the ebook is eligible, you’ll see Gemini Notebook listed when you click the “Tools” badge on a book’s detail page, or you can browse eligible books . Visit the Help Center to learn more about adding Play Books ebooks as a source in Gemini Notebook. Rollout pace Rapid Release and Scheduled Release domains: Available now Availability Available to all Google Workspace customers, Workspace Individual subscribers, and users with personal Google accounts who have Gemini Notebook, Google Play, and Google Books enabled Resources Keyword: Expert Intelligence: a new way for you to engage with trusted content Gemini Notebook Help: Add or discover new sources for your notebook Google Play Books Help: Expert Intelligence
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GRAFANA LABSGRAFANA-LOKI-3.6.17
3.6.17 (2026-09-09) Bug Fixes security/HIGH/pkg/push: Update module google.golang.org/grpc to v1.83.1 [SECURITY] (release-3.6.x) ( #24330 ) ( d8d78f6 ) security/HIGH/pkg/push: Update module google.golang.org/grpc to v1.83.2 [SECURITY] (release-3.6.x) ( #24444 ) ( 6d21d6b ) security/HIGH/: Update module google.golang.org/grpc to v1.83.1 [SECURITY] (release-3.6.x) ( #24329 ) ( ed9df58 ) security/HIGH/: Update module google.golang.org/grpc to v1.83.2 [SECURITY] (release-3.6.x) ( #24430 ) ( ee0ef56 ) security/MEDIUM/: Update module github.com/containerd/containerd/v2 to v2.0.12 [SECURITY] (release-3.6.x) ( #24461 ) ( 7fa1224 ) security/UNKNOWN/: Update module golang.org/x/crypto to v0.55.0 [SECURITY] (release-3.6.x) ( #24256 ) ( 85b2d4f ) security/UNKNOWN/: Update module golang.org/x/crypto to v0.56.0 [SECURITY] (release-3.6.x) ( #24336 ) ( 57bc922 ) security/UNKNOWN/: Update module golang.org/x/mod to v0.40.0 [SECURITY] (release-3.6.x) ( #23963 ) ( c08bf30 )
Published Never · Source checked 28 Sep 2026
Release notes and known issues →GRAFANA LABSGRAFANA-LOKI-3.7.8
3.7.8 (2026-09-17) Bug Fixes security/HIGH/pkg/push: Update module google.golang.org/grpc to v1.83.2 [SECURITY] (release-3.7.x) ( #24433 ) ( 4d5dc2b ) security/HIGH/: Update module google.golang.org/grpc to v1.83.1 [SECURITY] (release-3.7.x) ( #24328 ) ( 0a01797 ) security/HIGH/: Update module google.golang.org/grpc to v1.83.2 [SECURITY] (release-3.7.x) ( #24429 ) ( 14b5da8 ) security/MEDIUM/: Update module github.com/containerd/containerd/v2 to v2.2.8 [SECURITY] (release-3.7.x) ( #24460 ) ( 3e917f2 ) security/UNKNOWN/pkg/push: Update module golang.org/x/net to v0.56.0 [SECURITY] (release-3.7.x) ( #23422 ) ( 41064da ) security/UNKNOWN/pkg/push: Update module google.golang.org/grpc to v1.83.1 [SECURITY] (release-3.7.x) ( #23416 ) ( cd8e76d ) security/UNKNOWN/: Update module golang.org/x/crypto to v0.56.0 [SECURITY] (release-3.7.x) ( #24335 ) ( 47149cb )
Published Never · Source checked 28 Sep 2026
Release notes and known issues →VEEAMKB4292
Veeam Backup for Microsoft 365 Restore Portal Error: "The server has rejected the client credentials" KB ID: 4292 Product: Veeam Backup for Microsoft 365 | 6.0 | 7.0 | 7a | 8 | 8.1 | 8.2 | 8.3 | 8.4 | 8.5 | 8.6 Published: 2022-03-24 Last Modified: 2026-09-17 Challenge When attempting to login to the Veeam Backup for Microsoft 365 Restore Portal , the following error occurs: The server has rejected the client credentials. Solution At this time, three known scenarios cause this error. Each scenario is described below with its corresponding resolution. Scenario 1: Restore operator authentication certificate is installed in the wrong certificate store When the "Enable restore operator authentication with Microsoft credentials" option was configured, a certificate was selected from the certificate store or imported from a PFX file. That certificate is not installed in the location required for its type, so the certificate chain cannot be validated. The required placement depends on the certificate type: Self-signed certificate: The certificate is its own trust anchor. It must be present in the Personal certificate store of the Veeam Backup for Microsoft 365 server with an exportable private key. If the Veeam Backup for Microsoft 365 REST API component is installed on a separate machine, this certificate must also be imported into the Trusted Root Certification Authorities store on that machine. Certificate issued by a Certification Authority: The certificate must remain in the Personal certificate store of the Veeam Backup for Microsoft 365 server with its private key. Only the issuing root CA certificate belongs in the Trusted Root Certification Authorities store. If a certificate issued by a Certification Authority has been installed in the Trusted Root Certification Authorities store, it is treated as a trust anchor, and the following error occurs: Failed to validate remote certificate. Failed to validate the certificate chain: The revocation function was unable to check revocation for the certificate. Reference: Enabling Restore Operator Authentication Scenario 2: Updated application certificate has not been added to Microsoft Entra The application certificate within the Restore Portal settings has been updated, but it has not been added to the application settings of Microsoft Entra. When the certificate is updated within Veeam Backup for Microsoft 365 , it must also be added in the application settings through the Microsoft Entra admin center . Reference: Restore Portal Settings Scenario 3: Tenant-side configuration has not been completed For Backup as a Service for Microsoft 365 usage scenarios, the tenant must complete the configuration steps that assign the permissions required for Restore Portal access. Ensure that all steps provided in the Restore Portal Configuration for " On Tenant Side " have been completed. If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case. To submit feedback regarding this article, please click this link: Send Article Feedback To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →VEEAMKB4874
How to Identify and Repair Files That Cannot Be Opened After Restore KB ID: 4874 Product: Veeam Backup for Microsoft 365 | 8 Published: 2026-06-29 Last Modified: 2026-09-17 Updated for Veeam Backup for Microsoft 365 8.6 This article has been updated to document new Integrity Check capabilities included with Veeam Backup for Microsoft 365 8.6 . The integrity check can now process JET-based repositories and immutable repositories. Customers who ran an Integrity Check while running Veeam Backup for Microsoft 365 8.5, are advised to upgrade to version 8.6 and run the Integrity Check again. Purpose This article provides steps to identify and repair SharePoint, OneDrive, Teams files, and list attachments that were backed up with corrupted content due to the issue described in KB4835 . Solution Before You Begin Ensure you’re running Veeam Backup for Microsoft 365 version 8.5 or later before proceeding. When the Integrity Check is performed on an object storage repository, there will be a temporary increase in the number of API calls the storage system handles while previously written files are scanned for inconsistencies. The redownloading of affected files afterward also increases storage usage on that same repository. Repair Procedure The following steps are to be completed for each repository that contains SharePoint, OneDrive, and Teams files. The steps in this section use PowerShell commands that reference variables defined in one step and used in later steps, so all 5 steps should be completed sequentially for each repository. In Veeam Backup for Microsoft 365 8.5, this procedure only supports non-immutable object storage repositories. In version 8.6 and later, support for immutable object storage repositories and JET-based repositories was added. Step 1: Run an Integrity Check Open Veeam Backup for Microsoft 365 . In the main menu ( ☰ ) , expand Console , and select PowerShell . Note: Launching PowerShell from outside Veeam Backup for Microsoft 365 may require manual loading of PowerShell modules . In the PowerShell console, run the following command to import the module used by this article: This DLL module must be loaded directly to ensure the Start-VBORepositoryRepairSession cmdlet is available. Import-Module "C:\Program Files\Veeam\Backup365\Veeam.Archiver.PowerShell.dll" Copy Run the following cmdlet for the repository being investigated: $repository = Get-VBORepository - Name "Repository Name" Test-VBORepository - Repository $repository Copy Step 2: Review the Results If the Test-VBORepository output contains any of the following messages, proceed to Step 3: For Veeam Backup for Microsoft 365 8.5 The following site has corrupted file data The following list contains items referencing corrupted files For Veeam Backup for Microsoft 365 8.6 The following site has inconsistent file data The following list contains items referencing inconsistent files WARNING: The following list contains items that reference files with incomplete downloads If no messages appear, no further action is required for that repository. If you see messages other than those listed above, please contact Veeam Technical Support for assistance in investigating further. Step 3: Scan Repository and Flag Affected Items Run the following cmdlet to scan the repository and flag the affected items for re-backup. Their correct content will be redownloaded during the next backup job run in Step 4. Note that during scanning, the repository remains locked for any other operations, including backups, restores, and management. All backup and restore sessions related to this repository must be stopped before running a repair session. For an object storage repository : $session = Start-VBORepositoryRepairSession - Repository $repository - Type CleanMissingFilesData - Mode Full - Scope Full Copy For a JET-based repository (Veeam Backup for Microsoft 365 8.6+ Only): $session = Start-VBORepositoryRepairSession - Repository $repository - Type CleanMissingFilesData - Mode F
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →ELASTICKIBANA-5.1
Summary Reverts auto-installing product docs. Co-authored-by: qn895 quynh.nguyen@elastic.co Co-authored-by: Claude Fable 5.1 noreply@anthropic.com
Published Never · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-047027A1801550DD
Azure Payments HSM v2 is a highly available, single-tenant Payment HSM service for payment processing, credential issuance, PIN processing, key management, and authentication data protection. Customers retain exclusive administrative control of an isolate
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →MICROSOFTMICROSOFT-AZURE-A333150BEE38AE4D
High-scale mesh using connected group in Azure Virtual Network Manager is now in general availability. In available regions, customers may connect up to 3,000 virtual networks in a single mesh connectivity configuration by default and higher scale IP conn
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →REDISREDIS-8.10.2
Update urgency: SECURITY : There are security fixes in the release. Security fixes #15673 Commands queued in a transaction could still access keys whose ACL permissions were revoked before the transaction was executed #15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no ) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload RedisSearch: KNN queries on indexes with very long vector field names could cause the server to crash Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash
Published Never · Source checked 28 Sep 2026
Release notes and known issues →REDISREDIS-8.2.10
Update urgency: SECURITY : There are security fixes in the release. Security fixes #15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no ) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash
Published Never · Source checked 28 Sep 2026
Release notes and known issues →REDISREDIS-8.4.7
Update urgency: SECURITY : There are security fixes in the release. Security fixes #15673 Commands queued in a transaction could still access keys whose ACL permissions were revoked before the transaction was executed #15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no ) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash
Published Never · Source checked 28 Sep 2026
Release notes and known issues →REDISREDIS-8.6.7
Update urgency: SECURITY : There are security fixes in the release. Security fixes #15673 Commands queued in a transaction could still access keys whose ACL permissions were revoked before the transaction was executed #15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no ) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash
Published Never · Source checked 28 Sep 2026
Release notes and known issues →REDISREDIS-8.8.3
Update urgency: SECURITY : There are security fixes in the release. Security fixes #15673 Commands queued in a transaction could still access keys whose ACL permissions were revoked before the transaction was executed #15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no ) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash
Published Never · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-RU-2026-4246-1
Official SUSE recommended update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4243-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4244-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4247-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4248-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4249-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4250-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4251-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4252-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4253-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4254-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4255-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4256-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4258-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →SUSESUSE-SU-2026-4259-1
Official SUSE security update.
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →HASHICORPVAULT-2.1.1
2.1.1 September 16, 2026 SECURITY: core: Update github.com/apache/thrift to v0.24.0 to fix security vulnerability GHSA-8wv5-x4w7-5gww . core: Update golang.org/x/crypto to v0.56.0 to fix security vulnerabilities GO-2026-6354 and GO-2026-6355. core: Update google.golang.org/grpc to v1.83.2 to fix security vulnerability GHSA-2v4p-qf9q-27wj . CHANGES: auth/jwt: Added Okta provider with group fetching from Admin API when fetch_groups=true and truncation is detected. auth/jwt: Update plugin to v0.26.4 core/raft: Limited concurrent retry-join workers to 20. Any further retry-join attempts while 20 are in progress will result in an error ( too many concurrent raft retry joins in progress ). core: Bump Go version to 1.26.8 IMPROVEMENTS: secrets import: Add allowed_ipv4_cidrs to source_aws and source_azure Secrets Import blocks to allow private CIDR exemptions for SSRF-safe connectivity. secrets/pki: add an additional field to include an RFC 5280 revocation reason for (/pki/revoke) and (/pki/revoke-with-key). ui: Bump dompurify to 3.4.15 to address SECVULN advisories BUG FIXES: Secrets Recovery (enterprise): Fixing Vault panic in cli when running vault recover without a path. auth/jwt: Fixed incorrect HTTP status codes returned during agent ceiling policy evaluation. auth/token: Fixed a bug where auth/token/lookup and auth/token/lookup-self returned 403 for JWT tokens in a non-root namespace. consumption-billing: Fix OIDC identity token billing units being computed incorrectly across periodic flush cycles. The billing scalar now applies per-token duration adjustment, so the reported scalar and the per-mount attribution breakdown are always consistent. core/activitylog (enterprise): Fix a panic in CensusReport ACL policy metrics collection by safely handling transient missing policies and nil policy path/permission data while policies are changing. core/mounts: Fixed vault secrets move (and vault auth move ) incorrectly placing a mount in the root namespace when the destination path has a leading slash. oauth-resource-server (enterprise): Fix issue where RAR enforcement was skipped when the token's iss claim had cosmetic differences (e.g. different casing or trailing slash) compared to the issuer stored in the resource server profile. plugins: Fix issue with vault plugin reload -mounts command when run in the root namespace secrets-sync (enterprise): Fix LIST /v1/sys/sync/associations intermittently returning zero associations/secrets by forwarding the request to the active node instead of allowing it to be served locally by a performance standby or performance secondary. secrets/pki (enterprise): Fix panic in CMPv2 sentinel field parsing when cert request messages are empty. secrets/pki (enterprise): Fix unified CRL not being rebuilt after the background transfer copies locally-revoked certificates into unified storage. ui: Fix agent registry ceiling policies not displaying due to incorrect property name ui: Fix total secrets count binding on secrets sync overview page to match the API response key. ui: Resolve the flickering on the login page when a trailing slash is added to the namespace in the field.
Published Never · Source checked 28 Sep 2026
Release notes and known issues →VUE.JSVUE-3.5.43
For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.
Published Never · Source checked 28 Sep 2026
Release notes and known issues →WORDPRESSWORDPRESS-7.1.1
This security and maintenance release features 17 bug fixes on Core, 19 bug fixes for the Block Editor, and 11 security fixes. Because this is a security release, it is recommended that you update your sites immediately. You can download WordPress 7.1.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update […]
Published 17 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →WORDPRESSWORDPRESS-A6469D6AB2F6ED18
This security and maintenance release features 17 bug fixes on Core, 19 bug fixes for the Block Editor, and 11 security fixes. Because this is a security release, it is recommended that you update your sites immediately. You can download WordPress 7.1.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update […]
Published 17 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEANGULAR-22.1.7
compiler Commit Description wrap @for collection expression before appending non-null assertion core Commit Description return null when getDirectiveMetadata is called with null or undefined forms Commit Description mark control as dirty before setting its value in FVC interop
Published Never · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEANGULAR-22.2.0-RC.0
compiler Commit Description wrap @for collection expression before appending non-null assertion compiler-cli Commit Description add strictUnclaimedEventNames option to catch misspelled output bindings core Commit Description return null when getDirectiveMetadata is called with null or undefined update FakeNavigation to match WHATWG HTML spec forms Commit Description mark control as dirty before setting its value in FVC interop router Commit Description maintain frozen state on rollback until resource loading completes mark router_resource module-level symbols as side-effect free
Published Never · Source checked 28 Sep 2026
Release notes and known issues →CLOUDFLARECLOUDFLARE-C24CFC1204C48581
A modern storefront can look healthy while malicious JavaScript quietly siphons revenue, hijacks clicks, or rewrites analytics. See how Cloudflare's machine learning models surface evasive client-side attacks for analyst investigation.
Published 16 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →DRUPALDRUPAL-10.6.17
Drupal 10.6.17
Published Never · Source checked 28 Sep 2026
Release notes and known issues →DRUPALDRUPAL-11.3.17
Drupal 11.3.17
Published Never · Source checked 28 Sep 2026
Release notes and known issues →DRUPALDRUPAL-11.4.7
Drupal 11.4.7
Published Never · Source checked 28 Sep 2026
Release notes and known issues →GITLABGITLAB-19.4.0
Version v19.4.0
Published Never · Source checked 28 Sep 2026
Release notes and known issues →GITLABGITLAB-19.4.0-RC44
Version v19.4.0-rc44
Published Never · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-154.0.8037.44
The Stable channel has been updated to 154.0.8037.44/.45 for Windows. as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log . You can find more details about early Stable releases here . Interested in switching release channels? Find out how here . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Srinivas Sista Google Chrome
Published 16 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-154.0.8037.49
Hello Everyone! We've just released Chrome 154 (154.0.8037.49) for Android to a small percentage of users. It'll become available on Google Play over the next few days. You can find more details about early Stable releases here . This release includes stability and performance improvements. You can see a full list of the changes in the Git log . If you find a new issue, please let us know by filing a bug . Krishna Govind Google Chrome
Published 16 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-155.0.8059.4
Hi everyone! We've just released Chrome Beta 155 (155.0.8059.4) for Android. It's now available on Google Play . You can see a partial list of the changes in the Git log . For details on new features, check out the Chromium blog , and for details on web platform updates, check here . If you find a new issue, please let us know by filing a bug . Chrome Release Team Google Chrome
Published 16 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-155.0.8059.5
The Chrome team is excited to announce the promotion of Chrome 155 to the Beta channel for Windows, Mac and Linux. Chrome 155.0.8059.5 contains our usual under-the-hood performance and stability tweaks, but there are also some cool new features to explore - please head to the Chromium blog to learn more! A partial list of changes is available in the Git log . Interested in switching release channels? Find out how . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Chrome Release Team Google Chrome
Published 16 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-16765.49.0
The Stable channel is being updated to OS version 16765.49.0 (Browser version 152.0.7977.129 ) for most ChromeOS devices. If you find new issues, please let us know one of the following ways: File a bug Visit our ChromeOS communities General: Chromebook Help Community Beta Specific: ChromeOS Beta Help Community Report an issue or send feedback on Chrome Interested in switching channels? Find out how. Luis Menezes Google ChromeOS
Published 16 Sep 2026 · Source checked 26 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-71D64CDE79E43DAF
Hello Everyone! We've just released Chrome 154 (154.0.8037.49) for Android to a small percentage of users. It'll become available on Google Play over the next few days. You can find more details about early Stable releases here . This release includes stability and performance improvements. You can see a full list of the changes in the Git log . If you find a new issue, please let us know by filing a bug . Krishna Govind Google Chrome
Published 16 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-7BFA68BAC3BC4595
The Stable channel has been updated to 154.0.8037.44/.45 for Windows. as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log . You can find more details about early Stable releases here . Interested in switching release channels? Find out how here . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Srinivas Sista Google Chrome
Published 16 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-94AA242AB7FCD6E3
The Chrome team is excited to announce the promotion of Chrome 155 to the Beta channel for Windows, Mac and Linux. Chrome 155.0.8059.5 contains our usual under-the-hood performance and stability tweaks, but there are also some cool new features to explore - please head to the Chromium blog to learn more! A partial list of changes is available in the Git log . Interested in switching release channels? Find out how . If you find a new issue, please let us know by filing a bug . The community help forum is also a great place to reach out for help or learn about common issues. Chrome Release Team Google Chrome
Published 16 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-991CA8F988F3E745
Hi everyone! We've just released Chrome Beta 155 (155.0.8059.4) for Android. It's now available on Google Play . You can see a partial list of the changes in the Git log . For details on new features, check out the Chromium blog , and for details on web platform updates, check here . If you find a new issue, please let us know by filing a bug . Chrome Release Team Google Chrome
Published 16 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →GOOGLEGOOGLE-CHROME-A2AC816281776D16
The Stable channel is being updated to OS version 16765.49.0 (Browser version 152.0.7977.129 ) for most ChromeOS devices. If you find new issues, please let us know one of the following ways: File a bug Visit our ChromeOS communities General: Chromebook Help Community Beta Specific: ChromeOS Beta Help Community Report an issue or send feedback on Chrome Interested in switching channels? Find out how. Luis Menezes Google ChromeOS
Published 16 Sep 2026 · Source checked 28 Sep 2026
Release notes and known issues →