AI Weekly Malaysia

Epic, which makes the MyChart patient portal used to maintain over 320 million patient records in the US, has paused most of its product development for roughly six weeks to fix security bugs, per founder and CEO Judy Faulkner speaking to Modern Healthcare. The flaws surfaced after a deployment of Anthropic's frontier cybersecurity model, Mythos, and chief security officer Stirling Martin told The Times that some customer configurations of MyChart could let outsiders read patient records without leaving any entry in the software's logs. Martin said the model did not establish whether records could also be altered undetected, but Epic judged the risk serious enough to remediate; TechCrunch notes Epic has not disclosed the nature of the bugs.

Why: The concrete lesson is the logging gap, not the vendor: a read of patient records that leaves no trace in application logs defeats detection and audit entirely, and that class of bug is exactly what an AI security model found here at scale. If you ship anything with a permission model — patient data, tenant data, customer records — test whether privileged or misconfigured access paths produce an audit entry, and treat 'no log line' as a bug of its own. Also note the release-planning implication: a six-week freeze on most product development is what a serious finding costs, so teams running continuous release trains should decide in advance what triggers a stop-ship versus a patch-forward.

Researchers from VUSec and Scuola Superiore Sant'Anna disclosed a new Spectre-v2 variant called Branch Target Reuse (BTR), which exploits stale indirect branch prediction entries that survive JIT code cache rewrites, creating a transient execute-after-free primitive. They confirmed it affects SpiderMonkey (Firefox's JIT), GraalVM, and the Linux kernel's cBPF JIT, with different exploitability and leakage rates across the three. Two end-to-end Linux kernel proof-of-concept exploits recovered the root password hash within minutes on a fully patched Intel system with default protections enabled. The text names no CVE, no vendor patch, and no mitigation.

Why: There is no patch or CVE in this disclosure, so the only decisions available to you right now are posture ones: if you run multi-tenant Linux hosts, shared CI runners, or container platforms where untrusted code and your secrets coexist on the same CPU, this is a same-machine leak path that default protections did not stop in the researchers' test. The kernel cBPF JIT can be turned off (net.core.bpf_jit_enable=0) as a blunt lever, but the same stale-branch-target class also hits browser and JVM-style JITs you can't disable for your users, so watch for vendor guidance rather than assuming your current hardening covers it.

A The Hacker News DevSecOps/patch-management piece argues that financial services' long-standing habit of accepting a vulnerability backlog as a stability tradeoff no longer holds, because frontier models like 'Mythos' can read code and chain dormant weaknesses faster than teams can investigate and patch. It cites two figures: vulnerability exploitation has overtaken phishing as the leading initial access vector in financial services, and more than half of financial services vendors carry at least one high-severity CVE. The article names no vendor tooling, no version numbers, no remediation steps, and gives no methodology or source for either statistic.

Why: If you sell or integrate software into banks, insurers, or asset managers, this is a signal that your dependency-patching cadence is becoming a procurement and contract question rather than an internal hygiene one — 'we'll fix it in 18 months with a compensating control' is the exact posture the piece says is being repriced. Treat it as direction, not evidence: the two headline numbers (exploitation beating phishing; >50% of FS vendors with a high-severity CVE) are stated without a cited report, so don't quote them in a customer deck or a risk assessment until you find the underlying data.

CISA added CVE-2026-76504, a CVSS 9.8 authentication bypass in Cisco Catalyst SD-WAN Manager, to its Known Exploited Vulnerabilities catalog on Wednesday after Cisco confirmed active exploitation in September 2026. The flaw is a hex/URI-encoding handling bug: a crafted HTTP request to the API lets an unauthenticated remote attacker act as the admin user. Cisco published IoCs but not victim counts or attribution, and U.S. federal civilian agencies had until October 3, 2026 to patch — a two-day window. watchTowr's Jake Knott noted eight Cisco SD-WAN CVEs have hit KEV in 2026 alone.

Why: If you or a client run Cisco Catalyst SD-WAN Manager, this is a same-day patch plus log check: grep /var/log/nms/containers/service-proxy/serviceproxy-access.log and /var/log/nms/vmanage-server.log for j_security_check calls from unknown IPs and for usernames starting with 'viptela-reserved-'. If you don't run that appliance, nothing here changes your week — it is enterprise network gear, not developer tooling, and the useful signal is the pattern (eight SD-WAN CVEs on KEV this year) for anyone doing MSP or enterprise infra work.

Attackers are exploiting CVE-2026-88771, a CVSS 9.5 pre-authentication command injection flaw in Citrix NetScaler ADC and NetScaler Gateway, to drop web shells and stage configuration data. LevelBlue's THOR team, analyzing activity across multiple customer environments, found authentication events with attacker-controlled usernames containing 'pitboss' and 'NSPPE' strings, plus payload fetches via curl/wget from IPs including 64.94.85[.]67, 31.56.197[.]72 and 23.27.143[.]20. Second-stage payloads include a Perl script (update_c08937.pl) that edits /flash/nsconfig/ns.conf to create a local account named sec_monitor with the superuser role, and a Python script (main.py) that opens a reverse shell to 45.141.21[.]130:443 and kill -9's processes tied to /var/python/bin/customsnmpd. The disclosure follows reports that NCSC-NL pre-notified Dutch organizations and urged shutting appliances down; no attribution is given. The excerpt is truncated, so the 'CSS-like URL' web shell detail in the headline is not substantiated in the text provided.

