MediaTek published its October 2026 Product Security Bulletin on 5 October 2026, covering 31 vulnerabilities in its smartphone, tablet, IoT and automotive chipsets: 2 Critical, 9 High and 20 Medium. The two Critical bugs, CVE-2026-20519 and CVE-2026-20520, are out-of-bounds writes in the modem firmware caused by missing bounds checks; the CVE records say a device that connects to a rogue base station controlled by an attacker could suffer remote escalation of privilege with no user interaction and no extra execution privileges. Both affect a long list of 4G/5G modem chipsets (including the MT68xx and MT69xx Dimensity families and MT87xx/MT88xx parts) and were found internally. The High-rated issues include more modem out-of-bounds writes (for example CVE-2026-20526, which needs user interaction), out-of-bounds writes in the video decoder and encoder (CVE-2026-20586, CVE-2026-20589), a stack overflow in the Video HAL (CVE-2026-20521), and flaws in the NeuroPilot and APU AI-accelerator components. MediaTek says device makers received the patches at least two months before publication and that it is not aware of active exploitation. End users get the fixes only through their phone or tablet maker's security update, which often lands with or after the matching Android monthly patch.
MediaTek — Product Security Bulletin, October 2026 (published 5 Oct 2026)
Fortbridge published a working exploit chain on 5 October 2026 that turns an ordinary WordPress Media Library upload into code execution on the web server. WordPress hands uploaded HEIC images to ImageMagick, which decodes them with libheif. The chain first uses the derived-item and pixel-plane out-of-bounds read in libheif advisory GHSA-2jg2-4ch7-h545 (fixed in 1.23.2) to leak library and heap addresses through the JPEG thumbnails WordPress generates, then triggers the heap overflow in GHSA-x8r2-mggj-j6wr, a flaw in libheif's uncompressed (unci) decoder when the two chroma channels declare different bit depths, to hijack a C++ virtual call and run commands as the www-data PHP-FPM account. It needs a logged-in user with the upload_files capability (Author or higher by default); Fortbridge did not test guest uploads and validated it only on two exact Ubuntu and Debian stacks (6 of 8 and 22 of 24 runs succeeded). The libheif advisory, credited to Alex Thomas of Wordfence working with an agentic AI assessment framework, rates the overflow Critical (CVSS 3.1 9.8) and has no CVE yet. This is lab research, not an observed campaign. Wire: Cyber Security News 5 Oct.
Fortbridge — WordPress libheif RCE research (5 Oct 2026)
Google has temporarily stopped accepting product vulnerability submissions to its Open Source Software Vulnerability Reward Program (OSS VRP), which covers Google-maintained open-source projects such as Go, Angular, Bazel, Protocol Buffers and Fuchsia. Google says the pause is due to a significant rise in automated submissions, the vast majority of which are not valid. OSS VRP supply-chain reports (for example repository settings, GitHub Actions and access-control issues) and reports already in progress are not affected, and product vulnerabilities submitted before 1 October 2026 are still handled. Researchers can still use the Patch Rewards Program (up to US$15,000 for high-impact fixes) and the Cloud VRP for Google Cloud open-source repositories. Google says it will rework the programme and give an update in Q1 2027. Context from BleepingComputer: the OSS VRP launched in August 2022 with rewards from US$100 to US$31,337; curl ended its HackerOne bounty in January and Intel removed bounty payments in mid-September, both amid low-quality AI-generated reports. Wire: BleepingComputer 5 Oct.
Google Bug Hunters — Open Source Software VRP rules (pause notice)
Denmark's Central Person Register (CPR) administration announced on 5 October 2026 that it had found a serious security incident: by misusing a Danish company's lawful access to search the CPR system, unauthorised parties obtained names, addresses, CPR (personal identity) numbers and other details for about 8.8 million people registered in CPR. The CPR administration says its review shows the unauthorised access does not include the names and addresses of people registered with name and address protection. It has stopped the company's access and is working with specialists and authorities to map what happened; it has reported the incident to the Danish Data Protection Agency (Datatilsynet), and police are investigating with the relevant authorities. The company, the attackers and how many records were actually extracted have not been named. Separate from the DTU incident on this desk. CORRECTION (21 Oct 2026): a 12 October update naming the company whose access was abused, its owner and passwords used on its accounts has been removed until we can link a readable primary source for it. Correction (26 Oct 2026): a line quoting minister Christina Egelund to Ritzau on how long the access ran and an unlinked Cybersecurity News wire credit have been removed, because no linked source carries them. (source: CPR administration) Correction (26 Oct 2026): the Ministry of Higher Education, Research and Digitalisation's press release link now redirects to the ministry's home page and can no longer be read, so it has been removed and the card now rests on the CPR administration's own notice (5 Oct 2026). Details that only the ministry's release gave have been removed: that the ministry co-announced the incident, that CPR staff noticed irregular activity on Friday 2 October covering a period in September, the briefing of the parliamentary digitalisation committee, the ordered security review of CPR, the explanation of why the figure exceeds Denmark's population, and the authorities' warning about passwords and codes. (source: CPR administration)
CPR administration — Omfattende uautoriseret adgang til borgeres CPR-oplysninger (5 Oct 2026, Danish)
AhsayCBS is the central management console for Ahsay's cloud backup software, used mainly by managed service providers (MSPs) and system integrators. Two flaws were published on 4 October 2026 (CNA VulDB, with public exploit code): CVE-2026-105133, an authentication bypass in the checkSysPwd function of the API (CVSS 3.1 7.3), and CVE-2026-105134, an OS command injection in the Replication Receiver endpoint /rps/api/json/UpdateReceivers.do (CVSS 3.1 10.0, CVSS 4.0 9.3), where a random token can stand in for valid credentials. The CVE records list versions up to 10.3.2 and point to 10.3.4 as the fix, but Huntress said on 8 October that 10.3.4 is also vulnerable and that it has told Ahsay. Huntress first saw exploitation at 23:20 UTC on 7 October and had seen five organisations targeted by 8 October: attackers chained the two bugs to run code as NT AUTHORITY\SYSTEM, set up a malicious replication receiver, dropped a JSP webshell into the CBS web directory, ran reconnaissance, installed XMRig cryptominers disguised as Microsoft Edge, kept them running with a renamed NSSM service posing as Edge Update, loaded the vulnerable WinRing0x64.sys driver, and added an apparently AI-written PowerShell script that closes Task Manager if it stays open overnight. Primary: Huntress; wire: SecurityWeek. UPDATE 14–15 October: Ahsay published an updated critical security alert saying its earlier patches, v9.15.2.59 and v10.3.4.0, did not fully fix CVE-2026-105133 and CVE-2026-105134. Partners on v10 should apply the AhsayCBS v10.3.4.45 hotfix and partners on v7, v8 or v9 the v9.15.2.70 hotfix (both behind the partner portal), then reboot the server. Huntress says it independently verified that 10.3.4.45 blocks the initial entry point of the attack chain. CISA added both CVEs to its Known Exploited Vulnerabilities catalogue on 14 October with a 17 October deadline for US federal agencies. Wire: The Hacker News.
Huntress — Threat actors exploit critical AhsayCBS flaws to drop webshells and XMRig cryptominer (8 Oct 2026, updated 8 Oct 6pm ET)
Nikkei Inc., the Japanese media group that owns the Financial Times, said on 4 October 2026 (English notice 5 October) that a Microsoft 365 account used by one of its employees was accessed by a third party and used on 30 September to send about 9,000 spoofed emails with links to malicious websites, to staff and to news sources and others who had been in contact with several Nikkei employees. Nikkei believes recipients' names and email addresses and the content of some emails were exposed. It changed the account password, has seen no unauthorised logins since, asked recipients to delete the emails, reported the incident to Japan's Personal Information Protection Commission and is still working out the scope and the number of records involved. Group company Nikkei BP said separately on 4 October that one of its employees handed over login details to a phishing email that came from a Nikkei staff address, exposing 26 names and email addresses. Updated 6 Oct 2026: BleepingComputer (5:25 pm Perth) reports Nikkei also disclosed that an employee's Google Workspace account was accessed in late July, exposing names and email addresses of 1,646 employees and business partners but not reader or interviewee data, which Nikkei found in early August after a Google notification. (source: BleepingComputer) No attacker has been named and Nikkei has not said whether the incidents are connected. Primary: Nikkei Inc. notice.
Nikkei Inc. — Regarding information leaks and the sending of suspicious emails due to a cyberattack (5 Oct 2026; Japanese notice 4 Oct)
Citrix NetScaler Improper Restriction of Operations within the Bounds of a Memory Buffer Vulnerability. Citrix NetScaler ADC (formerly Citrix ADC) and Citrix NetScaler Gateway (formerly Citrix Gateway) contain an improper restriction of operations within the bounds of a memory buffer vulnerability that could allow for a denial of service. Apply vendor mitigations. Check the NVD record and the vendor advisory for affected versions and the patch.
BleepingComputer (4 October 2026) reports Anthropic has begun prompting Claude voice-feature users to voluntarily share voice conversations for model training. The in-product prompt asks: “Allow us to use your voice data to improve our AI models,” stating audio recordings and voice chat data help speech understanding/response, with opt-out and deletion via settings. Voice training is a separate control from Anthropic’s existing option to use chats and coding sessions for training — users can allow one path and refuse the other. Settings > Privacy shows “Allow us to use your voice data” described as applying only to approved sessions; Bleeping says the toggle appears disabled by default (not auto-enrolled). Wire-primary until Anthropic publishes a matching help-centre / privacy-policy notice URL. Distinct from desk ftc-openai-anthropic-probe and anthropic-agent-liability cards (regulatory/IPO risk). Primary wire: BleepingComputer 4 Oct.
BleepingComputer — Anthropic asks Claude users to share voice data for training (4 Oct 2026)
Have I Been Squatted researchers Ian Muscat and Leanne Briffa published research on 3 October 2026 showing two edge cases in the internationalised domain name (IDN) spoofing checks used by Chromium-based browsers such as Chrome and Edge. First, Chromium's whole-script confusable check only shows the encoded Punycode form when every character in a single-script Cyrillic label is on its list of Latin lookalikes; Cyrillic ө (a Kazakh, Mongolian and Tatar letter) is not on the list, so аррӏө.com, a lookalike of apple.com that Verisign's .com Cyrillic table allows to be registered, displays in Unicode. Other 'breaker' characters such as ү also work. Second, the top-domain comparison reduces names to a 'skeleton', but a hooked letter such as ƙ, and the bar on ө, survive as combining marks, so oƙta.com does not reduce to okta.com and no match is found. Chromium's navigation-time Safety Tips only fire for matches within one edit and for targets of five or more characters, so short brands such as Okta, Nike, Sky and VK get no near-match protection. The researchers registered 20 lookalike domains (including Cyrillic versions of openai.com, skype.com, sharepoint.com, shell.com and kaspersky.com) and say all showed in Unicode in the Chrome 154 address bar with valid certificates. They found 161,894 lookalike pairs among 733,509 IDNs in the .com zone, which are possible imitations, not confirmed typosquats. In webmail tests Gmail showed all 20 IDN sender domains in Unicode, while Outlook Web showed all of them as Punycode, even harmless ones. Chromium added one more Cyrillic character (м) to its list on 11 September, after Chrome 155 branched; earlier, Chrome 148 closed the ҏ and ӿ breakers. No CVE or Google fix for ө or ƙ has been announced, and no in-the-wild abuse is reported in the research. Wire: The Register (10 Oct).
Have I Been Squatted — Turning IDN edge cases into typosquats (3 Oct 2026)
Microsoft Threat Intelligence reported on 3 October 2026 a cluster of compromised websites that show a fake CAPTCHA or repair prompt telling visitors to open the Windows Run box, paste a copied command and press Enter. Unlike typical ClickFix lures, the page has already pre-fetched the main VBScript payload into the browser cache as a PNG-like file, so the pasted command can be short: it searches cache folders such as the Firefox profile for a file of an expected size, copies it to a temporary .vbs file and runs it through Windows Script Host with output hidden. The script gathers device details over WMI and pulls a PowerShell stage; later steps invoke .NET compilation tools, inject code into a legitimate Windows utility to steal browser-stored and device credentials, set the user's PowerShell execution policy to Bypass, unpack Python components and add a scheduled task that runs a Python payload windowlessly. Microsoft did not give victim numbers or name an operator. Wire: Cyber Security News 5 Oct.
Microsoft Threat Intelligence on X — ClickFix with browser-cache pre-fetched payload (3 Oct 2026)
NVD record CVE-2026-71885 (published 3 October 2026; CNA CVSS 4.0 9.2 Critical; CWE-287 / CWE-295) and the Legion of the Bouncy Castle advisory page: the Messaging Layer Security (MLS, RFC 9420) implementation in Bouncy Castle for Java before 1.86 never tied an X.509 credential to the LeafNode signature_key. LeafNode.verify() checked the leaf's signature against the key carried in the leaf itself, and the credential's certificate chain was stored but never parsed or compared, so RFC 9420 section 5.3's binding was not enforced. A party could present someone else's certificate as its credential and sign the leaf and KeyPackage with an unrelated key, and be accepted under that person's identity. Where a deployment publishes GroupInfo and the ratchet tree for external joins and passes external commits to Group.handle() without its own credential-admission check, an unauthenticated attacker could join as the victim, evict them, derive the current epoch, read later group messages, and send messages accepted as the victim. Deployments using only basic credentials are unaffected. Fixed in 1.86 (commit 77632a57ed; bcmls-jdk18on 1.86 on Maven Central): the leaf is rejected unless the end-entity certificate's public key equals signature_key; chain and identity validation to a trust anchor remain the application's job. Credit: Joshua Rogers and Khaled Suliman (AISLE Research). No exploitation reported; no Australian-specific notice found. Wire pickup: Forkast 4 Oct.
BleepingComputer (3 October 2026), citing TestingCatalog on X, reports Google is testing desktop-control capability in the Gemini Desktop macOS app, including a hidden “Additional sandbox options” setting. Wire description: when enabled, Gemini could read/create/modify/delete files outside explicitly connected folders, open apps, browse the web, and act through Mail/Safari/Messages without asking permission every time; UI copy says expanded access may allow actions without prior permission depending on settings. Feature is not live and Google has not publicly confirmed the rollout. Wire says Gemini would still prompt before purchases, money transfers, creating accounts, accepting legal terms, or modifying sensitive personal information. Context: Apple’s 2 Oct Full Disk Access hardening for AI-agent risk (desk apple-macos-fda-ai-agents-20261002). Wire-primary until Google publishes Gemini Desktop / computer-use docs. Primary: BleepingComputer 3 Oct.
BleepingComputer — Gemini Desktop Mac full-access sandbox options under test (3 Oct 2026)
