CUTSIGNcutting for sign — daily OSINT threat read

2026-11-02

30 stories analyzed · 4 deep reads · brief: “[PIPELINE] Cyber Threat Brief — 2026-11-02”

received 2026-11-02 12:13Z · emailed 2026-11-02 12:49Z

24
new IoCs
50
novel behaviors
6
story updates
9
watch devs 48h
10
verdict cards
× closeNew IoCs (24) — by story
× closeNovel behaviors (50) — by story
× closeStory updates (6) — developments of earlier briefs' stories

↓ Jump to brief cards

Today: 30 stories in the brief, 6 high-priority. Top story: Teams help-desk impersonation leads to Quick Assist access and AD CS ESC1/ESC8 abuse, data exfiltration. 6 are developments of stories already being tracked. 5 tracked stories escalated in the last 48 h.

Developments on tracked stories (48 h)

Hackers actively exploit SSHole OpenSSH flaw (CVE-2026-123158) to gain root on Linux systems, confirmed by CISA KEV listing · 3 developments
  • 2026-11-09 17:10Z GreyNoise recorded 16 successful exploitation chains from six IPs with post-exploitation behavior, including a root attacker installing the TAC Agent Python C2 implant (C2 tac.vpnla[.]org, never tasked) and Chinese-language implant strings. OpenSSH fixed the flaw in 10.6p2 on November 5, and Previdian confirmed exploitation from 13 IPs in nine countries. Title revised: "Hackers actively exploit SSHole OpenSSH flaw (CVE-2026-123158) to gain root on Linux systems". source
  • 2026-11-09 17:10Z CVE-2026-123158 was added to CISA's Known Exploited Vulnerabilities catalog. source
  • 2026-11-09 15:12Z The article details the root cause (musl crypt() returning * with salt borrowing), fixed OpenSSH 10.6p2 and per-branch Alpine package versions, and states that as of Nov 6 neither OpenSSH nor Alpine reports exploitation, with CISA marking exploitation status as poc. It also gives exposure checks and mitigations, and notes that the Alpine tiny-cloud alpine account is affected. Title revised: "OpenSSH SSHole (CVE-2026-123158) password auth bypass on musl/Alpine; PoC public, exploitation unconfirmed". source
Attackers probing SAP NetWeaver honeypots for webshells left by CVE-2025-31324; no confirmed compromises stated · 1 development
  • 2026-11-09 15:31Z Public repo for CVE-2021-44228: palantir/log4j-sniffer — A tool that scans archives to check for vulnerable log4j versions (★205; verify before trusting — fake PoCs are common). source
OpenSSH on musl flaw (*sshole) lets oversized passwords log into password-disabled accounts; exploited in the wild; patch to 10.6p2 · 2 developments
  • 2026-11-09 18:15Z New reporting headline states hackers are exploiting the *sshole OpenSSH flaw to breach Linux systems, contradicting the earlier claim that sources did not report observed exploitation. Confirmed in-the-wild exploitation is a material change for hunters. source
  • 2026-11-09 15:32Z An index-page headline reports that hackers targeted the OpenSSH "SSHole" flaw within hours of disclosure and gained root on a honeypot. This contradicts the stored summary's statement that no exploitation had been observed. source
Google patches Chrome zero-day CVE-2026-125350 (XML use-after-free) exploited in the wild; no public exploit details · 1 development
  • 2026-11-10 19:32Z CVE-2026-125350 was added to CISA's Known Exploited Vulnerabilities catalog. source
Barracuda confirms exploitation of ESG flaws CVE-2026-116606 and CVE-2026-111560 giving root access at a small number of organizations · 2 developments
  • 2026-11-10 19:32Z CVE-2026-111560 was added to CISA's Known Exploited Vulnerabilities catalog. source
  • 2026-11-10 19:32Z CVE-2026-116606 was added to CISA's Known Exploited Vulnerabilities catalog. source

From the brief — 18 verdict-shaped cards

P1

