Digest · Sunday

Security digest: August 2, 2026

1 editorial brief and 1 critical advisory.

All digests · RSS · Markdown

Take stock

  • Act now: MLflow CVE-2026-64849: Exploited Unauthenticated SSRF. Teams running MLflow tracking servers 3.3.0 through 3.14.x bound beyond localhost, especially on cloud VMs or Kubernetes nodes with an attached IAM role, service account or managed identity.
  • Maven: 1 critical advisory (org.bouncycastle:bc-fips, org.bouncycastle:bcprov-jdk18on, org.bouncycastle:bcprov-lts8on, org.bouncycastle:bcprov-jdk15to18). Check with mvn dependency:tree -Dincludes=<groupId>:<artifactId>.
  • None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.

Editorial briefs

Act now

· Vulnerability · CVE-2026-64849

MLflow CVE-2026-64849: Exploited Unauthenticated SSRF

If an MLflow tracking server below 3.15.0 is reachable by anyone you do not fully trust, assume attackers can read your cloud instance credentials through it: upgrade today, then check webhooks and cloud audit logs.

Must act: Teams running MLflow tracking servers 3.3.0 through 3.14.x bound beyond localhost, especially on cloud VMs or Kubernetes nodes with an attached IAM role, service account or managed identity.

Can relax: Local-only tracking servers on the default 127.0.0.1 binding, servers below 3.3.0 (no webhooks feature, though they need upgrading for other reasons), and anyone already on 3.16.0 or later.

  1. Check the version on every tracking server (pip show mlflow) and upgrade to 3.16.0 or later; 3.17.2 is current.
  2. Until upgraded, take the server off public networks or put it behind a VPN or identity-aware proxy.
  3. Block the MLflow host from reaching 169.254.169.254 and other link-local metadata addresses, and enforce IMDSv2 on AWS.

Read the brief →

Known exploited (CISA KEV) 0

Added to CISA’s catalog on this day: confirmed exploitation in the wild. Due date = CISA’s deadline for US federal agencies.

None.

Critical advisories by ecosystem 1

GitHub-reviewed advisories rated critical, published this day (Pacific time).

Maven 1

Check: mvn dependency:tree -Dincludes=<groupId>:<artifactId>