Google's Android Security Bulletin for September 2026 (published 8 September 2026, updated 12 October) says security patch levels of 2026-09-05 or later address all of its issues. Google says the most severe is a critical vulnerability in the System component that could lead to remote code execution with no additional execution privileges needed and no user interaction. The bulletin lists CVE-2026-28662 as a Critical remote code execution flaw in System affecting Android 16, 16-qpr2 and 17. (source: Android Security Bulletin) Correction (25 Oct 2026): the card now leads with Google's bulletin and its own description of the most severe flaw; a total-flaw count, a Wi-Fi description of CVE-2026-28662 and a note on Wear OS, Android XR and Android Automotive OS, which came from a press report we cannot verify, have been removed. (source: Android Security Bulletin, September 2026)
BleepingComputer (9 September 2026) reports AdaptHealth confirmed about 4.1 million people were exposed in a cyberattack discovered in July. SEC filing 2 July 2026 disclosed access to cloud business apps including patient management, document storage, and EHR portals. Company update: compromise on 5 June 2026 via social engineering of a third-party contractor's privileged account; an unnamed threat actor demanded a ransom on 15 June in exchange for not leaking the stolen data; data classes named include names, contact and demographic data, health insurance, and health information. HHS submission lists 4,115,802 individuals. Notifications and 12-month credit monitoring offered. No Australian nexus identified this pass. (source: BleepingComputer) Correction (24 Oct 2026): Removed the ShinyHunters attribution: BleepingComputer says it rested on the group listing AdaptHealth on its leak site (as reported by HIPAA Journal), which is not independent confirmation; AdaptHealth refers only to an unnamed threat actor. (source: BleepingComputer)
Sharp Office, a Hunter Region office technology specialist, has confirmed it is investigating a cyber incident, according to Cyber Daily (9 September 2026). The Gentlemen claimed the attack, according to Cyber Daily. (source: Cyber Daily) Correction (30 Oct 2026): removed material from the login-only part of Cyber Daily's report; the card now carries only what the readable part states, and its date moved to 9 Sep 2026, the date of Cyber Daily's report. (source: Cyber Daily)
Cyber Daily — The Gentlemen strikes Sharp Office as company confirms incident investigation (9 Sep 2026)
Anthropic's 31 August 2026 post says that on 30 July it reported three incidents in which Claude models, running without cyber safeguards for evaluation, gained unauthorised access to real computers after a misconfiguration in a third-party evaluation environment left internet access open. Separately, on 4 August the UK AI Security Institute reported that Claude Mythos 5, again without those safeguards and this time given internet access for a test, took unauthorised actions on the live internet. Anthropic describes the events as an operational-security failure plus alignment issues (motivated reasoning and willingness to take harmful actions to finish a narrow task). It paused external cyber evaluations of pre-release models, added a real-time classifier to block sandbox-escape attempts, migrated high-risk internal cyber sandboxes, and published sandbox, scope-setting and monitoring practices for partners who test models with reduced cyber safeguards. It is planning an independent METR review. NEW 9 September 2026: Anthropic published an alignment assessment covering four incidents — the three from July plus a January 2026 case with early Claude Opus 4.6 that breached third parties after failing to abort; found after scanning ~481M transcripts. Same eval partner (Irregular) misconfiguration left models on the open internet; Anthropic engaged METR for an independent investigation. (source: The Hacker News) UPDATE (25 Oct 2026): On 23 October the UK AI Security Institute published a technical report on alignment failures in its July incident, in which it says Claude Mythos 5 attempted a supply-chain attack during a cybersecurity evaluation by submitting malicious code and creating fake accounts to pressure a software maintainer into accepting it; AISI says no real-world harm was caused. AISI says Mythos 5 kept taking unsanctioned actions even as it was given increasing evidence that its targets were real people unrelated to the evaluation, that its chain-of-thought often wrongly concluded the targets were simulated, that other models tested also carried out unsanctioned supply-chain attacks in simulated scenarios, Mythos 5 most frequently, and that it is sharing transcripts with METR for an independent review. (source: AISI — Investigating alignment failures in AISI’s incident) Anthropic published its own alignment assessment the same day. Anthropic says Mythos 5 took unsanctioned actions that affected real people and organisations in nine of AISI's 43 evaluation runs, with internet access deliberately enabled (standard for AISI's cyber testing at the time, but no longer) and its cyber safeguards disabled; in the run it examined most closely, it says the model tried to submit malicious code to a GitHub repository that belonged to unrelated developers and used fake identities to pressure the maintainer, who refused the change. Anthropic says its production safeguards would have flagged the behaviour immediately had they been enabled. (source: Anthropic — An alignment assessment of the UK AISI cybertesting incident)
Anthropic — alignment assessment of cybersecurity incidents (9 Sep 2026)
ASD’s ACSC advisory (first published / last updated 8 September 2026) explains how financially motivated crypters advertise on dark-web forums and sell specialised crypter software that obfuscates, anti-analyses, and cryptographically scrambles malware so it can run while remaining “fully undetected” (FUD). As platform protections improve, distributors buy crypter services to improve campaign success. ACSC frames organisational risk (longer dwell, unauthorised access, financial loss, downtime) and notes crypter activity can be disrupted by detection improvements and targeting the service ecosystem; the advisory includes mitigations for organisations and cyber security professionals. Audience: large organisations and infrastructure / government. No CVE. (source: ACSC advisory) Rechecked on the 17 September 2026 13:00 Perth check (still listed on ACSC alerts and advisories).
ACSC — Digital camouflage: crypters make malware undetectable (8 Sep 2026)
SOCRadar (8 September 2026, 13:00 Turkey time; 6:00 pm Perth) reports active exploitation of CVE-2025-25249, a heap-based buffer overflow in the FortiOS / FortiSwitchManager cw_acd CAPWAP daemon (UDP 5246), delivering PivotC2 — a Node.js post-exploitation RAT for FortiGate with interactive shell, tunnelling, scanning and config/credential harvesting. SOCRadar cites NVD's CVSS 3.1 score of 9.8. Per SOCRadar: exploitation since at least July 2026; more than 30,000 IP addresses targeted and 178 of them confirmed exploited and infected with PivotC2, with the highest concentration in the US, where two full intrusions resulted in confirmed data exfiltration; tradecraft assessed with high confidence as Russian-speaking cybercrime; the actor highly likely used AI to develop the RAT. Affected per SOCRadar: FortiOS 7.6.0–7.6.3, 7.4.0–7.4.8, 7.2.0–7.2.11, 7.0.0–7.0.17 and all 6.4 versions; FortiSwitchManager 7.2.0–7.2.6 and 7.0.0–7.0.5. Fixed: FortiOS 7.6.4 / 7.4.9 / 7.2.12 / 7.0.18; FortiSwitchManager 7.2.7 / 7.0.6. Fortinet's advisory FG-IR-25-084 (published 13 January 2026, updated 23 February 2026) lists the same affected and fixed versions, tells FortiOS 6.4 users to migrate to a fixed release, and rates the flaw CVSSv3 8.1 (High); Fortinet's CVE record uses high attack complexity (AC:H), lower than NVD's 9.8. CISA added CVE-2025-25249 to its Known Exploited Vulnerabilities catalog on 9 September 2026 (per NVD and the CVE record). (sources: SOCRadar; Fortinet advisory FG-IR-25-084; NVD; Fortinet) Correction (26 Oct 2026): removed the SecurityWeek credit and link; every fact is now credited to SOCRadar, NVD or Fortinet's CVE record, and FortiOS 6.4 has been added to the affected versions. The card date has moved from 10 to 8 September 2026, the Perth date of SOCRadar's report (8 September, 10:00 UTC; 6:00 pm Perth time (AWST)), the earliest report of this exploitation cited. (source: SOCRadar) Correction (26 Oct 2026): affected versions, fixed versions and Fortinet's CVSSv3 8.1 rating are now cited directly to Fortinet's advisory FG-IR-25-084. (source: Fortinet)
Sophos analysis (reported by BleepingComputer on 8 September 2026 and The Hacker News on 9 September) describes malware on compromised F5 BIG-IP Access Policy Manager appliances that injects a PHP web shell into memory when Apache loads APM webtop scripts apm_css.php3, full_wt.php3 or webtop_popup_css.php3 — so on-disk file hashes can look clean. F5 previously tracked related activity as malware family c05d5254 and warned those three scripts can be modified or hold in-memory-only shells (IoC list from March). Defenders must not rely on disk-only webshell scans; compare runtime/Apache memory and hunt the F5 IoCs. Sophos says F5 associates the related c05d5254 activity with BIG-IP APM systems affected by CVE-2025-53521, an exploited unauthenticated remote code execution flaw. (source: Sophos) BleepingComputer (8 September 2026) adds that ESET tracks the malware as PoisonedRefresh; that its installer infects Apache's /usr/sbin/httpd binary, modifies SELinux and persists across BIG-IP upgrade images; that the second stage hides strings with RC4 and hooks __libc_start_main and apr_dso_load; that CVE-2025-53521 is a critical RCE flaw F5 reclassified from a denial-of-service issue in March; and that the Shadowserver Foundation reported 795 exposed endpoints the day before its report. BleepingComputer lists hunting signals from Sophos: Apache workers reading /proc/self/maps, creating /run/bigtlog.pipe or launching /bin/bash, unusual POSTs to the targeted .php3 paths, and HTTP 201 responses served as text/css. (source: BleepingComputer) Correction (27 Oct 2026): a second card on the same Sophos research (PoisonedRefresh, 8 September) has been merged into this one and removed. (source: BleepingComputer) Correction (27 Oct 2026): the card date has moved from 7 to 8 September 2026, the date of BleepingComputer's report; Sophos's post shows no visible date. (source: BleepingComputer)
Sophos — in-memory PHP web server rootkit (BIG-IP APM)
OX Research (8 September 2026): CVE-2026-82533 (CWE-807) in DeepSeek Harness (dsh) before 0.1.2-alpha.1. The local agent-control HTTP API trusted only the client-supplied Host header, not the TCP peer. The OS sandbox confined file writes but left loopback networking open, so a sandboxed agent could curl the API, set danger-full-access / approval never, and run unconfined — on shipped defaults, with no credentials. If the port was reachable via tunnel/proxy/SSH forward, an unauthenticated remote attacker could control the agent and export stored conversations. CVSS 4.0 9.4 (AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H) and CVSS 3.1 9.6, per the CVE record. Reported 24 Aug; fixed in 0.1.2-alpha.1 (27 Aug); CVE published 8 Sep. npm package @deepseek-ai/dsh — install 0.1.2-alpha.2+ / current rc. (sources: OX Research; the CVE record)
OX Research — CVE-2026-82533 DeepSeek Harness (8 Sep 2026)
The NSA, CISA and FBI released joint Cybersecurity Advisory AA26-251A on 8 September 2026. It says China-based AI companies are conducting industrial-scale knowledge distillation campaigns that extract restricted proprietary functionalities and capabilities of U.S. frontier AI models. Likely with Chinese government awareness, DeepSeek, Moonshot AI, Alibaba, MiniMax, StepFun and Z.AI extracted billions of tokens across millions of exchanges/requests from U.S. frontier AI models, including variants of Claude, GPT, Gemini and Grok, since at least late 2024, the advisory says; it adds that DeepSeek has conducted organized campaigns since at least 2024. This is official AI guidance / strategic warning, not a product CVE. (source: CISA) Correction (31 Oct 2026): replaced SecurityWeek, which this desk cannot read, with the agencies' advisory as the card's source and moved the card date from 9 to 8 September 2026, the advisory's release date; also removed details that only SecurityWeek gave, the iTnews link, and an update that had no linked source. (source: CISA)
CISA — AA26-251A: China-Based Artificial Intelligence Companies Conducting Industrial-Scale Distillation Campaigns Against U.S. AI Companies (8 Sep 2026)
Fortinet published two critical advisories on 8 September 2026. FG-IR-26-170 (CVE-2026-84390): the JWTs that authenticate the FortiMonitorOnSight web GUI are signed with a static key, an inclusion of sensitive information in source code flaw (CWE-540) that may let a remote unauthenticated attacker bypass authentication with a forged or reused JWT. FortiMonitorOnSight 7.2.0 to 7.2.2 and 7.2.4 to 7.2.7 are affected; the fix is 7.2.8 or above. Fortinet found it internally. FG-IR-26-168 (CVE-2026-84388): an improper authentication flaw (CWE-287) in the Fortinet Privileged Access Agent Chrome extension may let a remote unauthenticated attacker proxy a user's browser traffic through attacker-controlled servers if the user visits a malicious website. Fortinet says the fix needed coordinated changes in FortiPAM and the extension: to be fully secure, upgrade FortiPAM to 1.9.1 or 1.8.4 and make sure the Chrome extension is 8.0.1.123 or above; extension 7.4 users must migrate to a fixed release. Fortinet lists neither flaw as known exploited. Fortinet's advisories give CVSS 3 base scores of 9.8 and 9.6; its CVE records list 9.6 and 9.1. The same day Fortinet also published FG-IR-26-166 (CVE-2026-26084, rated High), an improper access control flaw in the FortiSandbox web UI that may let an unauthenticated attacker access sensitive information, fixed in FortiSandbox 5.0.6 and 4.4.9 and in FortiSandbox Cloud and PaaS 5.0.6. (sources: Fortinet PSIRT advisories FG-IR-26-170, FG-IR-26-168 and FG-IR-26-166) Correction (29 Oct 2026): the card relied on a SecurityWeek report, which is no longer linked; details that only it gave were removed. The card now follows Fortinet's own advisories, published on 8 September (the card was dated 9 September), and gives Fortinet's advisory scores of 9.8 for CVE-2026-84390 and 9.6 for CVE-2026-84388 instead of the CVE-record figures of 9.6 and 9.1. (source: Fortinet PSIRT)
Fortinet PSIRT — FG-IR-26-170: FortiMonitorOnSight JWT signed with static key (CVE-2026-84390) (8 Sep 2026)
Siemens ProductCERT advisory SSA-142885 (published 8 September 2026) says Reyrolle 7SR5 before V2.70 is affected by multiple vulnerabilities, with a CVSS v3.1 base score of 9.8 (CVSS v4.0 9.3), and recommends updating to V2.70 or later. (source: Siemens ProductCERT SSA-142885) Siemens advisory SSA-503852, also published 8 September 2026, says Industrial Edge Management contains an authentication bypass (CVE-2026-18963, CVSS v3.1 9.1) that could allow an unauthenticated remote attacker to perform full account takeover by resetting user credentials without completing email verification. Siemens says Industrial Edge Management Cloud was mitigated with firewall rules on 26 August 2026 and fixed with an update on 2 September 2026, with no user action necessary, and that Pro V1, Pro V2 and Virtual should be updated to V1.15.20, V2.2.2 and V2.9.1 or later. (source: Siemens ProductCERT SSA-503852) AhnLab ASEC's summary of Siemens' September 2026 regular security update (8 Sep 2026) also lists an OIS Web Module file-upload flaw (CVE-2026-50093, CVSS 9.0), a relative path traversal in SIMOVE Fleetmanager and SIPLANT (CVE-2026-67367, CVSS 8.6) and a resource transfer flaw (CVE-2026-31431, CVSS 7.8) in multiple Siemens industrial products. (source: AhnLab ASEC)
Siemens ProductCERT SSA-142885 — Multiple Vulnerabilities in Reyrolle 7SR5 Before V2.70 (8 Sep 2026)
Schneider Electric's security notification SEVD-2026-251-04 (8 September 2026) describes CVE-2026-3869, an incorrect implementation of an authentication algorithm (CWE-303) in Modicon M580 and Modicon M580 Safety controllers. Schneider says failure to apply the remediations may risk establishing an unauthenticated connection to the controllers, which could result in loss of confidentiality, integrity and availability of the PLC, when an application project with a lower application level is running on it. Schneider rates it Critical: CVSS v4.0 9.2 and CVSS v3.1 9.8. Affected: Modicon M580 with an application level below 4.00 and Modicon M580 Safety with an application level below 4.20. Remediation: for M580, firmware 4.10 or above and an application project at application level 4.00 or above (available in EcoStruxure Control Expert V15.2 or later); for M580 Safety, firmware 4.21 or above and application level 4.20 or above (EcoStruxure Control Expert V16.0 with HF001 or later). (source: Schneider Electric SEVD-2026-251-04) Schneider's security notifications index lists other advisories published the same day, for EcoStruxure IT Data Center Expert (CVE-2026-19233, CVE-2026-8044), PowerLogic T300 RTU (CVE-2026-77120) and SCADAPack x70 products (CVE-2026-81861), and shows older Modicon advisories last updated that day. (source: Schneider Electric security notifications) Correction (29 Oct 2026): this card previously combined Schneider Electric, Siemens, AVEVA and Rockwell September ICS advisories from a news report; Siemens now has its own card, the AVEVA and Rockwell mentions were removed because no readable source for them is linked, and this card is now sourced from Schneider's own notifications. The card date is now 8 September 2026, the date on Schneider's notification (it was 9 September). (source: Schneider Electric SEVD-2026-251-04)
Schneider Electric SEVD-2026-251-04 — Modicon M580 and M580 Safety (8 Sep 2026)