Teams help-desk impersonation leads to Quick Assist access and AD CS ESC1/ESC8 abuse, data exfiltration

MediumIoC cardAI verdict card

Microsoft investigated two unattributed intrusions where attackers impersonated IT support on Teams from external onmicrosoft.com tenants, got users to grant Quick Assist sessions, staged archives into KB-prefixed user-profile folders and ran payloads with portable/renamed Python, Bun or Java runtimes, then performed discovery and AD CS abuse. Case 1 abused an ESC1 template for privileged certificates, ran DCSync, and exfiltrated file-share data via Rclone renamed SearchApp.exe to an external SFTP server through a privileged account excluded from automatic disruption. Case 2 used PetitPotam to coerce DC NTLM auth, relayed it to AD CS Web Enrollment (ESC8), obtained a DC certificate and a TGT via PKINIT before the workstation was isolated. Hunt for Quick Assist sessions followed by runtimes executing from KB* AppData folders, anomalous certificate requests with requester-supplied SANs, /certsrv requests authenticated as DC machine accounts from other hosts, and PKINIT from workstations.

EXPOSURE CHECK
AffectedActive Directory Certificate Services with ESC1-vulnerable authentication templates · AD CS Web Enrollment / Certificate Enrollment Web Service accepting NTLM without EPA (ESC8); Windows Server 2022/2019 require manual EPA enablement · Microsoft Teams with external access allowed (social engineering, no Teams vulnerability)
Only ifUsers accept external Teams contact and grant Quick Assist/remote-support sessions · Certificate template allows requester-supplied subject/SAN with broad enrollment (ESC1) · Web Enrollment endpoint reachable with NTLM and no HTTPS+EPA (ESC8)
Not affected ifAD CS Web Enrollment removed or HTTPS+EPA enforced / NTLM disabled per KB5005413 · Windows Server 2025 AD CS with default EPA · No templates allow requester-supplied subject with broad enrollment

Why it matters: Concrete huntable behaviors against ubiquitous AD CS/Teams with confirmed DCSync and exfiltration; no patch, configuration-dependent.

P1

Ivanti Connect Secure zero-days CVE-2026-111357 and CVE-2026-118527 chained with CVE-2026-104935 in attacks by UTA0576

Criticalactor: UTA0576CVE-2026-111357CVE-2026-118527CVE-2026-104935update to 2026-10-29Verdict card

Ivanti Connect Secure gateways were compromised via two zero-days chained with the authentication bypass CVE-2026-104935, with exploitation reported since at least October 1, 2026, per Volexity and Defused as cited by BleepingComputer. Volexity attributes the activity to UTA0576, which gained unauthenticated root-level code execution, deployed no malware or web shell, re-exploited the device for each command, and tampered with logs. Hunters should look for anomalous ICS behavior and log tampering rather than relying on a clean Integrity Checker Tool result.

EXPOSURE CHECK
AffectedIvanti Connect Secure (ICS) gateway, with CVE-2026-104935, CVE-2026-111357, and CVE-2026-118527 chained
Only ifDevice exposed to the internet or reachable by attackers
Fixed inPatches released by Ivanti for CVE-2026-104935 (October 2026) and for CVE-2026-111357 and CVE-2026-118527 (advisory updated November 2026); specific version numbers not stated in source

Why it matters: Actively exploited edge VPN gateway with CISA KEV listing and over 5,000 exposed instances; detection relies on log tampering and anomalous command behavior.

P1

Alpine Linux rebuilds GitLab after attempted RCE on CVE-2026-97229; no confirmed compromise

HighCVE-2026-97229update to 2026-10-30Verdict card

Attackers attempted to exploit CVE-2026-97229, a maximum-severity integer overflow in the Onigmo regex engine bundled in Ruby, against Alpine Linux's self-hosted GitLab on October 20-21 by submitting malicious CI/CD pipeline configurations, causing eight worker crashes with some partial successes. Alpine rebuilt the instance and reset all passwords because it could not rule out code execution, though it found no tampering in repositories, packages, or releases through October 27 and says no compromise has been confirmed. Hunters should look for malicious regular expressions in CI/CD pipeline configurations and GitLab worker crashes, and confirm the Ruby-bundled fix is present since patching GitLab alone was insufficient.

