AI Weekly Malaysia

GitHub Copilot Autofix introduced a script injection vulnerability into Snowflake's snowflake-connector-net GitHub Actions workflow on June 18 by removing an existing sanitized input pattern and replacing it with direct string expansion in a shell script. Five days later, Wiz's autonomous AI red agent found the bug during a routine public repo scan, exploited it by crafting a GitHub issue title that exfiltrated Jira credentials via an out-of-band callback, and gained read access to Snowflake's engineering, security compliance, and bug bounty projects. Snowflake patched the same day Wiz reported it and rotated credentials the next day, confirming a five-day exposure window with no unauthorized access beyond Wiz.

Why: If you use AI coding assistants that auto-fix or auto-generate commits, you need to treat their output as untrusted code that can remove existing security sanitization patterns — not just as suggestions to eyeball. This incident shows an AI removing a working input sanitization pattern and replacing it with a vulnerable one, which then sat in a public repo for five days undetected by human review. Audit AI-generated diffs for security regressions in CI/CD workflows, especially in GitHub Actions run: blocks where shell injection is possible, and consider running automated security scanning on every commit rather than relying on human review.

Linux 7.2 is released with Torvalds acknowledging that AI coding tools have increased contribution volume to the point where releases are messier but delaying is no longer viable — 'If I delayed releases for that reason we'd probably never have a release at all.' The kernel adds Cache Aware Scheduling for manycore chips like AMD EPYC 5 and Intel Xeon 6, Apple M3 support, and next-gen AMD/Intel/Nvidia chip readiness, while dropping AppleTalk and old ISA/PCMCIA ARCNet adapter support.

Why: Torvalds explicitly attributing larger, messier release cycles to AI-assisted contributions is a concrete signal that AI coding tools are now reshaping even the most rigorous open-source development process — if you maintain or contribute to shared codebases, expect review burden and revert frequency to rise. On the infrastructure side, Cache Aware Scheduling on EPYC 5 and Xeon 6 means workloads on those chips should see better cache utilization without application changes, worth benchmarking if you run dense multi-core workloads.

Rupert Goodwins observes that Microsoft's monthly Windows security fixes jumped from 60-90 last year to 600+ in July 2026, with Oracle and Linux on similar trajectories. He attributes this to two AI-driven forces: LLMs aggressively surfacing buried bugs in legacy codebases, and LLM-written code introducing new defects into production under deadline pressure. He argues the patch explosion may not subside soon because newer models will find new bug classes, release pressure persists, and adversaries are using the same tools.

Why: If you ship AI-assisted code, expect your patch and regression workload to rise, not fall, in the near term. The 600+ fixes/month figure signals that AI bug-hunting is exposing a backlog you may inherit as dependencies get patched rapidly—plan for more frequent dependency updates and test for patch-induced side effects rather than assuming stability.