EUVD-2026-72126
GHSA-6j8v-fv4p-986p
Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Unauthenticated network SSRF (PR:N) but only in non-default non-production builds (AC:H); scope changes to reach the metadata service (S:C) leaking credentials (C:H) with minor request-forgery integrity impact (I:L).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4DescriptionCVE.org
OpenMAIC before 1.0.1 skips server-side request forgery validation in non-production builds, allowing unauthenticated attackers to reach cloud instance metadata services. Attackers can supply arbitrary provider URLs via the x-base-url header or baseUrl parameter to access sensitive cloud credentials and metadata.
AnalysisAI
Server-side request forgery in OpenMAIC before 1.0.1 lets unauthenticated attackers coerce the server into fetching arbitrary attacker-supplied provider URLs, reaching cloud instance metadata endpoints (e.g. 169.254.169.254) to steal IAM credentials and instance metadata. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the OpenMAIC instance to be running a non-production build (NODE_ENV not set to production), because the SSRF validation guard was gated to production builds only; production deployments are not vulnerable. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor CVSS 4.0 score is 9.0 with AV:N/AC:L/PR:N/UI:N but critically includes AT:P (attack requirements present) and VC:H/SC:H, reflecting that exploitation is gated on a specific non-production build condition rather than being universally reachable. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: upgrade to OpenMAIC v1.0.1 (https://github.com/THU-MAIC/OpenMAIC/releases/tag/v1.0.1), which runs the outbound URL guard in all environments and adds a repository-scanning test that fails if a gated call site reappears; note v1.0.1 also requires Node 22.19 or newer (up from 20.9) and re-validates every redirect hop while dropping credential headers on cross-origin hops. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, conduct an inventory audit of all OpenMAIC deployments to identify instances not explicitly running NODE_ENV=production, as these systems are immediately vulnerable to credential theft by any network-reachable attacker. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today