EXPOSURE CHECK
AffectedGitLab (CI/CD regex compiler Onigmo bundled in Ruby), CVE-2026-97229; Alpine initially ran GitLab 19.3.4 and later 19.3.6 which did not close the flaw without the Ruby patch
Only ifSelf-managed GitLab instance with CI/CD pipelines accepting crafted regular expressions
Not affected ifGitLab instance running a version with both the GitLab fix and the bundled Ruby update
Fixed inGitLab 19.3.5 plus Ruby fix (Alpine image alpinelinux/gitlab:19.3.6 with Ruby 3.3.13)

Why it matters: Max-severity unauthenticated RCE in GitLab with concrete CI-config and crash indicators, but attempts only and no confirmed compromise. (raised to P1: exploited + behaviors/KEV)

P1

C3RB3R ransomware attacks target Synology DSM devices running outdated versions; vendor warns, no confirmed success counts in source

Highactor: C3RB3Rmalware: C3RB3R ransomwareCVE-2024-10441CVE-2024-50629CVE-2024-10445AI verdict card

Synology warned customers that threat actors are exploiting a vulnerability patched in December 2024 to target DSM devices running outdated versions, with attacks aiming to encrypt data and extort ransom. The source links the November 2024 advisory covering CVE-2024-10441, CVE-2024-50629, and CVE-2024-10445 but says Synology has not yet named the exploited flaw. Hunters should look for encrypted files with a .L0CK3D extension, a read-me3.txt ransom note, and DSM management interface exposure to the internet.

EXPOSURE CHECK
AffectedSynology DiskStation Manager (DSM) outdated versions; patched in November 2024 advisory
Only ifManagement web interface reachable from the Internet
Not affected ifRunning patched DSM versions listed by Synology
Fixed inDSM 7.2.2-72806-1 or above; DSM 7.2.1-69057-6 or above; DSM 7.2-64570-4 or above; DSM 7.1.1-42962-7 or above; DSM 6.2.4-25556-8 or above

Why it matters: Actively exploited internet-facing NAS management interface with vendor advisory and named ransom artifacts.

P1

Unconfirmed: CVE-2026-42589 Gotenberg RCE exploitation reported in ThreatsDay roundup

Lowmalware: cache_baseCVE-2026-42589update to 2026-10-30AI verdict card

A ThreatsDay roundup reports that threat actors are exploiting CVE-2026-42589, a critical RCE in Gotenberg, to deliver a Go reverse shell called cache_base, citing VulnCheck. The roundup itself is unverified and the brief marks the item as unconfirmed, so treat the claim as reported rather than confirmed. Hunters could look for Gotenberg processes spawning shells and outbound connections to unfamiliar C2 hosts.

EXPOSURE CHECK
AffectedGotenberg (CVE-2026-42589, CVSS 9.8)
Fixed inPatched in May 2026 per the source; exact fixed version not stated

Why it matters: Reported exploitation of a critical RCE in a web-facing service with a described reverse shell, but unconfirmed in the brief and only cited through a roundup. (raised to P1: exploited + behaviors/KEV)

P1

WordPress Core race condition (no CVE yet) drawing exploit attempts, no confirmed compromises

HighAI verdict card

Defiant reports a race condition in WordPress Core's update process, patched in WordPress 7.1.4 (October 28) and backported to branches through 4.7, that can enable unauthenticated remote code execution with high attack complexity. The flaw stems from predictable, web-accessible staging directories used while unpacking full-package Core updates. Wordfence telemetry reports more than 18,500 requests in 21 hours targeting staged setup-config.php installer paths, but has not reported successful compromises. Hunters should look for web requests to staged installer paths such as setup-config.php during and after Core updates.

