Two layers: the week's news and what it means in our own operation. Everything fetched again on 20 September 2026, two claims from last week now stand right.

Deep dive: The CRA clock running, the NISG form arriving later

Correction: the form exists, just not before 1 October

Last week we wrote that Austria's registration portal does not exist. Outdated. The Company Service Portal has announced since 08 September 2026 that the application "NIS 2 Services" goes online in the USP as the NISG 2026 takes force on 1 October 2026, for registration and incident reports, deadline "initially by 1 January 2027". The same day the site of the new Federal Office for Cybersecurity goes live at the interior ministry, the agendas sit there and at the BMI, not at the RTR, whose old NISG page returns 404. The WKO FAQ names the same window, 1 October to 31 December 2026, plus the fields from § 29 para. 2. Binding remains BGBl. I Nr. 94/2025, two-tier thresholds, 50 employees or EUR 10m turnover and balance sheet total, in a group the association counts, fines from EUR 50,000 for registration breaches to EUR 7m or 1.4 per cent of group turnover.

The portal is a date, the preparation is work. The fourth line is the one most often missing on 1 October. Both duties end at the managing director, and who clarifies size, sector and group affiliation before October keeps a three-month buffer. (Quelle: NISG 2026, BGBl. I Nr. 94/2025; USP announcement of 08.09.2026; WKO NIS-FAQ)

The Cyber Resilience Act reporting duties apply since 11 September 2026, early warning within 24 hours, full notification within 72, final report 14 days after a corrective measure is available, over the ENISA platform. No new clarification of who counts as a manufacturer came from the Commission or ENISA this week. The clock starts with knowledge of the exploitation, played through in the CRA reporting manual. Germany is further, the NIS2UmsuCG applies there since 6 December 2025 with around 29,500 entities, the BSI portal stood live on 6 January 2026.

Assessment: Both duties end at the same table, at the managing director.

Deadlines per statute and authority descriptions, as of September 17, 2026 (source: European Commission, CRA reporting)

Deep dive: The gap without a CVE number, and our own endpoint

The advisory GHSA-2xp9-vwfh-vxw4 of 8 September 2026 describes unauthenticated remote code execution over AVIF files in the image optimization API, root cause libheif, reached through sharp. Affected: >= 10.0.0 below 15.5.24, >= 16.0.0 below 16.3.3. No CVE number on the entry, so scanners working off CVE lists miss it, and AVIF optimization stays disabled only while the fix is missing, a state and not a patch.

The entry point is a route that sits in the build, whether or not anyone uses it. Both gaps disappear through structure: an endpoint check in the build pipeline, error isolation in the patch run. (Quelle: GitHub Advisory GHSA-2xp9-vwfh-vxw4, 08.09.2026)

CVE-2026-75604 is older and narrower, NVD 9.0, published 1 September 2026: Windows hosts without Cache Components mask backslashes in route segments inconsistently, one remote request can leave the cache directory and expose build data including the server manifest key. Fixed in 15.5.24 and 16.3.3, afterwards rotate the NEXT_SERVER_ACTIONS_ENCRYPTION_KEY.

The test bench was our own site, measured on the version in the build directory, next 16.2.12, right in the affected span. The endpoint answered instead of refusing, /_next/image returned 200 with image/png for a real asset, although next/image is nowhere in use. The route does not ask about use. This edition appears after a rebuild above 16.3.3, framed in the Next.js post.

Operations, same week: one host ended the nightly patch run with apt exit 100, 19 packages open, 5 of them security updates. The queue behind it was not empty but unprocessed, every host behind that position got neither patches nor CVE comparison, logged as a terse "failed". A second node stayed blind across 13 runs, a changed host key let the CVE watcher abort, correct behaviour that ended as a footnote in the log. Both changed in the patch-run post and the patch management frame.

Assessment: The image optimizer gap was one patch release away, the blind night a formatting problem in the run itself.

Deep dive: Jev, a decision model without chat, on our GPUs

On 15 September 2026 TypeSafe AI presented Jev as the first "System One Model". Neither chat nor reasoning, the model returns no sentences but typed decisions, a Choice of at most 255 options, a score, a noun, each with a probability. Access: a hosted US API with a waitlist, no open weights. The vendor numbers are aggressive, 0.042 USD per million input tokens, output free, 70 to 500 ms, on the front page 193.6 times faster and 444.6 times cheaper. Heavier than those numbers: the evaluation reference is agreement with GPT-6 Astra and Claude Fable 5.1, agreement rather than correctness.

Two orders of magnitude lie between advertised and measured. The counter-measurement comes from early access, it is a single finding, but a traceable one. For an operation with its own inference chain the answer is a pilot on own GPUs, not a US contract. (Quelle: TypeSafe AI (own claim) against the Lindfors counter-measurement, 18.09.2026)