Why: Concrete action only if you actually run NetScaler ADC or Gateway (common in enterprise edge/VPN setups, rarely in a small Malaysian SaaS stack) — if so, patch per vendor guidance and hunt your auth logs for usernames containing 'pitboss' or 'NSPPE', check for a new local account named sec_monitor, and block egress to the four listed IPs. If you don't operate NetScaler, the takeaway is narrower: a pre-auth 9.5 with active exploitation and named IOCs is a template for how fast edge appliances get turned into superuser backdoors, so verify whether any appliance in your dependency chain is NetScaler before spending time on this.

Microsoft Security Research documented exploitation of CVE-2026-73570 (CVSS 8.9), an unauthenticated OS command injection in Zimbra Collaboration Suite that is triggerable via a crafted SMTP request, but only when SNMP notifications are enabled and the optional zimbra-snmp package is installed. Post-exploitation activity between July 20 and August 13, 2026 included JSP web shells, reverse shells, privilege escalation, memory-backed execution, and collection of email, authentication and mailbox data. Zimbra patched the flaw in version 10.1.20 in July 2026; CERT Polska flagged active exploitation in August 2026 and CISA added it to the KEV catalog with an August 24, 2026 federal remediation deadline.

Why: The reachability precondition is the decision point: if you or a client host Zimbra, check whether zimbra-snmp is installed and SNMP notifications are on - if not, this CVE is largely unreachable for you, and if you don't need it you can remove the package. If it is installed, confirm you are on 10.1.20 or later (patch shipped July 2026, before public disclosure on August 13) and grep /var/log/zimbra.log for suspicious service restarts plus temp and webapps directories for dropped files. For most Malaysian builders who don't self-host mail, this is not something to act on.

Google's Mandiant Consulting and Threat Intelligence Group observed threat actors in September 2026 exploiting CVE-2026-88772, a CVSS 9.5 memory overflow in the DTLS record parsing of the NetScaler Packet Processing Engine (NSPPE) in Citrix NetScaler ADC and Gateway appliances. Malformed or fragmented DTLS record headers corrupt heap memory and divert control flow to shellcode with root privileges on the underlying FreeBSD platform, bypassing authentication entirely. Post-exploitation, attackers modify httpd.conf so .deb files are handled as PHP, stage web shells in /netscaler/gui/vpn/scripts/linux, and deploy WHIPSHOT (PHP web shell hiding Base64 C2 in native HTTP headers) plus SLAPSHOT (a Python tunneler proxying into internal networks for reconnaissance and credential theft).

Why: Only relevant if you, a client, or a vendor-managed environment actually runs NetScaler ADC or Gateway as an edge/VPN appliance: this is pre-auth root, so an unpatched box is a direct path to internal credential theft, and the httpd.conf change treating .deb as PHP plus shells under /netscaler/gui/vpn/scripts/linux are concrete detection artifacts to check. Everyone else has nothing to change here. Note the reported targeting is organizations in North America and Europe across government, financial services, technology, education, and legal sectors - the text gives no Malaysia or Southeast Asia angle.

Kiteworks (formerly Accellion) asked customers to take systems offline for nine hours and shut down the environments it hosts for them after receiving intelligence about a potential imminent attack; the precautionary window was lifted on September 27, 2026. During that shutdown the company found a previously unknown critical vulnerability confined to a capability enabled for less than 1% of its customer base, developed and deployed a fix inside the window, and added an extra protective layer across all environments. No exploitation has been observed, other Kiteworks products are unaffected, and the flaw has no CVE identifier or public technical detail as of writing.

Why: Only teams running Kiteworks' secure file transfer product need to act, and the action is narrow: bring the system back online now that the threat window closed. For everyone else the takeaway is contractual rather than technical - a vendor can require nine hours of production downtime on short notice and disclose the underlying flaw with no CVE and no exploit detail, so if your business depends on a hosted file-transfer or document-sharing vendor, this is the case study for what your SLA and your own data-egress plan need to cover.

CISA added CVE-2026-104286 (CVSS 9.8), a path-traversal (CWE-22) plus NULL-byte (CWE-158) flaw in Fortinet FortiMail, to its Known Exploited Vulnerabilities catalog on October 1, 2026 after confirming active exploitation. Crafted HTTP/HTTPS requests let unauthenticated attackers write arbitrary files on the underlying system; affected branches are 8.0.0-8.0.1, 7.6.0-7.6.6, 7.4.0-7.4.8, and 7.2.0-7.2.9, with fixes not yet shipped for several of them. Fortinet's listed indicators of compromise include two IPs (79.141.169.187, 45.129.0.192) and newly added files such as /data/etc/ld.so.preload and /data/bin/webconsole.

Why: This is only actionable if you or a client actually run a FortiMail gateway, and the operational catch is that some branches have no patch yet: 7.2.x must move to the 7.4 branch, while 8.0.x, 7.6.x, and 7.4.x are told to wait for 8.0.2, 7.6.7, and 7.4.9 respectively. Until then the documented workarounds are disabling the IBE feature via 'config system encryption ibe / set status disable' and removing the management interface from internet exposure. The added /data/etc/ld.so.preload file is a persistence mechanism worth grepping for on any affected appliance, and FCEB agencies were given a patch deadline of October 4, 2026. Everyone else in this audience can skip it.