Security readout for executives and security teams
Plain-English summary
Yu AI Code Mother v4.3 reportedly exposes a static-file API that can let an unauthenticated internet user escape its intended directory and read other server files. Sensitive configuration, credentials, source code, or operational data could be exposed, depending on filesystem permissions and deployment contents.
Executive priority
Prioritize immediate exposure assessment and containment for internet-reachable v4.3 systems. The reported unauthenticated access and potential sensitive-file disclosure create material credential and data risk. No vendor patch is identified in the supplied sources, so owners should monitor authoritative vendor guidance and use access restrictions meanwhile.
Technical view
The reported CWE-22 flaw affects /api/static/{deployKey}/. A user-controlled path is concatenated with the preview root without normalization, permitting traversal outside that root. The record assigns CVSS 3.1 score 9.8. Although its vector claims high confidentiality, integrity, and availability impact, the supplied description specifically substantiates unauthorized file reading.
Likely exposure
Highest risk applies to Yu AI Code Mother v4.3 deployments where the affected API is reachable by untrusted users. Exploitation reportedly requires no authentication or user interaction. Actual accessible files depend on service-account permissions, filesystem layout, and external routing. The supplied affected-product metadata is otherwise listed as “n/a,” limiting inventory certainty.
Exploitation context
A public proof-of-concept reference exists, indicating technical details are publicly available. The CVE is not marked as CISA KEV in the supplied bundle, and no cited evidence confirms active exploitation. Treat internet-accessible instances as urgent without asserting attacks are occurring.
Researcher notes
The core report supports unauthenticated path traversal and out-of-root file reading. Evidence supplied here does not establish file modification, service disruption, or active exploitation, despite the CVSS vector rating integrity and availability high. Product identifiers, CPEs, and affected-version ranges beyond v4.3 are absent, and remediation details are not provided.
Mitigation direction
- Identify and prioritize all Yu AI Code Mother v4.3 deployments.
- Restrict untrusted access to the affected API while remediation is evaluated.
- Apply vendor-provided fixes or mitigations when authoritative guidance becomes available.
- Limit the application service account’s filesystem access to required files only.
- Review exposed systems for possible credential disclosure and rotate affected secrets where evidence supports it.
Validation and detection
- Confirm deployed versions and whether the affected API route exists.
- Determine whether unauthenticated users can reach the API from external networks.
- Review application and edge logs for traversal-like requests or unusual static-file access.
- Verify filesystem permissions prevent the service from reading unrelated sensitive files.
- After remediation, confirm path validation confines all requests to the intended preview root.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell 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-75337 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/fangtang7/CVE/blob/main/yu-ai/YU_AI_4.3_TRAVERSAL_POC.mdCVE reference, mitre
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.
Improper Limitation of a Pathname to a Restricted Directory
Improper Limitation of a Pathname to a Restricted Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.