Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-86259 – Unauthenticated SSRF to Cloud Metadata / Credential Exposure – OpenMAIC before 1.0.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86259 is a Server-Side Request Forgery (SSRF) vulnerability in OpenMAIC (THU-MAIC’s "Open Multi-Agent Interactive Classroom" platform) affecting all versions before 1.0.1. Because SSRF validation on outbound provider requests is only enforced in production builds, an unauthenticated attacker can force the server to issue requests to arbitrary internal or cloud-internal destinations, including cloud instance metadata services. The issue carries a CVSS score of 9.0 and network attack vector, reflecting the potential to reach and exfiltrate cloud credentials without any authentication.

Technical details

  • Root cause: the application’s outbound URL/SSRF validation guard is gated on environment (e.g., NODE_ENV), so non-production builds and self-hosted/dev deployments run with the check disabled ("fail open").
  • Trigger: an attacker supplies an arbitrary provider URL via the x-base-url request header or a baseUrl parameter, causing the server to make an outbound HTTP request to that attacker-controlled destination.
  • Attack vector: network, unauthenticated, no user interaction required.
  • Impact: the server can be coerced into contacting cloud instance metadata endpoints or other internal services, exposing temporary cloud credentials, internal service details, and configuration secrets, which may enable further access to cloud resources.

Affected software

  • THU-MAIC OpenMAIC: all versions from 0 up to (but not including) 1.0.1

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
  • Also scored under CVSS v4.0 at 9.0 (Critical) — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to OpenMAIC v1.0.1 or later, which enforces the outbound URL/SSRF guard in all environments (not just production) and drops credential headers on cross-origin redirect hops.
  • If no patch can be applied immediately:
    • Block outbound traffic from application servers to known cloud metadata IP ranges via firewall/security group rules.
    • Enforce strict allow-listing of permitted outbound domains, ideally through an inspecting proxy.
    • Apply least-privilege IAM roles/permissions to instances running OpenMAIC to limit the impact of any credentials that could be exposed.
    • Avoid running non-production/dev builds of OpenMAIC exposed to untrusted networks.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Meta tag (description): "The open-source AI interactive classroom. Upload a PDF to instantly generate an immersive, multi-agent learning experience."

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge