12.1 · Lack of vulnerability management

Explore 1 source-supported AI security cases for 12.1 · Lack of vulnerability management in Databricks DASF 3.0, with evidence, scope, and defensive analysis.

Risk category

Software vulnerabilities in the platforms supporting data and AI operations are not identified and addressed promptly. An attacker may compromise those underlying layers rather than attack the ML algorithm directly. Vulnerability management and secure development therefore need to cover the entire supporting software stack, including ordinary infrastructure components.

Official framework source ↗ · Open interactive explorer ↗

Incident · · Practical overlap

Flowise CustomMCP: Configuration Text Becomes Server Code

Flowise builds AI workflows and connects external tools through MCP. CVE-2025-59528 lets a reachable CustomMCP configuration handler evaluate supplied text with the Node.js Function constructor. SonicWall reported exploitation in 2026. Flowise 3.0.6 replaced that evaluation with data parsing; a restricted prompt does not repair the server-side configuration boundary.

Why it relates: A known vulnerability in a deployed AI platform requires actual fleet remediation. The component vulnerability is established, not an assertion that a named organization knowingly delayed patching.

Flowise CustomMCP configuration evaluation and reported exploitation; authentication depends on deployment, and no model instruction is needed.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