/

CVE-2026-86259

Severity:

HIGH RISK

(7.5)

SSRF (CWE-918) in OpenMAIC Non-Production Deployments

CVE-2026-86259

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-306, CWE-918

Impact:

Unauthorized access to internal services and cloud instance metadata

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

OpenMAIC builds that skip server-side request forgery validation allow unauthenticated attackers to direct server-side requests to arbitrary URLs. By supplying a provider URL through the x-base-url header or baseUrl parameter, an attacker may reach cloud instance metadata services and access sensitive credentials or metadata.

Affected context

The vulnerability can occur in OpenMAIC deployments using non-production builds where SSRF protections are omitted or bypassed. It becomes risky when externally supplied values from the x-base-url header or baseUrl parameter influence outbound provider requests and the application can reach internal network destinations or cloud metadata endpoints.

Exploit preconditions

  • Attack surface: HTTP endpoints or request paths that accept the x-base-url

header or baseUrl parameter

  • Required access: No authentication, according to the reported behavior - Trigger point: Server-side provider requests constructed from attacker-

controlled URL values

  • Why exploitation is possible: Non-production builds do not consistently

enforce SSRF validation, allowing requests to arbitrary destinations that

may include internal services or cloud metadata endpoints

Why this happens

The underlying issue is a failure to enforce server-side request forgery controls across all build configurations. Attacker-controlled URL input is trusted when selecting an outbound request destination, rather than being constrained by an allowlist or validated against protected network ranges. This maps primarily to CWE-918, Server-Side Request Forgery. The lack of access control on the affected request path also relates to CWE-306, Missing Authentication for Critical Function.

Potential impact

  • Attackers may read cloud instance metadata
  • Cloud credentials or temporary access tokens could be exposed
  • Internal services may be reachable from the application environment
  • Attackers could use obtained credentials for unauthorized cloud actions
  • Sensitive information may be disclosed through response handling

General mitigation guidance

Mitigation generally focuses on enforcing SSRF defenses consistently across production and non-production builds. Common defensive patterns include allowing outbound requests only to explicitly approved providers, rejecting loopback, link-local, private, and cloud metadata address ranges, validating URLs after resolution, and preventing redirects from escaping approved destinations. Trust in client-supplied URL headers and parameters should be reduced or eliminated. Sensitive provider operations should require appropriate authentication and least-privilege service identities, while network egress controls can provide an additional containment layer.

How teams detect issues like this

Detection approaches can include static analysis for outbound request functions whose destinations derive from HTTP headers or query parameters, code review checks comparing security behavior across build configurations, and policy enforcement requiring SSRF validation for every externally influenced URL. Runtime monitoring can alert on requests to loopback, private, link-local, and cloud metadata ranges, as well as unusual provider destinations. Automated security review tools may help identify missing validation and authentication controls.

Sources

SourceLink
github.comgithub.com/THU-MAIC/OpenMAIC
github.comgithub.com/THU-MAIC/OpenMAIC/blob/v1.0.0/app/api/generate/image/route.ts#L73-L78
github.comgithub.com/THU-MAIC/OpenMAIC/blob/v1.0.0/middleware.ts#L60-L63
github.comgithub.com/THU-MAIC/OpenMAIC/releases/tag/v1.0.1
github.comgithub.com/THU-MAIC/OpenMAIC/security/advisories/GHSA-9m7h-vh2h-rc3w
vulncheck.comvulncheck.com/advisories/openmaic-before-1.0.1-ssrf-via-environment-gated-url-validation

Frequently asked

questions

Yes. The reported behavior allows unauthenticated network clients to submit

attacker-controlled provider URLs when the affected non-production build is

reachable.

No application authentication is reported as necessary. The attacker needs

network access to an endpoint that processes the x-base-url header or baseUrl

parameter.

Enforce SSRF validation in every build configuration, use strict outbound

destination allowlists, and block access to internal and cloud metadata

ranges.

Treat all client-supplied URLs as untrusted, require authentication for

sensitive request functions, apply egress restrictions, and include

non-production builds in security testing and policy checks.

Find out what's already
exploitable in your codebase.