CISA published ICS advisory ICSA-26-279-02 on 6 October 2026 for the SMTP client application shipped with lwIP, the lightweight open-source TCP/IP stack (hosted on Savannah) that is compiled into a huge range of microcontroller and embedded products. CISA lists lwIP SMTP client 2.2.1 as affected and says the client does not check the size of its inputs, so a buffer overflow can crash the device and may allow remote code execution; it lists energy and water and wastewater as the critical infrastructure sectors and says deployments are worldwide. CVE-2026-15340 was published to the CVE list on 9 October with a CVSS 3.1 score of 9.8 (CVSS 4.0 9.3). The fix, credited to xchglabs and committed to lwIP's git repository by maintainer Simon Goldschmidt on 12 May 2026 as 'smtp: fix server-driven AUTH line overflow into tx_buf' (bug #68313, commit 614420f), changes only src/apps/smtp/smtp.c, which means the overflow is triggered by the mail server's side of an AUTH exchange and only matters for firmware that builds and uses the SMTP client module. CISA's decision data marks exploitation as proof-of-concept, with no reports of attacks. Because lwIP is embedded inside vendors' firmware, most owners cannot patch it themselves and need a firmware update from the device maker. Primary: CISA advisory; vendor: lwIP fix commit.
wolfSSL released wolfSSH 1.6.0 on 6 October 2026 with five security fixes. CVE-2026-16516 (Critical per wolfSSL): the client did not check that the ECDSA curve in a server's host key matched the negotiated algorithm, so a man-in-the-middle could swap in a key on another curve and pass signature verification with its own private key; it also needs the application to use a lax public-key check callback. Affects all versions through 1.5.0. CVE-2026-83540 (High): wolfSSHd on Windows shared one authentication context and its logon token across concurrent connections, so a user with a valid account could end up logged in as another, more privileged user (1.4.15 to 1.5.0; non-Windows builds unaffected). Medium: CVE-2026-84897 lets an unauthenticated client make a server run client-side DH group-exchange handling and costly primality checks (about half a second of CPU per 1 KB packet); CVE-2026-81535 admits forwarded-tcpip channels without the forwarding policy callback in --enable-fwd builds; CVE-2026-83742 is an SFTP path bug in wolfSSH_RealPath() that writes one NUL byte past a stack buffer and can crash the process. 1.6.0 also turns on strict key exchange (Terrapin protection) by default, requires RSA user keys of at least 2048 bits and limits failed logins to six. wolfSSH is mostly found embedded in devices and firmware, so fixes arrive through vendor updates. No exploitation is reported. Primary: wolfSSH GitHub release notes; wire: Cyber Security News.
wolfSSL — wolfSSH v1.6.0-stable release notes (6 Oct 2026)
Gitea released 28.0.0 on 30 September 2026 (the project has dropped the old '1.' prefix) with 20 security fixes, then 28.1.0 on 6 October with nine more. The most serious, CVE-2026-103059 (CVSS 9.1 as reported by Cyber Security News), affects instances using Gitea's built-in SSH server: public keys were looked up with a case-insensitive SQL LIKE, so a forged case-variant RSA key whose private key the attacker controls could be matched to another user's account. Keys are now matched by fingerprint. Other 28.0.0 fixes close several ways for repository migrations, mirrors and push mirrors to reach internal hosts despite the outbound allowlist (DNS rebinding, multiple DNS answers and approved-domain IP skips, including CVE-2026-70357, CVE-2026-101027, CVE-2026-101029 and CVE-2026-89430); Gitea now sends Git network traffic through an internal proxy that enforces the rules at connect time. Gitea Actions fixes stop cancelled-then-rerun fork pull request runs from reaching self-hosted runners without approval (CVE-2026-104632, CVE-2026-104626) and stop a maintainer's event from running an untrusted contributor's workflow (CVE-2026-94205). There are also stored XSS fixes (container registry blobs, CVE-2026-103667) and a duplicate Git tree entry check that hid files from review (CVE-2026-95106). 28.1.0 adds fixes for push mirror API permission checks (CVE-2026-97208, CVE-2026-86684), repository media stored XSS (CVE-2026-96594) and an OAuth2 refresh grant that accepted access tokens (CVE-2026-101023). No exploitation is reported. Upgrading changes egress settings (set EGRESS_MODE = strict for deny-by-default) and needs Git 2.25 or later, so read the release notes first. Primary: Gitea blog; wire: Cyber Security News.
Gitea blog — Gitea 28.1.0 is released (6 Oct 2026)
Elastic posted 14 advisories (ESA-2026-185 and ESA-2026-187 to 199) on 6 October 2026. The highest-rated, ESA-2026-187 / CVE-2026-102406 (CVSS 3.1 8.8), is in Kibana's Fleet package installation: a user who has been given Fleet privileges to install custom (uploaded) integration packages, but no direct Elasticsearch admin rights, can claim a data stream identifier already used by another user or team in the same Kibana deployment. Fleet then applies the attacker's index and ingest-pipeline settings, so newly ingested data flows through infrastructure the attacker controls and stops reaching its intended destination. Elastic warns the interception can continue after the malicious package is removed, so affected infrastructure must be checked and repaired separately. It affects Kibana 8.14.0 to 8.19.21, 9.0.0 to 9.4.6 and 9.5.0 to 9.5.3, self-managed and Elastic Cloud Hosted, where delegated users can upload custom packages. Other notable fixes: ESA-2026-199 / CVE-2026-103009 (7.1), a cross-cluster search authorisation bypass that only affects clusters acting as a fulfilling cluster under Remote Cluster Security 2.0; ESA-2026-197 / CVE-2026-103007 (7.2), privilege escalation through the delegated manage_roles privilege when it uses wildcard or regex index patterns; and ESA-2026-193 / CVE-2026-102412 (6.5), where limited Fleet users could read Fleet Server host TLS private keys (Kibana 9.3 to 9.5). The rest are mostly authenticated denial-of-service bugs in Elasticsearch, plus an Elastic Endpoint crash loop on Windows hosts with Chinese, Japanese or Korean locales that can switch off Elastic Defend protection. Elastic does not report exploitation. Primary: Elastic security announcements.
ABC News reported on 6 October 2026 that the Australian Competition and Consumer Commission received 138 scam reports involving LinkedIn in July and August 2026, with reported losses of up to $254,449. The pattern is recruitment fraud rather than a platform breach: fake job ads, cloned profiles of real recruiters and employees (one jobseeker was approached in the name of a real Aurecon staff member, and Aurecon confirmed it had not contacted him), and offers that end in an upfront fee. A common version, described by Contract Services Australia managing director Mark Hopcroft, is a 'recruiter' who says your CV fails the employer's keyword screening and then offers their own HR specialist to fix it, in his case for about A$8,600 (US$6,000); he only caught it because the role was not on the company's own careers site. Users say approaches rise sharply after switching a profile to 'open to work'. LinkedIn's Job Search Safety Pulse survey found about 16 per cent of Australian respondents say they have fallen for a job scam (25 per cent of Gen Z), 61 per cent have seen an ad they suspected was fake, and nearly half say cost-of-living pressure makes them take more risks. ANZ warned last month that realistic job scams have become a common impersonation scam. Practical checks: confirm any role on the employer's own website, contact the company through a number you look up yourself, and never pay for CV writing, training or equipment to get a job. Report to Scamwatch and, if money was sent, to your bank straight away.
ABC News — Jobseekers exploited by recruitment scammers on LinkedIn (6 Oct 2026)
SOCRadar's Threat Research Unit published research on 6 October 2026 into CyberXero, a Russian-speaking, financially motivated initial access broker that pairs common attack tools with an AI orchestration layer on its own servers. Everything surfaced through one mistake: an open directory served the actor's live working folder, more than 90,000 files including AI session logs, scripts with plaintext tokens and stolen data, and the actor stayed active while researchers watched. On one workstation it configured up to 51 Claude Code agents for discovery, password testing, exploitation and data theft; a second setup connected PentAGI, an open-source AI penetration-testing framework, to a Cobalt Strike team server through an AI provider's API, with model choice and token budgets set per task. Session logs show the operator telling the model the targets were its own systems under authorised testing and, when refused, opening a fresh session with the same cover story; some refusals held, including requests to install a backdoor, disable a firewall, move across a network and plant a webshell. The broad campaign used an internal wp2shell package that abuses the WordPress REST API batch endpoint to inject SQL, create a rogue administrator and drop a WSO-family webshell, and it also hit Magento and used Support Board CVE-2026-4815 within 30 days of disclosure; one automated run scanned 4,708 targets, found 429 reachable WordPress admin panels and placed 32 shells in 61 seconds. A separate hand-picked pipeline mapped seven Ukrainian energy and utility organisations, including the national transmission operator; four Ukrainian organisations had confirmed data theft, a Kharkiv district-heating provider lost 564,073 subscriber records, and data on more than 628,000 Ukrainians was found. More than 40 organisations were affected worldwide, with activity also seen in Poland, China and Pakistan; SOCRadar found no direct proof of an access sale. Infrastructure was first seen in July 2026 across eight nodes in European hosting and Tencent Cloud. Primary: SOCRadar; wire: Cyber Security News (7 Oct).
SOCRadar — CyberXero: an AI-augmented initial access broker targeting Ukrainian critical infrastructure (6 Oct 2026)
SonicWall published advisory SNWLID-2026-0017 on 6 October 2026 covering four flaws in Secure Mobile Access (SMA) 1000 series appliances, physical and virtual SMA 6210, 7210 and 8200v. The worst, CVE-2026-102255 (CVSS 10.0), sits in the Appliance WorkPlace interface: an unintended alternate access path lets the appliance act as a forward proxy, so a remote attacker with no login can make it send requests on their behalf, reach internal functions and perform unauthorised operations (CWE-918 server-side request forgery and CWE-441 unintended proxy). The other three need an administrator account: CVE-2026-102256 (7.8) is an operating-system command injection that can give remote code execution, CVE-2026-102257 (7.2) is a Zip Slip path traversal in the Appliance Management Console (AMC) that can also lead to code execution, and CVE-2026-102258 (5.5) is stored cross-site scripting in AMC. SonicWall says it has no evidence any of the four are being exploited, lists no workaround, and says SSL-VPN on SonicWall firewalls and the SMA 100 series are not affected. Benoît Sevens of Anthropic reported the SSRF and command-injection bugs; Brian Mariani reported the Zip Slip through Trend Micro's Zero Day Initiative and the XSS through DigitalCanion SA. Important for anyone who patched last month: the builds that fixed the exploited September zero-days CVE-2026-83548 and CVE-2026-83549 (12.4.3-03526 and 12.5.0-02952) are the last affected builds in this advisory. Shadowserver tracks more than 400 internet-exposed SMA1000 appliances, and CISA has added 19 SonicWall flaws to its exploited list in four years, so expect attention. Primary: SonicWall PSIRT advisory; wires: BleepingComputer and Cyber Security News (7 Oct). UPDATE (9 Oct): BleepingComputer reported on 9 October that Previdian's honeypot network has seen exploitation attempts consistent with CVE-2026-102255: crafted OPTIONS requests to the WorkPlace Extraweb interface tried to reach the appliance's internal CouchDB service on 127.0.0.1:5984 and call a design document's _rewrite function using admin:admin credentials, a different technique from the July and September SMA1000 SSRF attacks. Previdian has not established whether any attempt succeeded, and SonicWall's advisory had not marked the flaw as exploited. Shadowserver tracks more than 400 SMA1000 appliances exposed online. UPDATE (13 Oct): The Hacker News reported on 12 October that the first exploitation attempts were seen by two threat intelligence firms, Defused Cyber and Previdian, on 8 October, two days after the fix shipped. Previdian has counted 135 attempts so far from two IP addresses located in the United States; those are sensor hits, not confirmed compromises, and the IP locations say nothing about where the attackers are. SonicWall had still not updated its advisory to mark the flaw as exploited. Earlier SMA1000 zero-days were used to steal credentials, session databases and TOTP multi-factor seeds before moving into internal networks, so treat an unpatched appliance as a possible foothold.
SonicWall PSIRT — SNWLID-2026-0017, SMA1000 series multiple vulnerabilities (6 Oct 2026)
The FBI and the US Secret Service published joint cybersecurity advisory JCSA-20261006-01 on 6 October 2026, warning that FortiBleed is an active, worldwide campaign against internet-facing Fortinet FortiGate firewalls and SSL VPN gateways. FortiBleed is not a single new software bug: the operators use credential stuffing and password spraying with logins from earlier Fortinet leak dumps and infostealer logs, then take password hashes from devices that still store administrator passwords with legacy SHA-256 and crack them offline on a GPU cluster run with Hashcat and Hashtopolis. SOCRadar has verified more than 86,644 compromised devices in 194 countries. The workflow came to light because the operators left their own backend server open; it shows them filtering out honeypots, ranking victims by revenue and network layout, creating new administrator accounts on the firewall to keep access, enumerating Active Directory and spraying passwords inside the network, then selling working VPN access. The agencies say some victims have been locked out after the attackers deleted or changed the original admin accounts, so recovery can take more than a patch and a password reset, and that the access has been used as an entry point for ransomware affiliates (wire reports name INC/Lynx and Payload). The advisory lists account names seen on victim devices, including forticloud-sync, forticloud-tech, fortiAdmin, adminin, districtadmin and system_config, and infrastructure including a command-and-control server at 45.154.12[.]132 and a Hashtopolis host at 85.11.187[.]8. Primary: FBI/USSS joint advisory on IC3; wires: The Hacker News and Cyber Security News (7 Oct).
FBI and USSS — Joint Cybersecurity Advisory JCSA-20261006-01: FortiBleed operations continue targeting exposed systems leading to reports of lockouts (6 Oct 2026, PDF)
Progress published a critical security bulletin on 6 October 2026 for CVE-2026-91140, an OS command injection flaw in the GenAI agent and prompt definitions for the DataDirect Autonomous REST Connector (ARC) AI Model Generator, distributed through the public progress/datadirect-arc-ai-model-gen GitHub repository as an Early Access feature. The generator takes a filename value from the OpenAPI or Swagger document it is given and uses it in a shell command for temporary-file cleanup without proper validation or quoting, so a document with shell metacharacters in that value runs commands on the developer's machine or the CI runner when someone invokes the generator. Progress rates it CVSS 3.1 9.6 (network, no privileges, user interaction required). The affected files are ARCGenAI-Generator.agent.md 2.0, ARCGenAI-Generator.prompt.md 1.0 and ARCGenAI-EntityGen.agent.md 1.0; all three are updated to 2.1. There is no installer or migration: the fix is pulling the latest definitions. Progress also tells anyone who already ran the agents on untrusted or third-party API specifications to review those workspaces and CI environments for unexpected files or commands, since the flaw produces no product error message. CISA's assessment records no known exploitation. Primary: Progress bulletin and the GitHub fix commit; wire: Cyber Security News (7 Oct).
OpenSSH 10.6 / 10.6p1 was released on 6 October 2026 with a batch of security fixes for both the ssh client and the sshd server. The headline change disables the LZ77 dictionary coder in compression: researchers Fabian Bäumer and Marcus Brinkmann showed in "Crossing the Streams" that, when compression is on, all channels in one SSH connection share one compression dictionary, so an attacker who can feed chosen text into one channel and watch ciphertext lengths can recover secrets carried in another channel. Compression still works but is less effective. The sftp client now validates paths returned by a server more strictly, so a malicious server can no longer steer a recursive download into writing outside its target folder (reported by Junghoon Cho). The ssh client now refuses destination usernames containing $ or \ on the command line, because usernames from untrusted sources could reach a shell through ProxyCommand or Match exec (reported by KeenLab Tencent); usernames set with the User directive in config files are not restricted. Other fixes cover GSSAPI credentials from a failed attempt persisting into a later login, the authorized_keys "restrict" keyword not applying to tunnel forwarding, compressed packets inflating past the size limit, and a root-privileged session process on old platforms without file-descriptor passing (GatewayPorts and StreamLocalForwarding are now forced off there). The OpenSSH team says it is getting many AI-assisted bug reports, has seen AI-found bugs rediscovered independently, and will ship releases more often. The release notes assign no CVE numbers or CVSS scores, but MITRE published CVE records for the fixes on 6 and 7 October. UPDATE 15 October: Red Hat tracked the root-retaining session-process issue as CVE-2026-110929 (Important, draft CVSS 3.1 8.1); it has since rejected that ID as a duplicate of CVE-2026-106589, which it rates Low (draft CVSS 3.1 2.9). An authenticated user on an affected build can act as root, including making privileged socket connections and binding forwards to low-numbered ports. Red Hat says Red Hat Enterprise Linux, and Linux generally, is not affected because the post-authentication process drops to the logged-in user there. The flaw applies to QNX 6, SCO OpenServer 5 and OpenSSH builds made with --disable-fd-passing, which should upgrade to 10.6. Primary: OpenSSH 10.6 release notes; wire: Cyber Security News (7 Oct). Correction (22 Oct 2026): this card gave the root-retaining session-process flaw as CVE-2026-110929 with Red Hat's draft score of 8.1 (Important) and said the 10.6 fixes had no CVEs. Red Hat has rejected CVE-2026-110929 as a duplicate of CVE-2026-106589, which it rates Low (draft CVSS 3.1 2.9), and MITRE published CVE records for the 10.6 fixes on 6 and 7 October. (source: Red Hat CVE database)
OpenSSH — Release notes, OpenSSH 10.6/10.6p1 (6 Oct 2026)
MVSEP, an online service that separates music and voice tracks, published a security incident notice (last updated 6 October 2026) saying an attacker was in its servers between 4 and 6 October and could read its database and stored files. Automated probing began on 4 October; at about 01:30 UTC on 5 October the attacker abused a flaw in how the website read one of its browser cookies to run commands on the web server, found login details for MVSEP's other servers and signed in to them as an administrator. The 5 October database outage was the attacker restarting the database. MVSEP fixed the flaw on all servers at 03:25 UTC on 6 October, removed the access, moved servers to key-only logins and replaced its encryption key, database and payment-provider keys, and Google, GitHub, Google Drive and Yandex Disk credentials. It is treating everything as exposed: names, email addresses, sign-in method, plan and credit balance; passwords as salted bcrypt hashes; API keys, which were stored as-is and work until replaced; processing history including file names, transcriptions, job IP addresses and webhook URLs; audio uploads still on the servers; payment records (card details are entered on Paddle and YooKassa pages and never reached MVSEP); support tickets; and cloud-storage tokens, now revoked. All saved logins were signed out. MVSEP has not said how many users are affected. Primary: MVSEP incident notice.
MVSEP — Security incident: 4–6 October 2026 (last updated 6 Oct 2026)
Advantest Corporation, a Japanese maker of automated test equipment for the semiconductor industry, has begun notifying people that their personal information was taken in the ransomware attack it disclosed in February 2026. An attacker broke into its network on 15 February and deployed ransomware; at the time the company could not say whether customer or employee data was affected. In a notification letter dated 6 October 2026, Advantest says an unauthorised third party accessed its systems and extracted data from its servers, including the recipient's personally identifiable information. The letter does not say how many people are affected or whether they are customers, employees or partners, and BleepingComputer had no answer to those questions at publication. Advantest says it has no information that the data has been leaked or misused, and is offering 18 months of identity, credit and web monitoring through Kroll, with enrolment open until 4 January 2027. BleepingComputer found no public claim by a ransomware group. Source: BleepingComputer (7 Oct), which quotes the notification; Advantest's own notice is not yet linked publicly.
BleepingComputer — Advantest confirms personal information stolen in ransomware attack (7 Oct 2026)
