Skip to content
senn-techsenn-tech
← IT News
Week 2026-W462026-11-09

IT News Wk 46: APT, GPU Prices, Home Assistant

APTCVE-2026-109518Memory crisisGPU pricesHome Assistant

This week the attack sits in the very tool we use to patch everything else: in APT, a package can be swapped after the signature check. Memory also stays the big topic. According to heise the RTX 5090 costs about 8,000 euros, Microsoft gives Windows 11 a memory diet for 8 GB devices, and forecasts for relief range from 2028 to 2030. In Home Assistant, 2026.11 removes the separate HACS. The labels mean: verified (two independent sources read), reported (one source read), vendor-claimed, or inferred (our reading).

Own measurements from 8 November are marked as such. They appear in the APT deep dive (Assessment section) and in the digest under Keycloak, Stalwart, Caddy and Docker; each paragraph states its date and, where available, host count and method.

Deep Dive: APT flaw CVE-2026-109518 and the package path

Ubuntu logo
Ubuntu and Debian disclosed and fixed the APT flaw on 4 November. (Quelle: Simple Icons 16.36.0, file ubuntu.svg (CC0), trademark: Canonical)

How the attack works

The discoverer, Max Justicz, found a bug in how APT handles HTTP redirects. According to the Debian announcement DSA-6607-1, APT can merge two different downloads when a redirect gives both the same address. On top of that, file handling is faulty when a download is resumed. An attacker can use this to replace a file after APT has checked it. According to Debian, this leads to code execution as root. Ubuntu stresses that the swap works even when the package would fail the signature check, and names a repeated download (Acquire::Retries) as a precondition. The attacker needs a position in the HTTP path (man-in-the-middle); according to linuxnews.de, visiting a web page is not enough. The rating is CVSS 4.0 at 7.7 (Ubuntu's figure). According to Ubuntu, snaps are not affected. Not established are the vulnerable upstream version ranges and any exploitation in the wild; we read nothing on either. Status: verified (Debian, Ubuntu, upstream changelog, Linuxiac, linuxnews.de).

Affected versions and fixed versions

Upstream, the fix is in APT 3.3.6 of 4 November; according to the changelog, the download methods now open their target files exclusively. The distributions ship these packages:

DistributionFixed version
Debian 13 (trixie)apt 3.0.4
Ubuntu 26.103.3.3ubuntu0.1
Ubuntu 26.04 LTS3.2.1ubuntu0.1
Ubuntu 24.04 LTS2.8.4ubuntu0.1
Ubuntu 22.04 LTS2.4.15ubuntu0.1

Ubuntu 20.04 and 18.04 get the fix only through ESM (Ubuntu Pro). According to the Ubuntu blog, releases from 22.04 on are affected by default, older ones only with a non-zero Acquire::Retries. The announcement says nothing about Debian 12; anyone running it checks the security tracker instead of assuming all is well. The fixed versions come from USN-8996-1 and the DSA. Status: vendor-claimed.

What to do now

Ubuntu recommends switching package sources from http:// to https://, which not every mirror supports, and fetching the update itself without retries: sudo apt update && sudo apt upgrade -o Acquire::Retries=0. To upgrade only APT, use sudo apt install -o Acquire::Retries=0 --only-upgrade '?source-package(^apt$)'. According to Ubuntu, unattended-upgrades pulls the fix within 24 hours. apt list --installed '?source-package(^apt$)' shows the current state. Inferred: a local HTTP cache or reverse proxy in front of the package sources (apt-cacher, Squid) sits in the network path and should be checked first. Proxmox hosts have a Debian base and belong in the check; whether your Proxmox repository runs over HTTPS is something we did not generalise.

Assessment: The flaw is a bug in the transport path, not in the signature check itself, and it needs a network position. Inferred, that makes it more serious for networks with their own mirror or proxy than for a server with direct HTTPS access. We measured our own fleet (8 November 2026, dpkg-query -W apt over SSH on four hosts): the two Ubuntu 26.04 hosts are on 3.2.1ubuntu0.1 and the two Debian 13 hosts on 3.0.4, which are the fixed versions in the table. Alpine hosts use apk and are not affected; for their own flaw this week see the link in the digest.


Deep Dive: Memory crisis, GPU prices and Windows on 8 GB

The RTX 5090 costs about 8,000 euros

heise reports on 2 November that the RTX 5080 is barely available under 2,000 euros (list price 2,099 euros) and rose by more than 30 percent in two weeks. The RTX 5090 reportedly costs about 8,000 euros, against around 6,000 euros in mid-October. The RTX Pro 6000 with 96 GB starts at about 16,500 euros, the Pro 5000 card with 48 GB only from 8,000 euros. According to heise, Nvidia says only that the 5090 will keep shipping and does not confirm ongoing production. heise names the AI boom, scarce GDDR7 memory and the fact that the same chips earn more as a workstation card as causes. A date in January 2027 is circulating for a 24 GB version of the 5080; heise writes that nothing may come of it this time. For context there is an older PCGH calculation from 6 October: it puts the 32 GiB of GDDR7 at about 275 euros and a markup with no cost item behind it of about 2,900 euros net. According to PCGH, the calculation rests on public cost estimates and customary industry margins. We could not read a second source for the current prices, because the counter-articles sat behind a consent prompt or a block. Status: reported.

Windows 11 on 8 GB PCs: Microsoft saves memory in the system

On 3 November Microsoft described improvements for 8 GB devices in the Windows Experience Blog, shipped with build 26300.9818 (version 26H2). According to Microsoft, startup, search, Settings and Explorer respond up to 20 percent faster than in the January 2026 state, and multitasking up to 40 percent faster (measured on an HP OmniBook 3 with 8 GB). Up to 2 GB more active data stays in RAM instead of being paged out, and the committed memory growth drops by up to 900 MB. Widgets load only when opened, inactive Edge tabs sleep after 15 minutes instead of two hours, and Teams starts in efficiency mode on 8 GB PCs. To use it, turn on "Get the latest updates as soon as they're available" under Settings > Windows Update and update Edge, Microsoft 365 and Teams as well. pureinfotech and windowspro.de confirm the changes; Dr. Windows is sceptical and headlines its piece "Microsoft pulls off a marketing stunt". The percentages are lab figures from Microsoft and not independently checked. pureinfotech and Born name the KB number KB5127936; the Microsoft article names none. Status: verified for the changes, vendor-claimed for the percentages.

How long the shortage will last

heise writes on 5 November that Sam Altman softened his criticism of privately used DRAM after pushback on X. On the duration of the shortage, the article gives at least the coming year; SK Hynix considers bottlenecks possible until 2030, Gartner and Counterpoint see relief in 2028 at the earliest. Those are analyst figures we read only through heise. One consequence is shown by heise/c't on 6 November: according to TrendForce, three to four percent of all smartphones in 2026 contain refurbished memory chips, and in 2027 it could be seven to nine percent, mostly in cheap LTE devices. For hard drives, noted.lol calculates with data from a single retailer (eRacks): the price per terabyte rose between March and August by 66 percent for the WD Red Pro and by 55 percent for the IronWolf Pro. That is an opinion piece in dollars, not a market index. Status: reported.

Assessment: Anyone running their own GPU hosts is buying at the worst possible time right now, and the prices give no reason to hurry: a retail price can jump by a third in two weeks and come back just as fast. Before buying, measure how much VRAM the existing cards really use. Inferred from the heise prices: a Pro 5000 with 48 GB costs as much as a 5090 with 32 GB, and a Pro 6000 with 96 GB as much as two of them; we did not compare bandwidth or performance. For Windows fleets with 8 GB devices, the update switch is cheaper than new memory, but the figures come from Microsoft, so a test on one of your own devices before the rollout is still needed.


Deep Dive: Home Assistant 2026.11 replaces HACS

Home Assistant mark
Home Assistant 2026.11 of 4 November brings a built-in Marketplace and new entity names. (Quelle: Simple Icons 16.36.0, file homeassistant.svg (CC0), trademark: Home Assistant)

Marketplace instead of a separate HACS

Home Assistant released version 2026.11 on 4 November. According to the release notes, community integrations, dashboard cards, themes and templates are now installed under Settings > Marketplace; an integration needs no restart for this. A separate HACS installation is no longer possible on 2026.11, and the old HACS gets no new versions. Matter Alpha described the plans as early as 2 October: existing HACS installations are taken over automatically on first start, custom repositories, update entities and dashboard resources stay, and the old HACS is removed. Browsing, installing and updating work without a GitHub account; only custom repositories need a GitHub connection. Home Assistant still does not test or support the community content; a warning appears before installing or updating. In the GitHub project, users are already reporting problems with the takeover, for example that many integrations formerly installed through HACS appear as "not loaded" (issue 190450) or that the GitHub rate limit kicks in at startup (issue 191046). We read only the titles of those issues. Status: verified (release notes and an independent report, though the report predates the release); the migration problems are reported.

Entity names: a backward-incompatible change

Entities now have a single name, and Home Assistant adds device and area names only where they are needed. The project explicitly calls the change not backward compatible. Cards without their own name show the device name followed by the entity name, so some dashboards look different after the update. The friendly_name attribute is slated for deprecation; templates should use entity_name(), device_name() and area_name(). Further breaking changes according to the release notes: Z-Wave needs zwave-js-server 3.11.0 or newer, MQTT entities without a unique_id no longer create devices, and Uptime Kuma is supported only from version 2.0. Status: vendor-claimed, one source read. We have not tested the changes on an instance of our own.

Matter cameras, LoRaWAN and Green Power

According to the release notes there are also Matter 1.5 cameras with live video over WebRTC and a Labs preview of two-way audio with a push-to-talk button for Matter and Reolink cameras. LoRaWAN runs through ChirpStack and The Things Network, and the Zigbee integration supports battery-free Green Power devices such as the Friends of Hue switches. Backups and media can be stored on internal or USB drives. Automations and scripts can exclude entities, devices, areas, floors or labels from a target. The page lists 38 new integrations. According to the release notes, the Flipr integration is removed because the company was liquidated. Status: vendor-claimed.

Assessment: For running installations, two things need checking before the update: templates and automations that read friendly_name, and templates that refer to the HACS integration (the project's documentation has the migration details). A backup and a trial run on a copy cost little. The Marketplace changes nothing about the stance on community code: it becomes more convenient to install, but it is still not vetted.


Digest: Other important news

Label at the end of each line: verified (two sources read), reported (one source read), vendor-claimed (figure comes from the vendor).

Security

  • OpenSSH "sshole", CVE-2026-123158: password bypass on Alpine and other musl systems Affected is OpenSSH before 10.6p2 on musl systems without PAM, meaning Alpine, OpenWrt, Buildroot and Yocto: accounts with * in the password field accept passwords of 257 to 1,024 characters. Help Net Security reports exploitation, SecurityWeek confirms the fix in 10.6p2 but writes that no exploitation has been reported so far; the sources contradict each other. We published our fleet check of 36 hosts separately this week. | reported
  • Keycloak 26.8.2: Elestio counts 33 flaws with a CVE The release page lists entries with CVE numbers under "Security fixes", among them a signature-check bypass on the SAML redirect, an account takeover through a login race, session takeover via a forged id_token_hint and stored XSS on the login page; it gives no total. Elestio speaks of 33 CVE entries in one patch release and names four individually: CVE-2026-117691 (SAML redirect), CVE-2026-103112 (login race), CVE-2026-107889 (XSS on the login page) and CVE-2026-110931 (SAML denial of service). Of our two Keycloak instances, both are below 26.8.2 on 8 November, so the update is pending. | vendor-claimed
  • SonicWall SonicOS: SAML bypass in the SSL VPN is in the CISA KEV list CVE-2026-19868 (CVSS 7.1) affects Gen7 with SonicOS 7.3.3-7015 and older and Gen8 with 8.2.2-8015 and older; the fixes are 7.3.4-7013 and 8.2.3-8015, and only an active SAML login is attackable. For the GMS manager (end of life), SonicWall will not fix two other flaws, writes SecurityWeek. The CISA KEV deadline ends on 20 November. We did not open the catalog itself. | reported
  • WordPress core, CVE-2026-119977 WordPress 4.7 to 7.1.3 is affected, and 7.1.4 fixes it. That the flaw is in the CISA KEV list is stated by Elestio, not by borncity. Our sites run on Kirby and Next.js and are not affected. | verified
  • Barracuda Email Security Gateway: auth bypass and root commands CVE-2026-116606 (CVSS 9.3, firmware before 9.4.0.030) and CVE-2026-111560 (CVSS 8.6) can be chained to root; according to the report the second also affects Load Balancer ADC, Message Archiver and other products from the company. Exploitation is not reported. | reported
  • rsync 3.5.2: denial of service through weak checksums CVE-2026-119741: a malicious receiver can force the sender to compute a disproportionate number of strong checksums; the release limits the effort. Linuxiac confirms this, and neither source names the affected version ranges. Relevant for backup scripts that run against third-party receivers. | verified

Hardware

AI and development

  • OpenAI: 1,724 confirmed kernel bugs, 1,169 root exploits Autonomous agents searched the kernel mainline in October: 2,308 suspected cases, 1,724 confirmed, 1,169 local root exploits, cost about 1.2 million dollars. The sources describe the 948 differently: SecurityWeek relays OpenAI's statement that they are separate patches; Help Net Security counts 1,169 root exploits that, after grouping those with the same cause, come to 948 distinct vulnerabilities. What exactly the number counts is therefore not settled. All figures come from OpenAI. As a countermeasure the reports name isolation, for example with Firecracker or gVisor. | reported
  • vLLM 0.33.0: stable ABI for CUDA wheels Since version 0.33.0 the CUDA wheels are supposed to be ABI-stable against libtorch; the project shows a switch from torch 2.14.1 to 2.15.0 without rebuilding vLLM, so far only on a development build and only for CUDA. The blog itself warns to check further dependencies. We found no independent evidence. Inferred: keep the container pin on the tested combination and try a torch switch only in a test container. For the end of CUDA 12.9 see our post. | vendor-claimed
  • Kinference: a control plane in front of vLLM The open-source project (Apache 2.0) distributes requests by queue and KV cache contents and limits token rates and costs per tenant. Cloud Native Now reports on the same day. It requires Kubernetes, and the Helm charts only run with --devel. For a single host with LiteLLM you do not need it (inferred). | vendor-claimed
  • Kimi K3.1 Pro with day-0 support in vLLM About 2.8 trillion parameters, 104 billion active, 1 million context, MXFP4 weights; the examples run on GB300, MI355X and TPU v7x. The model does not fit on a host with 128 GB of VRAM (inferred). | vendor-claimed
  • Anthropic Message Threads (public beta) Instead of resending the whole history, only changes go to the API; according to Anthropic, time to first token drops by about 35 percent at 500,000 to one million tokens. The thread is held encrypted in memory and expires after five minutes of inactivity. | vendor-claimed
  • Anthropic FlashProve under Apache 2.0 A prototype with EPFL, MIT and StarkWare that cryptographically proves a specific model produced a specific answer, without revealing the weights. Tested with Llama 4 Maverick: the proof for 1,024 tokens is about 18.78 MB, and verification takes about 17 seconds on 24 CPU threads. | reported

Software releases

  • Open WebUI 0.13.0 A schema migration (back up first; with several workers, update all instances at the same time) and security fixes, plus a tab workspace, side chats and MCP apps in chat. The limit for tool calls rises from 256 to 1,024. | vendor-claimed

  • Stalwart 1.0.3 Blobs can be encrypted at rest, new OAuth scopes, IMAP SEARCH with up to 32 levels. The first start after the update needs a one-time restart with STALWART_UPDATE_ROLE_PERMISSIONS=true. We run 1.0.2 (as of 8 November). | vendor-claimed

  • LiteLLM 1.108.0 (LTS) Entra ID on all Azure Foundry routes, shared budgets for model groups and two breaking changes (prompt_token_calculator is removed, Cerebras parameters). We inferred the security fixes from the PR titles only. We read half of the notes. | vendor-claimed

  • Fedora 45 and openSUSE Leap 16.1 Fedora 45 brings kernel 7.2, GNOME 51 and RPM signature checking on by default. Leap 16.1 is based on SLES 16.1 with kernel 6.12 LTS and a new immutable mode with a snapshot per update. | reported

  • Ollama 0.40.15 Parallel requests for recurrent and vision GGUF models, YaRN long context for Qwen3 and the MiMo V2.6 model with 9 billion parameters. The release date is inconsistent (3 or 6 November), hence "this week". | vendor-claimed

  • Caddy 2.11.8 and 2.11.9: five security advisories on file_server, php_fastcgi and root with All five GitHub advisories of 4 November are fixed in 2.11.8, and one is rated high (GHSA-r766-rf9f-588h, the precondition is a root taken from {host}). Version 2.11.9 fixes a regression from 2.11.8 and further security issues, mainly in FastCGI, and brings breaking changes for FastCGI; anyone running php_fastcgi should plan for 2.11.9 right away. A Caddy that only does reverse_proxy does not meet the preconditions, by our reading: in the Caddyfile of our gateway, grep -c on 8 November counted 0 hits each for file_server, try_files, php_fastcgi, root and on_demand; {host} appears 8 times, but in no root. Details and a check command are in the post. | reported

  • Docker Engine 29.9.3 and BuildKit 0.34.2 The release of 3 November fixes four CVEs. For two of them the GitHub advisories are available: CVE-2026-116587 (go-jose, high CPU load when parsing crafted RSA keys, denial of service, rated high, CVSS 3.1: 7.5) and CVE-2026-116591 (klauspost zstd library, crash on crafted data, rated high, CVSS 4.0: 8.7). Two Swarm advisories come on top: CVE-2026-115538 (overlay encryption after firewalld flushes Docker's iptables rules) and CVE-2026-115539 (certificates after a leader change). No ratings are available to us for those; their GitHub advisory pages (GHSA-6jhp-7446-hf7f, GHSA-628g-hv7f-pgjc) returned 404 on 8 November. A single host without Swarm is not affected by them, judging by the titles (inferred). BuildKit 0.34.2 closes two more advisories that have no CVE number. On 8 November we ran docker version on five Docker hosts: versions range from 26.1.5 to 29.8.0, and none is on 29.9.3 yet. | vendor-claimed

  • PostgreSQL 19: release moved to 19 November RC1 came out on 15 October, RC2 is planned for 12 November, and the release for 19 November if nothing intervenes. That is what the RC1 announcement says; the release team's mail from Jonathan Katz of 10 October gives the reason as the many fixes in the stable branches, which RC2 is meant to pick up before the release. The roadmap page still says October and is out of date. The next minor release of the supported versions also arrives on 12 November. | vendor-claimed

  • Ceph Tentacle 20.2.5 According to the release notes, the release of 2 November hardens the checking of CephX service tickets ("hardened service ticket verification"); for this change the notes name no CVE number of their own. The same page warns: upgrades from Squid 19.2.6 to Tentacle versions before 20.2.4 may fail, daemons older than 20.2.4 do not start, and if only the managers are upgraded the way out is to redeploy them with the old image. Anyone coming from 19.2.6 should therefore not go to a version before 20.2.4. | vendor-claimed

Windows

  • KB5127936 is supposed to fix the RDP error 0xC000000D The optional preview update is supposed to fix a regression since KB5124010 (Born could not confirm this) in which non-administrators with administrator protection enabled could not sign in over Remote Desktop; it rolls out with Patch Tuesday on 10 November. Relevant for terminal servers. | reported
  • Why Task Manager hangs under load When the CPU is short, all processes suffer, and a higher priority does not help with waits on locks. As a workaround the article names Ctrl+Alt+Del, because that desktop runs protected. | reported

Smart home

  • Fritz!Smart Energy 201: DECT socket with consumption metering for 49 euros Up to 3,680 watts, standby below 0.2 watts, a Fritzbox with a DECT base is required. For connecting to other systems, heise names the FritzSmart Gateway or the Matter bridge of the Fritzbox 5690 Pro, which so far runs only on lab firmware. AVM's primary page was not reachable. | reported
  • evcc 0.319.0 with breaking changes The release of 8 November changes the Huawei SmartLogger integration (battery removed, curtailment as separate devices), the optimizer's behaviour for the home battery when charging with PV surplus, and the login to Volvo Connected (now OAuth2). New is EEBus for Buderus and Bosch heat pumps. SmarthomeAssistent also reports the heat pump integration, the article describes it in detail: it needs a Buderus MX400 gateway or Bosch K40 RF with OHPCF, and only the Buderus WLW186i MB AR is practically confirmed. | vendor-claimed
  • Eve Thermo 5th generation tested From 72.99 euros, Matter over Thread, local with no cloud or account. The Eve Thermo Control room sensor can be linked through Matter binding, also from Home Assistant with the "Matter Binding Helper" add-on. The test names schedules only with iOS or Google Home, and the price, as drawbacks. We did not read the rating or grade. | reported

From the blog

Published this week:

Sources for this edition

Compiled on Monday, 9 November 2026. Sources: see above. Anything that arrives after that goes into the next edition.