LIVE · cybersecurity feed
Live wire
Malware Hijacks Android Car Head UnitsCritical Flaw in NASA/JPL Open-Source Spacecraft Command Software Allowed Unauthenticated Command ExecutionCVE-2026-73570 · U.S. CISA adds Zimbra Collaboration Suite (ZCS) flaw to its Known Exploited Vulnerabilities catalogCVE-2024-3094 · Connecting the Dots: Securing the Overlooked Corners of the Software Development Lifecycle (SDLC) Supply Chain14 Trojanized npm Packages Drop RedC2 4.0 Linux Backdoor With AI-Assisted C2Hundreds of leaked AWS keys give full control over corporate accountsAndroid Car Malware Spreads Through Built-In Updaters for Ad Fraud, Proxy BotnetMalware injected into popular Rust packages to steal developer credentialsSix Maximum-Severity Flaws Found in Cisco ProductsCritical Isolated-vm Vulnerability Leads to RCE on Host
vulnerabilitycritical

CISA warns of hackers exploiting critical MLflow vulnerability

The Cybersecurity and Infrastructure Security Agency (CISA) warned federal agencies that threat actors are now exploiting a critical vulnerability in the MLflow open-source AI engineering platform. [...]

zeroday.news ·

The Cybersecurity and Infrastructure Security Agency (CISA) has issued a warning to federal agencies regarding active exploitation of a critical vulnerability in MLflow, an open-source AI engineering platform. The flaw, identified as CVE-2026-64849, is a DNS-rebinding server-side request forgery (SSRF) bypass that affects MLflow's outbound webhook delivery.

MLflow, which is backed by the Linux Foundation and boasts over 30 million monthly downloads, is widely used for developing and monitoring AI applications, including large language models (LLMs). The vulnerability was patched in version 3.15.0.

According to MLflow's security team, the default MLflow Tracking Server, when configured without authentication and using a default SQLite backend, exposes the model-registry webhooks API. This includes a synchronous POST /api/2.0/mlflow/webhooks/{id}/test endpoint that returns the upstream response status and body to the caller.

This configuration allows an unauthenticated attacker who can reach the tracking server to force the server to issue HTTP requests to arbitrary internal, loopback, or cloud-metadata endpoints. The attacker can then read the responses via the /test endpoint. This capability can be leveraged to access cloud instance metadata, such as AWS IMDS IAM credentials, internal-only administrative services, or to perform internal port and host scanning.

Successful exploitation of CVE-2026-64849 can lead to the theft of cloud credentials, including AWS Identity and Access Management (IAM) credentials, through low-complexity attacks.

CISA added the vulnerability to its catalog of actively exploited flaws on Wednesday, August 20, 2026. In response, U.S. Federal Civilian Executive Branch (FCEB) agencies have been mandated to secure their MLflow instances within two weeks, in accordance with Binding Operational Directive 26-04. This directive, issued in June, requires prioritized patching for publicly exposed assets, vulnerabilities listed in CISA's KEV catalog, flaws that allow for automated large-scale exploitation, and those granting partial or total system control.

While CISA has not yet released specific details about the ongoing attacks, a cybersecurity firm reported that attackers began scanning for MLflow systems within hours of the CVE ID being assigned. The firm indicated that attackers are exploiting the vulnerability to directly access cloud metadata services and exfiltrate cloud credentials and secrets. Organizations running MLflow are advised to prioritize patching exposed systems, review audit logs for signs of compromise, and verify whether sensitive credentials may have been exposed.

This warning follows a separate alert from CISA on Tuesday regarding active exploitation of a critical remote code execution (RCE) flaw in the Windows Internet Key Exchange (IKE) Service Extensions component.

vulnerabilityai
ShareXLinkedInWhatsAppFacebook

More News

view all →
vulnerability

ToxicPanda 2.0 Gets a Major Upgrade, Expanding Attacks Across 16 Countries

ToxicPanda 2.0 targets 349 financial apps and abuses Android Wireless Debugging to gain deeper device access and steal banking credentials. ToxicPanda used to be a Europe-focused nuisance targeting a manageable list of banks. That version is gone. Zimperium’s zLabs team just documented ToxicPanda 2.0, and the numbers alone tell the story: 349 targeted financial institutions […]

security

Postal Service moves to finalize mail ballot regs before SCOTUS ruling

The rules have already been rejected by multiple state courts, but the Trump administration said it’s preparing in case of a favorable Supreme Court decision. The post Postal Service moves to finalize mail ballot regs before SCOTUS ruling appeared first on CyberScoop.

ai

If you're not using AI to attack your own systems, your adversaries will

Agents are also the new attack surface - cue defenders' existential angst

privacy

TikTok Agrees to $400 Million Settlement in U.S. Child Privacy Lawsuit

TikTok has agreed to a $400 million settlement with the U.S. Department of Justice to resolve a lawsuit alleging violations of child privacy laws. The lawsuit, filed in 2024, accused the company of improperly collecting data from users under 13 and failing to comply with parental requests to delete accounts. The settlement includes an immediate payment of $300 million and an additional $100 million contingent on the dissolution of a prior consent decree related to Musical.ly.

malware

Hackers infect Android car head units with proxy botnet malware

A supply-chain attack targeting Android-based car head units is using a legitimate device-update app to spread malware that enlists compromised devices in a proxy botnet or uses them for ad fraud. [...]

security

Named Pipes Under Attack: Securing Windows Interprocess Communication

Windows named pipes provide fast interprocess communication, but weak access controls can expose privileged services to untrusted processes. ThreatLocker explains how endpoint verification, command authorization, strict input validation, and narrowly scoped privileges can help secure named-pipe communication. [...]