EXPOSURE CHECK
AffectedWordPress Core update process (versions prior to 7.1.4 and backported branches through 4.7, as stated)
Only ifFull-package Core update in progress with staging tree publicly web-accessible and PHP-executable · Predictable or discovered staging path
Not affected ifSites already on WordPress 7.1.4 or a backported patched release
Fixed inWordPress 7.1.4 and backported releases through 4.7 branch

Why it matters: Unauthenticated RCE in WordPress Core with active exploit attempts across many internet-facing sites; no confirmed compromises reported.

P2

VOLTA infostealer steals browser, wallet and cloud credentials, ranks victims via OpenRouter LLMs

Mediummalware: VOLTA-AUTODOXER (VOLTA)IoC card

Cisco Talos documents VOLTA-AUTODOXER, a self-deleting Windows infostealer (likely builder-sold) that harvests browser credentials/cookies (bypassing Chrome App-Bound Encryption via headless Chrome), wallets, Microsoft OAuth tokens, SSH/cloud keys and Wi-Fi passwords, then enriches with stolen sessions and POSTs a dossier to OpenRouter for LLM victim ranking. Exfiltration is via Telegram in three zip stages. Hunt for Chrome launched with --headless by non-developer processes, endpoint connections to openrouter.ai/api/v1/chat/completions from unusual processes, and files volta_debug.txt, Identity_Report.txt, AI_Analysis.txt, volta_*.zip.

EXPOSURE CHECK
AffectedWindows hosts with Chromium browsers, Firefox, Outlook, Slack, crypto wallets

Why it matters: Commodity stealer with concrete huntable behaviors (headless Chrome ABE bypass, OpenRouter calls, Telegram exfil) but no enterprise-targeting reported.

P2

Trojanized Claude Code extension (2.1.312/2.1.313) on Cursor marketplace attempts persistent SSH backdoor

LowIoC card

Tampered anthropic.claude-code versions 2.1.312 and 2.1.313 were served by the Cursor extension marketplace for about 11 hours on Oct 29, 2026, exposing up to 5,000 developers. An injected JavaScript loader in extension.js collects host recon (Git email, env-var names matching KEY/TOKEN/SECRET), appends an svc-telemetry SSH key to authorized_keys, tries to enable SSH, opens a reverse tunnel (-N -R '*:0:localhost:22') to 134.209.82.225, and persists via LaunchAgent com.apple.sysmond, @reboot cron, or SysMon scheduled task/Startup sysmon.cmd. Coding errors likely blocked remote access on many macOS/Windows hosts, but keys and persistence may still be written; hunt for the svc-telemetry key, .smt/.smtk/.stk_ files, ssh/autossh child processes of Cursor, and connections to the C2.

EXPOSURE CHECK
Affectedanthropic.claude-code extension versions 2.1.312 and 2.1.313 from the Cursor extension marketplace (Oct 29, 2026, ~2:27 AM–1:35 PM PDT)
Only ifInstalled or auto-updated the extension via Cursor marketplace during the exposure window · Remote SSH access requires an SSH server already running on the host
Not affected ifInstalled from Microsoft Visual Studio Marketplace, Open VSX, or npm @anthropic-ai/claude-code

Why it matters: Short-lived supply-chain incident affecting Cursor users with concrete, huntable persistence artifacts and Microsoft-published queries; server taken down.

P2

Threat actors use agentic AI tooling (ARTEX) to find exposed secrets and compromise Azure and Entra ID tenants

Mediumactor: UNC7228 (STORM-0940)malware: ARTEXupdate to 2026-10-27IoC cardVerdict cardAI draft v2

GTIG and Mandiant report PRC-nexus UNC7228 (overlaps STORM-0940) and financially motivated groups operating open-source agentic pentest frameworks (ARTEX, PentAGI, CAIRN, Hexstrike) in real intrusions since late August 2026, with confirmed compromise and data theft. ARTEX used supplied valid credentials to probe Azure/AWS permissions, poison MySQL general_log into JSP webshells, abuse Kudu APIs, Kerberoast/DCSync, and post output to rotating webhook.site URLs via curl. Hunt for 2–25 second bursts of API calls, artex-probe-*/ArtexProbe artifacts, MySQL SET GLOBAL general_log_file changes, and server egress to webhook.site.

