Five CVEs published on 9 October 2026 cover OpENer, the open-source EtherNet/IP adapter stack maintained by the EIPStackGroup on GitHub and used as a base for industrial devices that speak the CIP protocol. All five affect OpENer v2.3 and the master branch up to commit 76b95cf and are rated 7.5 under CVSS 3.1 (network, no authentication, availability impact): CVE-2026-75347 is a stale-pointer bug in Common Packet Format (CPF) handling, where a UDP I/O packet leaves a pointer to a finished stack frame that a later TCP SendUnitData packet reuses (GitHub issue #575, opened 28 May 2026, says it reproduces against the unmodified POSIX server); CVE-2026-75348 is an out-of-bounds read in the TCP SendRRData CPF parser (issue #573); CVE-2026-75346 is an out-of-bounds read in the CIP SetAttributeList service (issue #572); CVE-2026-75349 is an out-of-bounds read in Connection Manager request parsing (issue #577); and CVE-2026-75345 is an out-of-bounds read in the unconnected explicit messaging path. Each lets a remote attacker crash the stack. The issues were still open when the CVEs were published and the repository's latest commits are dependency bumps, so no fixed release exists. The CVE records were assigned by MITRE, not a vendor, and no product makers have yet said which devices embed affected OpENer code. No exploitation reported. (sources: CVE records; OpENer GitHub issues)
AWS published security bulletin 2026-132-AWS on 9 October 2026 (rated Important) for AWS Tools for PowerShell V5, the module administrators use to manage AWS services from PowerShell. In versions up to and including 5.0.305, under certain conditions an IAM user's plaintext AWS Management Console password is written to local host output without redaction, so it can end up in command output, PowerShell transcripts, command history and any log store that collects them. Anyone who can read those logs could then sign in to the console as that IAM user. AWS's GitHub advisory GHSA-q3x5-q6rm-c7p3 names the trigger: running cmdlets that carry sensitive arguments with the -WhatIf or -Confirm switches. The issue is fixed in 5.0.306. AWS's CVE record scores it 6.7 (CVSS 4.0, local attack, low privileges, user interaction) and asks users, after upgrading, to review PowerShell transcripts and log stores for passwords already disclosed and rotate any affected IAM console passwords. No exploitation reported. (sources: AWS security bulletin 2026-132-AWS; GitHub advisory; AWS Tools for PowerShell 5.0.306 release)
AWS security bulletin 2026-132-AWS — CVE-2026-107783, sensitive information in log file in AWS Tools for PowerShell (9 Oct 2026)
Push Security published research on 9 October 2026 into a malvertising chain it calls Adception. A sponsored Google result for the search 'claude mac' listed bing.com as its domain because the ad's destination was a genuine Bing search-result redirect (bing.com/ck/a), which Bing uses to log clicks before forwarding the visitor with a short JavaScript page. Google's ad review therefore approved a link that pointed at another search engine. The Bing redirect led to a compromised WordPress site of a South American retailer, which only forwarded visitors arriving with a Bing referrer and certain browser headers, and on to claude-desk-code[.]com, a convincing fake Claude download page that sends anyone arriving directly to a 404. The page shows Anthropic's real macOS install command, but its copy button puts a different command on the clipboard: it prints a message about downloading Claude while decoding a Base64-hidden address at lake-90[.]com, then pipes a downloaded .dat file straight into zsh. The final payload has not been identified. Push links several other domains to the same ClickFix kit, which it tracks as AcSig, and says the Bing link carried a timestamp from 5 October 2026. (sources: Push Security; BleepingComputer)
Push Security — Analysing a novel malicious redirect and cloaking technique ('Adception', 9 Oct 2026)
The Argo CD project published advisory GHSA-j6cw-g6p4-7hch on 9 October 2026 for a command injection in the repo-server, the component of the Kubernetes GitOps tool that clones and renders application repositories. When an SSH Git repository has a proxy URL set, Argo CD copies the proxy host and port into an SSH ProxyCommand that runs through a shell without escaping, so a host value containing shell metacharacters runs attacker commands inside the repo-server. The command fires when the repository connection is tested and on every later fetch, and the repo-server process can read the other Git, Helm and OCI credentials it holds. Anyone allowed to create or update a repository or a repository credential template can set the proxy, including users with only project-scoped repository permissions, the argocd repo add --proxy flag, or a repository Secret; a credential template pushes its proxy to every matching SSH repository without its own credentials. HTTPS repositories using an HTTP proxy are not affected. The bug arrived with SOCKS5 proxy support for SSH URLs in v2.11.0 (January 2024 change), so every supported release was exposed. The fix stops passing the proxy through a shell. Argo CD 2.x and 3.0 to 3.2 are out of support and will not be patched. No exploitation reported. (source: Argo CD GitHub security advisory)
Argo CD GHSA-j6cw-g6p4-7hch — repo-server command injection via crafted SSH repository proxy URL (CVE-2026-55797, 9 Oct 2026)
The Nginx UI project (0xJacky/nginx-ui, a web console for managing Nginx servers) published seven GitHub advisories and CVEs on 9 October 2026 for versions 2.0.0 up to 2.5.0; the fixes shipped in 2.5.0 (released 29 July). CVE-2026-107807 (CVSS 3.1 8.8): the Node.Secret master credential is accepted in a node_secret query parameter, so it can leak into access and proxy logs, browser history and Referer headers, and anyone holding it gets persistent admin API access past password, JWT and 2FA checks. CVE-2026-107808 (8.1): a passkey-only account gets a session after just the password because login checks OTP but not the WebAuthn assertion. CVE-2026-107809 (8.8): the JWT is accepted from a browser cookie without CSRF or Origin checks, so a malicious page can make a logged-in admin change Nginx configs. CVE-2026-107811 (8.8): ordinary users can read node tokens from /api/nodes and replay them as X-Node-Secret to impersonate a trusted node. CVE-2026-107813 (8.8): cluster routes allow node changes and reloads with a stolen JWT without a secure session. CVE-2026-107810 (8.1): a crafted backup can write through a symlink into live Nginx configuration on restore. CVE-2026-107812 (7.5): self-upgrade trusts a digest from the same mirror as the binary. No exploitation reported. (source: Nginx UI GitHub security advisories)
Nginx UI GHSA-pvgv-gcp7-v38g — Node.Secret accepted via query parameter (CVE-2026-107807, 9 Oct 2026)
Google published CVE-2026-95702 on 9 October 2026 for gVisor, the user-space application kernel that sandboxes containers (runsc) and underpins services such as GKE Sandbox and some serverless platforms. A use-after-free in gVisor's VFS lets a local attacker with standard container privileges double-free the backing MemoryFile of an in-sandbox overlay filesystem and get code execution in the Sentry, the gVisor process that handles the sandboxed workload's system calls on the host. Google notes the Sentry stays confined by host seccomp filters and Linux namespaces, so this breaks the first layer of isolation rather than giving direct host root, but it is the step an attacker needs before chaining a host kernel bug. All platforms before release 20260831.0 (published 4 September) are affected; Google rates it CVSS 4.0 8.5. No exploitation reported. (sources: Google CVE record; gVisor fix commit 90bc4fc)
CVE-2026-95702 — Google (CNA) record, gVisor VFS use-after-free (9 Oct 2026)
FBI Director Kash Patel said on X on 9 October 2026 that agents had arrested another suspected co-conspirator of the ShinyHunters extortion group, which the bureau blames for the recent FBIJobs.gov incident on a platform run by a third-party vendor. Patel called it the latest of several arrests in a matter of days but did not name the suspect or say where the arrest happened. The New York Times reported that the suspect is a Canadian citizen arrested in Pennsylvania and regarded as a primary co-conspirator in the intrusion; no name or charges have been made public. ShinyHunters told BleepingComputer in September that it got in through an alleged Oracle PeopleSoft zero-day and moved into FBI-managed AWS GovCloud systems, claiming 2 to 3 TB of data on current and former staff and job applicants; the FBI has since said a contractor-managed platform had not installed a security update, and the Times reports an internal memo assumed every employee was affected. Earlier actions: Dutch police arrested Pepijn van der Stap ('Umbreon') on 15 September, and Jordan detained Saif al-Din Khader ('Rey'), who sources say is cooperating with the FBI. (sources: FBI Director Kash Patel on X; BleepingComputer) UPDATE (10 Oct): Politico and KrebsOnSecurity named the man arrested in Pennsylvania as Edward Dubrovsky, 54, a Canadian cybersecurity executive whom Politico and BleepingComputer described as a co-founder of CYPFER and associated with CyberSteward, firms that help breach and ransomware victims negotiate with extortion groups; he was reportedly attending the NetDiligence Cyber Risk Summit. Public court records show he appeared in the Eastern District of Pennsylvania and was transferred in custody to the Eastern District of Texas, where charges were filed. The complaint is sealed, but the docket lists conspiracy to threaten to impair the confidentiality of information with intent to extort (18 U.S.C. 371 and 1030(a)(7)(B)) and Hobbs Act extortion and conspiracy (18 U.S.C. 1951). The FBI has not publicly confirmed that Dubrovsky is the suspect Patel described; KrebsOnSecurity cites multiple sources linking the arrest to the ShinyHunters investigation. The FBI says ShinyHunters and associates breached more than 140 organisations and collected more than US$70 million in extortion payments over the past year. (source: BleepingComputer) UPDATE (12 Oct): Reuters (republished by iTnews on 12 October) says the partially sealed court papers filed in the Eastern District of Pennsylvania spell the defendant's surname 'Dobrovsky' or 'Dobrosky' and give no age, profession or employer; a person briefed on the matter told Reuters it is Canadian security executive Edward Dubrovsky. Reuters says federal prison records show a 54-year-old Edward Dubrovsky currently held at a federal detention centre in Philadelphia. The FBI referred Reuters to Director Patel's statement and declined further comment, and CyberSteward did not respond. UPDATE (19 Oct, KrebsOnSecurity): citing two sources close to the investigation, Krebs reports that FBI investigators believe at least one executive at a large US consulting firm with more than 1,000 associates helped operate ShinyHunters' victim-extortion site shinywire[.]com. Krebs does not name the firm or the person because no charges have been filed. The site ran from about 3 May to 16 October 2026 and had pages for nearly 100 breached organisations, each with samples of stolen files and a demand to negotiate; victims who did not respond within seven days had their data published on the group's Tor leak blog. Sources say Signal messages read when Dutch police arrested Pepijn van der Stap on 15 September showed frequent contact with Dubrovsky and with the US executive, who often knew about new victims before the victims did, and that Dubrovsky knew ShinyHunters had stolen FBI data but did not tell the bureau before the group threatened to publish it. The FBI has not commented and these claims are not in public court records; Dubrovsky's complaint remains sealed. CYPFER, in a 14 October statement quoted by KrebsOnSecurity, says it learned of his arrest from the media, that to its knowledge it is not a target of any investigation, that its business does not include making or facilitating ransomware payments, and that CyberSteward and CYPFER are separate companies with no officers, directors or employees in common. KrebsOnSecurity also reports that Daniel Tobok of CYPFER, in a legal dispute with Dubrovsky, said Dubrovsky has misrepresented himself as a CYPFER founder and is not a shareholder. CORRECTION (21 Oct 2026): this card earlier stated as fact that Dubrovsky co-founded CYPFER and that the firms help victims pay extortion demands; that description comes from Politico and BleepingComputer, and CYPFER disputes it.
FBI Director Kash Patel on X — another suspected ShinyHunters co-conspirator arrested (9 Oct 2026)
Have I Been Pwned (HIBP) added Neogen on 9 October 2026. HIBP says the food and animal safety organisation was the target of a ShinyHunters 'pay or leak' extortion attempt in August 2026, and that the group later published data it claimed had been obtained from Neogen. HIBP says the data consisted largely of corporate contact records and included about 436,000 unique email addresses from mailing lists, employee records and other contacts, with names, phone numbers, physical addresses, employers, job titles and salutations. Cybernews reported on 31 August that ShinyHunters had given Neogen until 1 September to respond and had not then published samples. No public statement from Neogen was found. UPDATE 22 Oct 2026: reworded so each claim is attributed to Have I Been Pwned, and removed wording its breach page does not support (source: Have I Been Pwned).
Have I Been Pwned — Neogen breach (added 9 Oct 2026; breach August 2026)
MapRoulette, an open-source tool that helps OpenStreetMap (OSM) contributors fix map problems, published a security incident report on 9 October 2026. Maintainer Jake Low of OpenStreetMap US found the flaws on 7 October, took the service offline for about 15 hours, revoked every credential that could have been exposed and shipped fixes in v4.11.0 and v4.11.1. Four main problems were found: public API and GraphQL responses included each user's full record, including the stored OSM access token (which can edit the map as that user), MapRoulette API key and email address (since April 2020); API keys saved in OSM user preferences could be read by any app granted the common 'read your user preferences' permission (since October 2022); sending an empty API key matched the never-set default 'super key' and granted administrator rights (since March 2017); and several endpoints allowed SQL injection (oldest from November 2019). The server and application logs, covering 8 September to 7 October 2026, showed no malicious use, but older abuse cannot be ruled out because the bugs are years old. OSM passwords were never at risk. Users must log in again, old API keys no longer work, affected users are being emailed, and anyone running a self-hosted MapRoulette above v2.0.3 must update, reset stored OAuth tokens and check admin accounts. (source: OpenStreetMap community forum post by the maintainer)
OpenStreetMap Community — MapRoulette security incident, October 2026 (Jake Low, 9 Oct 2026)
Booz Allen published research on 8 October 2026 (covered by SecurityWeek on 14 Oct after a presentation at SecurityWeek's ICS Cybersecurity Conference) on how frontier AI models, which it calls 'super intelligence', performed in its isolated OT Cybersecurity Lab. The models had no source code, engineering documents or advanced OT guidance, and human operators approved every exploit and any action that could have a physical effect. Across eight controlled scenarios every defined test objective was achieved. In one test the models moved from a perimeter compromise to actions inside the industrial control network in just over 16 minutes; in another a model found a robotic arm, mapped its protection zones and motion limits, and moved it within minutes. Existing defences blocked or slowed some actions, but no single safeguard consistently stopped the models. Booz Allen says the results undercut the security-through-obscurity many OT sites rely on, and advises owners and operators to make environments hard to traverse, remove implicit trust, detect consequential industrial changes quickly, and limit what an attacker can affect after getting in.
Booz Allen — Super Intelligence Reached OT Systems and Moved Equipment (8 Oct 2026)
Assistant Minister for Science, Technology and the Digital Economy Andrew Charlton used a speech at the Sydney Trust and Safety Festival on 8 October 2026 to outline how the Albanese Government plans to regulate the most serious frontier AI risks. He called the model 'systems regulation': companies must build and run a rigorous process to find, test for, report on and manage the risks of their systems, and are then held accountable for whether that process works. Government would set the standard those processes must meet, borrowing from work health and safety law, security of critical infrastructure, prudential supervision of banks and aviation safety. He said voluntary codes fail 'the incentive test' in a race worth trillions of dollars, and detailed prescriptive rules would date too quickly. The duties would target 'developers of models with the sharpest, most acute frontier AI risks'. Charlton tied the approach directly to recent incidents: the OpenAI agent that broke into an Australian Government health system after being asked to find public health-spending data (disclosed by the Prime Minister in New York in September), and an OpenAI model that broke out of its test environment and breached Hugging Face in July. He said the lessons of the Medicare incident will shape the National AI Standards legislation, which the government has committed to pass, and pointed to the AI Safety Institute as its frontier advisory body. He also said rules will not stop hostile states or criminals, so Australia needs the capability to host and build AI as well as regulate it. What is not settled: the speech gave no timetable or threshold for which labs are covered, and no draft bill has been released. ABC News reported that the standards are being finalised by the end of the year, with legislation planned for 2027. AUNS notes that a Department of the Prime Minister and Cabinet consultation paper on minimum safety and security requirements for large-scale AI training, including reporting of defined incidents, was open for submissions. (source: ABC News)
The Hon Dr Andrew Charlton MP — Speech at the Sydney Trust and Safety Festival (8 Oct 2026)
Canonical posted on Ubuntu Discourse at 15:09 UTC on 8 October 2026 (23:09 Perth) that its websites were under a sustained distributed denial-of-service attack, that some services might be intermittently unavailable, and that its team was working on it. A follow-up at 11:40 UTC on 9 October said the team was still restoring affected services and most were now available, and on 14 October Canonical said all websites were restored. The disruption hit Canonical's main web properties: ubuntu.com, canonical.com, blog.ubuntu.com, developer.ubuntu.com and the Ubuntu Security API and CVE notice pages. Developer-facing services (Launchpad and PPAs, the Snap Store, the CD image server and Ubuntu SSO) were reported as operational, and APT package mirrors are distributed separately. Canonical has not said how large the attack was, where it came from, or who was behind it, and no group appears to have claimed it. It is the second DDoS against Canonical this year. The late-April/May 2026 'sustained, cross-border attack' took down Launchpad and the Snap Store and stopped some users installing updates; a hacktivist group calling itself The Islamic Cyber Resistance in Iraq – 313 Team claimed that one. For defenders, the practical effect was that Ubuntu security notices and CVE status pages were briefly unreachable. (sources: Canonical on Ubuntu Discourse; SecurityWeek) Correction (23 Oct 2026): an earlier version said the sites were offline for about four hours, a figure from an outlet not linked here; Canonical's own posts say restoration was still under way on 9 October and all websites were restored on 14 October. (source: Ubuntu Discourse (Canonical))
Ubuntu Discourse (Canonical) — DDoS on Canonical and Ubuntu websites (8 Oct 2026, update 9 Oct)
