AI Weekly Malaysia

A critical unauthenticated SSRF vulnerability in MLflow (CVE-2026-64849, CVSS 9.3) is being actively exploited in the wild within hours of its CVE assignment on August 17, 2026. Attackers are scanning for exposed MLflow Tracking Servers and abusing the model-registry webhooks to proxy requests to cloud metadata endpoints, exfiltrating cloud credentials and secrets. The flaw affects versions prior to 3.15.0 and bypasses earlier SSRF fixes due to how MLflow handles web redirects.

Why: If you run MLflow Tracking Server exposed to the internet—especially on AWS, GCP, or Azure—patch to 3.15.0 immediately, rotate any cloud credentials that may have been exposed via metadata endpoints (169.254.169.254), and audit logs for unexpected webhook-triggered outbound requests. This is not theoretical: watchTowr honeypots caught indiscriminate scanning starting the same day the CVE was published.

SvelteKit 3.0's release candidate promotes 'remote functions' from experimental status (introduced in 2.27) to equal footing with traditional load functions, enabling type-safe RPCs directly inside individual page components without full page refreshes. A cited benchmark shows SvelteKit's SSR returns HTML payloads three times smaller than Next.js for an equivalent product page.

Why: If you're choosing a full-stack JS framework for a new project, SvelteKit 3's remote functions eliminate the boilerplate of manual data-fetching hacks while preserving end-to-end type safety — a concrete DX advantage over Next.js patterns. The 3x smaller SSR payload benchmark is worth validating against your own pages if performance is a selection criterion.