Analyst readout for executives and security teams
Plain-English summary
CVE-2026-9464 is a server-side request forgery issue in YunaiV yudao-cloud 2026.03. An authenticated remote user could make the application send unintended requests through the Admin API. This can expose internal services or support further compromise, depending on network placement and privileges.
Executive priority
Treat as a near-term exposure review, not an emergency absent evidence of active exploitation. Prioritize systems where the Admin API is externally reachable, broadly accessible, or connected to sensitive internal networks.
Technical view
The issue affects IotDataSinkHttpConfig in /admin-api/iot/data-sink/create, part of the yudao-cloud Admin API Endpoint. VulDB rates it CVSS 5.8 with network access, low complexity, and authentication required. The public record cites CWE-918 SSRF and states a public exploit exists.
Likely exposure
Exposure is most likely where yudao-cloud 2026.03 is deployed and the Admin API is reachable by users or networks beyond tightly trusted administrators. Authentication is required, so risk depends heavily on admin account access, role design, and network segmentation.
Exploitation context
The source bundle says exploit details were publicly disclosed and may be used. It does not cite CISA KEV listing or confirmed active exploitation. The vendor reportedly did not respond, and no vendor patch or official mitigation is named in the provided sources.
Researcher notes
Evidence identifies SSRF in an authenticated Admin API data-sink creation path. Public exploit disclosure increases monitoring urgency, but the provided bundle lacks vendor confirmation, patch status, and safe detection details beyond endpoint and component names.
Mitigation direction
- Inventory any YunaiV yudao-cloud 2026.03 deployments.
- Check vendor channels for official updates or mitigation guidance.
- Restrict Admin API access to trusted administrator networks only.
- Review and tighten permissions for accounts able to create IoT data sinks.
- Monitor application servers for unexpected outbound connections.
Validation and detection
- Confirm whether yudao-cloud 2026.03 is present in production or staging.
- Verify /admin-api/iot/data-sink/create is not internet-accessible.
- Review Admin API logs for unusual data sink creation activity.
- Check outbound firewall logs from yudao-cloud hosts.
- Validate that only intended administrators can access the affected workflow.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9464 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.8 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:M/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:M/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 6.4 6.4 VulDB CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P — — VulDB CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 1.2 3.4 VulDB CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 1.2 3.4 VulDB Vulnerability scoring details
Base CVSS 4.0 score
5.1 MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
4.7 MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 3.0 score
4.7 MediumVector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 2.0 score
5.8 MediumVector: AV:N/AC:L/Au:M/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline VulDB
Advisory disclosed
- Source timeline VulDB
VulDB entry created
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline VulDB
VulDB entry last update
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 source CVE List V5
- VDB-365445 | YunaiV yudao-cloud Admin API Endpoint create IotDataSinkHttpConfig server-side request forgery CVE reference, VulDB · vdb-entry, technical-description
- VDB-365445 | CTI Indicators (IOB, IOC, IOA) CVE reference, VulDB · signature, permissions-required
- Submit #813962 | YunaiV yudao-cloud 2026.03 Server-Side Request Forgery CVE reference, VulDB · third-party-advisory
- https://github.com/fakebug111/my_public_bug/blob/main/issus05.md CVE reference, VulDB · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.