EXPOSURE CHECK
Only ifAttacker holds valid credentials (compromised accounts, SAS tokens, service principals, Kudu publishing credentials, IAM keys) · Internet-exposed management interfaces (e.g., Azure Kudu/SCM) or application SQL APIs

Why it matters: Concrete huntable behaviors (MySQL log webshell, webhook.site curl C2, ARTEX naming artifacts) but no specific CVE; noisy agentic tooling seen against finance in Asia.

P2

Unit 42 tracks CL-UNK-1211 espionage cluster targeting government-linked Linux servers with PHP web shells and SysGoRAT

Mediumactor: CL-UNK-1211malware: SysGoRATupdate to 2026-10-16IoC cardAI verdict card

Palo Alto Networks Unit 42 reports a cyber espionage cluster tracked as CL-UNK-1211 that targeted Linux infrastructure tied to government entities between October 2025 and April 2026. The actors used PHP web shells, three credential-harvesting methods (.bashrc replacement, PHP login page injection, and scanning config and history files for cleartext passwords), and a Go-based multi-platform RAT called SysGoRAT that connects over WebSocket to a hard-coded IP. Hunters should look for PHP web shells, unexpected .bashrc modifications, injected PHP login code, the search_social.php and zip_mails.sh scripts, and enumeration of /var/qmail/mailnames/.

Why it matters: Concrete huntable behaviors on Linux servers, but no KEV or confirmed exploited vulnerability is named in the sources.

P2

NetamLoader: Kaspersky details .NET loader planted in Windows update staging directory on a government Windows 10 build in Asia

Lowmalware: NetamLoaderIoC card

Kaspersky reported a previously undocumented .NET loader, NetamLoader, packaged in a CAB file placed in the Windows update download directory on a custom government-only Windows 10 build in Asia, with a single victim observed. The chain abuses AppDomainManager injection via a .config file to run through PatchMyPC-ScriptRunner.exe, then loads layered payloads from Resources.resx and runs them in dllhost.exe, beaconing to a C2 host after a jitter delay. Hunters should look for files and processes under the SoftwareDistribution\Download paths and dllhost.exe loading XAML content; the source does not state the attacker or whether data was stolen.

EXPOSURE CHECK
AffectedCustom government-only Windows 10 build used in Asia (per Kaspersky)

Why it matters: Concrete huntable file paths and loader behavior, but a single observed victim in a bespoke government build limits breadth.

P2

FBI attributes ~$6.36B Binance crypto theft to North Korea's TraderTraitor; 628 laundering addresses published

Highactor: TraderTraitor

The FBI formally attributed the October 29, 2026 theft of roughly $6.36 billion in virtual assets from Binance to TraderTraitor (also tracked as Lazarus Group, Jade Sleet, APT38) and published 628 associated cryptocurrency addresses for exchanges and VASPs to block. Binance linked the breach to a compromised DevOps engineer's laptop that let attackers access a service container and submit unauthorized withdrawals, with most funds moved within 20 minutes. Hunters should look for laundering-address matches in blockchain monitoring and, for their own environments, prior-style patterns such as developer-workstation compromise via fake recruiter or test-code lures.

Why it matters: Attributed major financial theft with a known workstation entry path, but no concrete huntable host behaviors or published detection content in the sources.

P2

Northflank breach leads to unauthorized use of customers' AI API keys; customers told to rotate all secrets

Medium

Cloud platform Northflank disclosed a security incident on October 30 after a threat alert from Wiz and told customers to assume environment variables were decrypted and to rotate all keys. Customers reported unauthorized use of AI API keys stored on the platform, though the company has not disclosed how attackers gained access or how many customers were affected. Wiz's "Black October for AI Developer Platforms" report ties the incident to at least nine AI developer platform incidents in October, with LLMJacking as the abuse pattern. Hunters should review AI provider usage and billing logs for unexpected activity.