The counter-calculation came from Lindfors on 18 September 2026 over 24 Norwegian documents. On the stance decision Jev ties at 20 of 24 with DeepSeek V4.1 Flash without reasoning, only the score task wins clearly, and real costs lay at one sixth to one fourteenth of the reference, not 1/445. Good Start Labs measured 86 to 92 per cent agreement with five other models on 6,003 checks, the models among themselves 88 to 95 per cent, Hacker News at 1,909 points and some 500 comments.

For us the frame decides before the performance: no EU region, no self-hosting, no weights, so Jev is unusable today for personal and NIS2-relevant data, and no LiteLLM provider exists. The contract is rebuildable in-house with the Python adapter on own vLLM endpoints, and the jaggedness page itself lists what fails, no counting, no date sequences, adversarial content can move the answer.

Assessment: Jev is a classifying switch with a probability, measurably cheap for routing and triage.

Deep dive: TrueNAS plugin, the HA fix is in the .deb, not in APT

Two days after our plugin post, v2.1.23-beta4 appeared on 19 September 2026 at 03:11 UTC. We read the postinst of the tag, it now restarts pvedaemon pveproxy pvestatd pve-ha-crm pve-ha-lrm and knows an escape with TRUENAS_PLUGIN_NO_RESTART=1. The issue #100 fix is now inside the package, and iXsystems marks this release itself as prerelease, the three betas before it were not.

The catch is the route the documentation shows. Counted again on 20 September, install.sh holds no pve-ha restart anywhere in main, alpha and beta4, and the signed APT repo still serves 2.1.17+deb1 of 1 July 2026. Whoever installs per the guide through APT has issue #100 unchanged, twelve weeks behind. The docs page still shows api_host, its footer names 26 March 2026 as last change, and the warning stands verbatim, "Do not use in production workloads". Open on 20 September: 46 issues, 87 per cent of posts from one person.

The integration runs over the Proxmox interface, the package is delivered by iXsystems. (Quelle: Proxmox Server Solutions GmbH, Wikimedia Commons, Public Domain)

Identical software, three delivery paths, different state, whoever follows the docs takes the oldest. On our inventory it stays a test bench, one TrueNAS owns every Zvol, replication the plugin does not know, shared storage stays LINSTOR/DRBD. What is won is a rule: after every custom storage backend, restart pve-ha-crm and pve-ha-lrm and test before the emergency comes. (Quelle: GitHub: tag v2.1.23-beta4 postinst, install.sh, APT Release of 01.07.2026, all fetched on 20.09.2026)

Digest: More news that matters

Security and operations

Three kernel gaps in the KEV, due 21 September: CVE-2025-39964, CVE-2026-53266 and CVE-2025-39682 added as actively exploited on 18 September. Local privilege escalation on a hypervisor host lifts guest isolation, unprivileged user namespaces as entry are standard on container hosts. No Proxmox advisory, the announcements end at 2 September, a Debian kernel topic.
Grafana, RCE unpacking plugins, still no fix: CVE-2026-15815, high, published 17 September. Prepared archives chain relative symlinks out of the plugin directory, unpacked before the signature check, and the advisory names no patched version, CERT-Bund. No update call but a lever, GF_INSTALL_PLUGINS empty.
Nextcloud, RCE through the preview: high, published 17 September, without a CVE, the path runs over the preview of corrupt files in Imagick. Recommended 32.0.13, 33.0.7 and 34.0.2, equivalents: Imagick out of PHP, enable_previews false.
n8n, 15 advisories of 16 September: fixed in 2.39.6, 2.40.1 and 1.123.80. CVE-2026-92587 hits our exact configuration, a git node with a relative URL against a forge, workaround n8n-nodes-base.git in NODES_EXCLUDE, as in the n8n post.
Unbound, critical heap overflow, Alpine old: CVE-2026-81642 of 16 September, affected up to and including 1.26.0, fix 1.26.1 the same day. Alpine 3.23 packages 1.25.2-r0, 1.26.1 only in edge. A resolver built at night from alpine:latest delivers that version, regardless of source pinning.
Caddy, placeholder injection in rewrite, fixed in 2.11.4: CVE-2026-77281, medium, published 18 September, affected up to 2.11.3. A rewrite URI ending in a literal question mark lets attacker-controlled substitutions run a second placeholder expansion. Broader than our Caddyfile post: secrets in expandable environment variables are the exposed surface.
Windows 11, domain devices locked out below Server 2025: from KB5124008 Windows takes Machine Identity Isolation into account, without enforcing it, yet devices with the feature enabled below that domain functional level lose interactive sign-in. The remedy, registry values from 2 to 0, restart, then Test-ComputerSecureChannel -Repair, is on that page.
CrowdSec, 170 private repos copied over an old access: the attacker used the still-open GitHub access of someone who left in May, his device compromised through prepared npm packages from TanStack. One endpoint, one forgotten access, with us the Gitea check at offboarding.

Models and inference

No major lab brought open weights this week: DeepSeek, Qwen, Mistral, Meta, Zhipu, Moonshot, MiniMax, Google, Microsoft and Cohere, searched through the API for files created between 14 and 19 September, give an empty set. The week belongs to NVIDIA, NVFP4 builds of foreign architectures, that is a correction of last week, the MIT build of DeepSeek V4.1 Flash came openly on 16 September, not gated, on 14 September GLM-5.3-NVFP4 followed.
Ternary-Bonsai-2-27B is the download of the week: ternary weights on Qwen3.8-27B, Apache-2.0, created 16 September, 1.5 million downloads in 30 days. The card claims 1.72 bits per weight, not measured by us, the path over llama.cpp.
vLLM, no stable release, SM120 fix open: newest stable stays v0.29.0 of 9 September, in the window only v0.30.0rc2. Issue #57156 and PR #57158 stay open, DeepSeek V4.1 on RTX-5090 class a build project. The advisories in the window, CVE-2026-57173 and CVE-2026-69147, are fixed in 0.24.0 and 0.28.0, so no new exposure.
LiteLLM, hardening in stable, two channels disagree: last week put the MCP-OAuth hardening in the RC line, too narrow, it is in v1.101.0 of 15 September. Since this morning PyPI serves 1.102.0, uploaded 04:41 UTC, while GitHub releases stand at 1.101.0 with no release object for 1.102.0. Rule: pin versions to releases, not to tags, details in the gateway audit.

Infrastructure and storage

Proxmox VE 9.2.20 upstream, not in the apt channels: the changelog on master opens with 9.2.20 of 11 September, the channels still say 9.2.11, our production cluster reports 9.2.11. No CVE list for Proxmox from us this week, we read none, and Proxmox VE 8 is at its end since 31 August 2026 per endoflife.date.
VMware ESXi 9.0 is not a future date, it is 15 months old: the circulating October 2026 target misses the facts. VCF 9.0 with ESXi, vCenter and NSX in 9.0 has been downloadable for licence holders since 19 June 2025, Broadcom confirms the delivery, the release notes list the changes, the ticker page carrying that October date returns 404. Nothing shifts for the move to Proxmox, vVOL is deprecated in 9.0.

Hardware

RTX Pro 5500 Blackwell, 84 GB, no price, no delivery date: the product page is online as of 20 September, reads "Coming Soon" and names the specs preliminary. ComputerBase confirms the 21,760 FP32 units on GB202 and the dual blower cooler, PNY confirms 1,398 GB/s, Geizhals carries the card since 14 September with 0 offers in Germany and Austria. No Austrian street price, no independent token measurements, the card is six days old, recalculated in the comparison post.

Same core count, different ceiling, 1,398 against 1,792 GB/s are 78 per cent of bandwidth with 84 against 32 GB of VRAM. Capacity is paid for with bandwidth, not with compute, and without a delivery date it stays a calculation. (Quelle: NVIDIA product data, RTX Pro 5500 marked as preliminary)

The next genuinely measured data point on the Blackwell Pro class, by Gamers Nexus on 24 June 2025, thermals, noise and LLM runs on the RTX PRO 6000. Explicitly not the Pro 5500, which was not on the market at that test.

RTX 5090, no first-party stock, listings up to 9,500 USD: Tom's Hardware finds no offer from the platforms themselves at Amazon and Newegg, PCGH counts on 15 September an Asus TUF from 6,395 USD at a marketplace seller against 4,299 USD median in June and 5,249 EUR at the cheapest dealer here, ComputerBase lies above 6,000 EUR in the median of newly listed German offers, in Austria 5,849 EUR for a ROG Astral in the Geizhals. Listings, not transactions, marketplace accounts with 81 per cent positive ratings. The GeForce licence still says "No Datacenter Deployment" from December 2017, and the RTX Pro 5500 aims there.
Memory prices, the curve points up: 3dcenter laid the September index for German end-customer prices, template the TrendForce line of plus 12 to 15 per cent on conventional DRAM in the fourth quarter.

Compliance and business

Mainstream support for Windows Server 2022 ends 14 October 2026, extended support to 15 October 2031.

Sources for this edition

Primary sources first, then the framing. We called every address ourselves on 20 September 2026.

Unternehmensserviceportal, NIS-2 implementation starts: entry into force 1 October 2026, application "NIS 2 Services", registration initially by 1 January 2027.
WKO, NIS FAQ: window 1 October to 31 December 2026, fields per § 29 para. 2, no exception for financial companies.
RIS, BGBl. I Nr. 94/2025: the Austrian NISG in the authentic federal law gazette.
ENISA, Single Reporting Platform, CRA guidelines of the Commission and the CRA policy page as of 15 September 2026.
BSI on the NIS2UmsuCG, the BSI portal and the press overview of the BSI.
Next.js Advisory GHSA-2xp9-vwfh-vxw4: AVIF path over libheif, fixes 15.5.24 and 16.3.3, AVIF optimization temporarily disabled, no CVE.
NVD, CVE-2026-75604: Windows path traversal, 9.0, published 1 September 2026.
TypeSafe AI, Jev announcement, evaluation page, Choice primitive, jaggedness docs, Python adapter and open-jev DeBERTa.
Lindfors, a first look at Jev, Good Start Labs and Hacker News: counter-measurements and objections on method.
TrueNAS plugin, release beta4, postinst of the tag, APT Release, install.sh and the plugin docs.
Proxmox git, pve-manager changelog, the forum announcements and endoflife.date Proxmox VE.
CISA KEV: the seven additions from 14 to 18 September 2026, kernel deadline 21 September 2026.
Grafana GHSA-xp8x-3q7w-cpqr, CERT-Bund WID-SEC-2026-3450, Nextcloud GHSA-7hwf-8pcj-33h4, n8n advisories, n8n GHSA-fm93-2x43-6676, Caddy GHSA-j8px-rmrx-76h9 and the Unbound advisories.
vLLM releases, issue #57156, PR #57158, CVE-2026-57173 and CVE-2026-69147.
LiteLLM v1.101.0, PyPI litellm, LiteLLM SSRF CVE-2026-59823.
NVIDIA NVFP4 DeepSeek V4.1 Flash, GLM-5.3-NVFP4, Ternary-Bonsai-2-27B and DeepSeek V4.1 Flash.
NVIDIA RTX Pro 5500, PNY RTX Pro 5500, Tom's Hardware, PCGH, ComputerBase, Geizhals, listed since 14 September without a price and the NVIDIA GeForce license.
heise, VMware Cloud Foundation 9 is here, Broadcom on the delivery and the VCF 9.0 release notes: downloadable for licence holders since 19 June 2025.
Gamers Nexus, RTX PRO 6000 tear-down of 24 June 2025 and Data Science in your pocket, Pro 5500 of 14 September 2026.
Windows 11 25H2 release health, lifecycle Windows Server 2022, CrowdSec, Air Security Plugin4Shell, Claude Code fix.
Alpine package page unbound, TrueNAS version notes, it-daily DRAM, 3dcenter memory index, watchlist-internet scam calls, watchlist-internet WhatsApp.
Proxmox logo, Wikimedia Commons: Public Domain, provided by Proxmox Server Solutions GmbH.

What we could not substantiate, and therefore do not write as fact: a price, a delivery date and a CUDA core count from NVIDIA itself for the RTX Pro 5500, the page names everything preliminary and the dealer lists in Germany and Austria were empty on 20 September; any independent token measurement on this card; the architecture, the parameter count and the training data of Jev, the 200 times figures have been reproduced by nobody, and what was measured was Norwegian, not German; the Forbes report on the valuation, the page was not reachable for our fetch; the subprocessor list of TypeSafe, it is loaded by script; an NVD score for the Unbound CVE-2026-81642, the entry stood at publication on "Awaiting Analysis"; full texts from TechPowerUp, VideoCardz and pcwelt, which refused us on all three; a statement by NVIDIA on the supply situation of the RTX 5090; and a Proxmox advisory for this week, there is none, the kernel gaps belong to the Debian kernel of the hosts.

From the blog

NISG 2026, registration by 31 December 2026: thresholds, sectors, fines, deadlines to 31 December.
CRA reporting duty in 24 hours: the deadlines from Article 71, the reporting chain via ENISA, and the question of when a finished product turns its maker into a manufacturer.
The image optimizer gap in Next.js: two gaps, one without a CVE number, measured on our own endpoint.
One host with apt exit 100 stopped the patch run: an abort in the middle of the list, one blind node across thirteen runs, two metrics against it.
LiteLLM gateway, the update at the gateway: what a proxy update says about the AI chain.
RTX Pro 5500 against RTX 5090: the same GB202 silicon, 22 per cent less bandwidth, and what runs empty first.
TrueNAS as storage for Proxmox VE: the source code behind the announcement, pulled again as of 20 September 2026.
Patch management in the Mittelstand: the frame for several reports in this edition.

Compiled on 20 September 2026, as of 07:00 CEST, with own measurement on the site and in operations, all sources in the block above.

IT News Week 38/2026: NISG form from 1 October, the decision model Jev, the TrueNAS fix in the .deb