CVE-2026-86259

OpenMAIC versions before 1.0.1 skip server-side request forgery (SSRF) validation in non-production builds, leaving requests unvalidated by the framework's SSRF checks. Because the bypass requires no authentication, an unauthenticated remote attacker can supply an arbitrary provider URL through the x-base-url header or the baseUrl parameter, causing OpenMAIC to fetch from an attacker-controlled or attacker-chosen endpoint. By pointing that URL at the cloud instance metadata service (for example 169.254.169.254), the attacker can retrieve sensitive cloud credentials and instance metadata belonging to the affected workload. Deployments running non-production builds of OpenMAIC prior to 1.0.1, particularly in cloud environments where metadata services are reachable from the instance, are affected. No public proof-of-concept or in-the-wild exploitation is currently known, and EPSS estimates only a 0.3% probability of exploitation within 30 days.

What to do: Upgrade to OpenMAIC 1.0.1 or later, or run production builds in which SSRF validation remains enabled. Until patched, restrict outbound access from OpenMAIC workloads to cloud metadata endpoints (e.g., 169.254.169.254) and avoid exposing non-production builds to untrusted network traffic. Review cloud credentials and metadata-service access logs for signs of unauthorized retrieval.