EXPOSURE CHECK
AffectedNorthflank cloud platform customer environment variables and stored AI API keys (versions not stated)
Only ifCustomer secrets or AI API keys stored in Northflank environment variables, secret groups, or add-ons

Why it matters: Customer-facing secret exposure with reported AI key abuse, but no technical behaviors or detection content published by sources.

P2

Polymarket returns $3.9M after malicious script drains traders; DebugBear DNS records compromised via registrar

Low

Polymarket halted trading on its international platform on October 29 after users reported unauthorized withdrawals, which Hudson Rock linked to malicious JavaScript served from a DebugBear address loaded by the Polymarket site. The script targeted logged-in traders, checking portfolios and either dumping positions or shifting assets to attacker-chosen wallets, piggybacking on open sessions rather than exfiltrating passwords or keys. DebugBear says its DNS server records were compromised through its domain registrar and it has not explained how registrar access was obtained. Hunters should look for unexpected third-party script loads from the DebugBear RUM embed and unauthorized changes at the registrar and DNS layer.

EXPOSURE CHECK
AffectedDebugBear real user monitoring (RUM) script embed
Only ifWebsite loads the DebugBear RUM embed script
Not affected ifDebugBear embed code removed, as DebugBear initially advised customers

Why it matters: Concrete web-script behavior in a third-party embed with confirmed trader losses, but no published detection content and registrar access method unknown.

P2

Linux kernel TCP use-after-free CVE-2026-98432 enables remote root on MPTCP listeners; distro fixes rolling out, no confirmed exploitation

MediumCVE-2026-98432update to 2026-10-30AI verdict card

Anthropic researchers reported a remote root exploit for a use-after-free race in the Linux kernel IPv4 TCP code (CVE-2026-98432), with the CNA scoring it 9.8 and Red Hat scoring it 5.9. The sources say RCE was demonstrated on servers with an MPTCP listener, while the flaw also affects ordinary TCP, and Go 1.24+ enables MPTCP listeners by default on Linux. Ubuntu, RHEL, and Rocky Linux were still vulnerable or awaiting fixes at publication, and the sources report no confirmed in-the-wild exploitation; hunters should inventory kernel versions and MPTCP listeners.

EXPOSURE CHECK
AffectedLinux kernel IPv4 TCP code, versions dating back to 4.4 (per BleepingComputer) · Ubuntu 22.04 LTS, 24.04 LTS, 26.04 LTS, 26.10 (vulnerable per Canonical tracker as of Oct 30) · Red Hat Enterprise Linux 8, 9, 10 (per Red Hat); RHEL 7 not affected · Rocky Linux 8, 9, 10 (per CIQ)
Only ifServer running an MPTCP listener (RCE demonstrated only in this condition) · Ordinary TCP also affected, but RCE not publicly demonstrated without an MPTCP listener · Go 1.24+ programs may enable MPTCP listeners by default on Linux · Triggering race may also involve net.ipv4.tcp_migrate_req enabled or BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program
Not affected ifRHEL 7 (kernel does not contain vulnerable code) · macOS (uses XNU kernel, not Linux) · Disabling MPTCP alone is insufficient per CIQ
Fixed inDebian 12: kernel 6.1.190-1; Debian 13: kernel 6.12.113-1; other vendors (Oracle Linux, Amazon Linux, SUSE) released fixes for some kernel versions; Ubuntu, RHEL, Rocky fixes pending at publication

Why it matters: Public RCE exploit for root on MPTCP listeners with fixes still rolling out, but no confirmed exploitation and no huntable adversary behavior in sources.

P2

Public PoC for Android 'SMS of Death' DoS (CVE-2026-58882) crashes unpatched phones via WAP Push SMS

MediumCVE-2026-58882

A researcher published a proof-of-concept for CVE-2026-58882, a zero-click denial-of-service flaw in Android's WapPushOverSms.decodeWapPdu that a malformed eight-byte WAP Push message sent as a data SMS to port 2948 can trigger. The crash of com.android.phone disrupts cellular connectivity and ongoing calls, and can cause reboot loops; Google reportedly patched it in the October 2026 updates for Android 14 through 17, while Android 12 and 13 remain unpatched. Hunters should look for abnormal crashes of com.android.phone and inbound data SMS to port 2948 on devices that are not yet patched.

EXPOSURE CHECK
AffectedAndroid 12 and 13 (no fix, per source)
Not affected ifAndroid 14 through 17 with the October 2026 security update or later
Fixed inGoogle fix 'Fix remote DoS in decodeWapPdu' in October 2026 Android security updates for Android 14 through 17

Why it matters: Public PoC for a remote DoS on Android 12/13 without a fix; no confirmed exploitation in the sources and no enterprise-side behavior to hunt beyond device crashes.

P2

CVE-2026-112816: CVSS 10.0 certificate-chain flaw in Canonical LXD and MicroCloud allows client impersonation; no confirmed exploitation

MediumCVE-2026-112816

Canonical LXD and MicroCloud contain a critical flaw where the server validated only the leaf of a client certificate chain against the trust store, letting an attacker with network access to the HTTPS API and a trusted client's public certificate impersonate that client. The Incus project reported the bug, and Canonical confirmed LXD is affected. Per the sources, there is no public sign of exploitation, CISA has not listed it as known exploited, and no working exploit is published; hunters should check for exposed LXD HTTPS API listeners (core.https_address) and MicroCloud cluster join activity.

EXPOSURE CHECK
AffectedLXD 4.0.14, 5.0.10, 5.21.8 and 6.9 and earlier releases, per CVE record (fixed in snap 4.0.15, 5.0.11, 5.21.9, 6.10.1) · MicroCloud (fixed in 2.1.5 and 3.4.1) · Incus (fixed in 7.6.0)
Only ifNetwork API enabled via core.https_address (standalone LXD listens only on a local socket by default) · Attacker has network access to the HTTPS API · Attacker possesses the public certificate of a client already trusted by the server · For MicroCloud, attacker can capture a member's public certificate during cluster join
Not affected ifUbuntu archive LXD packages are listed as not affected or not shipped; use the snap releases · LXD API not exposed on the network
Fixed inLXD 6.10.1, 5.21.9, 5.0.11, 4.0.15; MicroCloud 3.4.1, 2.1.5; Incus 7.6.0

Why it matters: Critical CVSS 10.0 authentication bypass in virtualization software, but only exploitable with network API access and a trusted client's public certificate; not known exploited.

P2

Roundup: critical 16-year-old TianoCore EDK II PXE boot overflow (CVE-2026-97631) and other week's news

MediumCVE-2026-97631

SecurityWeek's weekly roundup covers CVE-2026-97631, a critical buffer overflow in TianoCore EDK II PXE network boot code that Ars Technica says affects most server firmware, exploitable by an attacker with local network access sending an oversized ICMP error message during PXE boot. Only machines using network boot are exposed, and the source says fixes must come from firmware vendors. The remaining items are news summaries (Cathedral's disputed AI-led intrusion claim against Anthropic, suspected Iran-linked freezer hacks, a Cloudflare/SGLang cross-tenant leak, and OFAC sanctions on North Korean IT-worker facilitators) with no hunt-ready technical detail for this story.

EXPOSURE CHECK
AffectedTianoCore EDK II firmware code as used by server firmware suppliers such as AMI, Insyde and Phoenix
Only ifMachine uses network boot (PXE) · Attacker has local network access to the machine during boot
Not affected ifMachine does not use PXE network boot

Why it matters: Critical firmware flaw in widely deployed server UEFI code with local network exposure; detection content is limited, so hunt-worthy but not immediate.

Also in today's read (12)

Priorities and summaries are drawn from public reporting only. The analyst view carries the full behaviors, evidence and indicators.