Yu Mother 4.3 Static Resource Interface /api/static/{deployKey}/ deployKey path traversal

Summaryinfo

A vulnerability was found in Yu Mother 4.3 and classified as problematic. Affected is an unknown function of the file /api/static/{deployKey}/ of the component Static Resource Interface. Such manipulation of the argument deployKey leads to path traversal. This vulnerability is listed as CVE-2026-75337. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability was found in Yu Mother 4.3 and classified as problematic. Affected by this issue is an unknown code of the file /api/static/{deployKey}/ of the component Static Resource Interface. The manipulation of the argument deployKey with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. CVE summarizes:

The static resource interface /api/static/{deployKey}/ of Yu AI Code Mother v4.3 is vulnerable to path traversal. The user-controlled path is concatenated to the preview root directory without any normalization, allowing anonymous attackers to read files outside the preview root.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-75337 since 08/17/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/28/2026). The MITRE ATT&CK project declares the attack technique as T1006.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Yu

Name

• Mother

Version

• 4.3

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion