Friday’s 5 PM technology recap brings five developments with direct practical consequences: Google patched an actively exploited Chrome flaw, Rapid7 documented a backdoor hidden inside trojanized HAProxy builds, a reported DeepSeek order could create a huge Huawei inference cluster, U.S. military branches disabled advertising identifiers over location-tracking concerns, and NVIDIA confirmed that DLSS 5 is planned for RTX 40-series graphics cards.[1][3][6][8][9]
Reporting cutoff: September 4, 2026, 5:09:26 p.m. EDT (21:09:26 UTC). The Chrome exploitation is confirmed by Google, while the attacker and victim details remain undisclosed.[1] Rapid7’s findings concern compromised, recompiled software—not a newly disclosed HAProxy vulnerability.[3] The DeepSeek cluster remains an unnamed-source report that neither DeepSeek nor Huawei had publicly confirmed.[5][6] Military privacy changes reduce one tracking channel but do not make a device untrackable.[8] NVIDIA supplied no RTX 40 rollout date.[9]
Listen to the broadcast-ready recap
This KittenTTS Bella narration was synthesized locally from the same checked facts as the article.
Tonight’s five-story rundown
- Chrome fixes an actively exploited V8 type-confusion flaw.[1][2]
- Ted hides in trojanized HAProxy and Linux service binaries.[3][4]
- DeepSeek reportedly plans a 160,000-chip Huawei inference cluster.[5][6]
- Military branches turn off advertising identifiers amid location concerns.[7][8]
- NVIDIA plans DLSS 5 support for RTX 40-series GPUs.[9]
1. Update Chrome: Google confirms active exploitation [1]
Google’s September 3 Stable Channel Update moved Chrome to 152.0.7977.82/.83 on Windows and macOS and 152.0.7977.82 on Linux.[1] The release includes 12 security fixes and says Google is aware that an exploit for CVE-2026-85046 exists in the wild.[1]
Help Net Security identifies CVE-2026-85046 as a high-severity type-confusion flaw in Chrome’s V8 JavaScript engine.[2] A maliciously crafted page could execute code inside Chrome’s sandbox; that wording does not establish complete takeover of the operating system, which may require another exploit or a separate escape path.[2]
Practical action: open Chrome’s About page, let the update complete, restart the browser, and verify the version. Managed environments should confirm deployment data rather than assuming automatic updates reached every endpoint. Users of other Chromium-based browsers should check their own vendor advisories.
2. Ted backdoor shows why a matching version string is not enough [3]
Rapid7 reports finding a previously undocumented Linux backdoor called Ted inside trojanized HAProxy 2.8.12 binaries at two South Korean organizations.[3][4] The modified proxy could intercept traffic, inject selected web pages, run commands, and conceal command-and-control traffic from ordinary backend logs and HAProxy counters.[3][4]
The same investigation found modified service binaries including sshd, crond, agetty, atd, and polkitd.[3] This is not evidence of an HAProxy product vulnerability: the attackers already needed sufficient access to replace trusted binaries.[3] Rapid7 says the initial-access method and precise timeline remain unknown, and it attributes the activity to North Korean actors with medium confidence.[3]
Practical action: administrators should verify critical edge binaries against vendor or distribution package hashes, review package-manager history, inventory service-file changes, and investigate unexplained outbound traffic. If compromise is suspected, preserve evidence before reinstallation or credential rotation so the scope can be reconstructed.
3. DeepSeek’s reported Huawei cluster would be enormous—but it is still a plan [5][6]
Bloomberg reported that DeepSeek plans to deploy at least 160,000 Huawei Ascend 950DT accelerators in an Inner Mongolia data center.[5][6] The Decoder’s accessible summary says the chips would be used for inference rather than training, while DeepSeek would continue using NVIDIA hardware for heavier model-training workloads.[5][6]
If completed at the reported size, the project would be the largest known Huawei accelerator cluster.[6] The same reporting says production limits and memory shortages could prevent Huawei from filling the order for more than a year.[6]
Why it matters: a cluster this large would show how Chinese AI operators are separating inference from training and scaling around export-constrained supply chains.[5][6] It could also pressure power, networking, cooling, and high-bandwidth-memory availability.[6]
4. Military advertising-ID changes spotlight the wider location-data problem [8]
Reuters reports that the Air Force, Army, Navy, and U.S. Special Operations Command told Senator Ron Wyden that advertising identifiers had been disabled on at least some military phones and computers.[7][8] The Air Force said it made the change two months earlier; the Army said Windows advertising IDs had been blocked since before 2021 and disabled by default on Android and Apple devices since at least February 2026.[7][8]
Wyden and Representative Pat Harrigan asked the Pentagon to investigate whether it had adequately addressed the risk from commercially traded location data.[8] Privacy researcher Zach Edwards cautioned that turning off advertising IDs blocks one identifier, but applications, networks, and other device signals can still be combined to locate people.[8]
Local action: on managed phones, document which privacy controls are enforced and which remain user-controlled. For sensitive travel or field work, use a broader operational-security plan instead of treating one settings toggle as a complete defense.
5. NVIDIA says DLSS 5 will reach RTX 40 cards—later [9]
NVIDIA told The Verge that DLSS 5 will expand from RTX 50-series hardware to RTX 40-series GPUs after performance on RTX 50 cards is better optimized.[9] RTX 40 owners were not given a release date.[9]
The report says players will receive a basic on/off control, while detailed choices such as model selection, masking, structure, and tone intensity will remain in developers’ hands.[9] NVIDIA also declined to reconfirm the complete list of games previously announced for DLSS 5 support.[9]
Practical action: RTX 40 owners should wait for NVIDIA’s official driver and game integrations rather than installing leaked or unofficial ports. Once available, compare the feature on and off in each game because generated lighting and image changes may not match every player’s preference.
What to do next
- Everyone using Chrome: update, restart, and verify the installed version.
- Linux and edge administrators: validate critical binaries against trusted packages, not just version strings.
- AI infrastructure watchers: treat the DeepSeek cluster as reported planning until companies or physical deployment confirm it.
- Mobile-device owners and managers: disable advertising identifiers, then review location permissions and app inventory.
- RTX 40 gamers: wait for supported DLSS 5 releases and test visual quality per game.
Need help securing or improving your technology? Schedule The IT Guys
More from The IT Guys
Frequently asked questions
How do I know Chrome actually updated?
Open Chrome’s About page, let it check, restart when prompted, and verify the displayed build is 152.0.7977.82 or later on Linux, or 152.0.7977.82/.83 or later on Windows and macOS.[1]
Is HAProxy itself vulnerable to Ted?
Rapid7’s report describes trojanized HAProxy binaries installed after compromise, not a vulnerability in official HAProxy code. The distinction matters because patching alone does not remove a replaced binary or stolen credentials.[3]
Has DeepSeek already installed 160,000 Huawei chips?
No public evidence checked here establishes that. Bloomberg reported a plan, and delivery may take more than a year because of production and memory constraints.[5][6]
Does disabling an advertising ID stop all location tracking?
No. It closes one common linkage mechanism, but apps, network data, permissions, and other device signals can still expose location.[8]
Can RTX 40 owners use DLSS 5 now?
Not through a supported general release described in this report. NVIDIA confirmed future RTX 40 support but gave no date.[9]
Sources checked for this edition
- Chrome Releases — Stable Channel Update for Desktop — September 3, 2026.
- Help Net Security — Google patches actively exploited Chrome zero-day (CVE-2026-85046) — September 4, 2026, 12:09:13 UTC.
- Rapid7 — DPRK APTs: Ted backdoor and curlRAT target South Korean media and automotive sectors — September 4, 2026.
- The Hacker News — New Ted Backdoor Hides Inside Victims’ Own HAProxy Builds to Intercept Web Traffic — September 4, 2026, 20:21 IST.
- Bloomberg — DeepSeek Plans Big Huawei AI Chip Order to Power New Data Center — September 4, 2026; automated retrieval was blocked.
- The Decoder — Deepseek plans the largest known Huawei chip cluster with 160,000 processors in Inner Mongolia — September 4, 2026, 14:19:14 UTC.
- Reuters — US military turns off ad trackers on devices amid Middle East targeting reports — September 4, 2026.
- CNBC TV18 / Reuters — US military turns off ad trackers on devices amid Middle East targeting reports — September 4, 2026.
- The Verge — Nvidia will officially bring DLSS 5 to older GPUs — but won’t give gamers full control — September 4, 2026, 01:49:25 UTC.
Source state checked through September 4, 2026, 5:09:26 p.m. EDT / 21:09:26 UTC. Bloomberg and Reuters blocked automated full-page retrieval; those claims are labeled and paired with accessible reports or syndication. CNBC TV18 preserves Reuters reporting and is not independent corroboration.