Pucagit

Unsafe URL path construction occurs due to unsanitized caller-supplied identifier values used in HTTP request paths for resource operations. Identifiers containing characters with special meaning in URL paths can cause requests to address different resources or resource types than intended. In environments where identifier values originate from untrusted sources, this may lead to unauthorized access, modification, or deletion of resources. This is particularly critical in deployments that forward end-user values directly into SDK identifier parameters without validation (such as UUID checks) and rely on URL-prefix-based authorization at an upstream layer, such as a reverse proxy, edge gateway, or Web Application Firewall (WAF), where authorization is based on the intended path rather than the final delivered request path.

Frappe, a full-stack web application framework, contains a path traversal issue that may allow unauthenticated arbitrary file read on internet-facing surfaces, such as ERPNext. Over 115,700 potentially affected devices have been identified worldwide. Path traversal is a technique where an attacker uses special characters to access files and directories outside the intended folder.

LangChain contains runtime code paths that deserialize inputs, outputs, or other application-controlled payloads using overly broad object allowlists, specifically calling `load()` with `allowed objects="all"`. This allows attacker-supplied serialized constructor dictionaries to instantiate trusted classes with untrusted arguments. This issue can lead to Server-Side Request Forgery (SSRF), enabling access to internal services, cloud metadata endpoints, or sensitive network resources, which may result in credential theft and persistent supply-chain compromise. Applications are exposed if they accept untrusted structured input (such as JSON) without validation, preserve attacker-controlled nested dictionaries or lists in run data, and use affected API paths. Known affected surfaces include the `RunnableWithMessageHistory` class, the `astream log()` function, and the `astream events(version="v1")` function. Additionally, a secret-marker validation bypass in the ` is lc secret` function allows constructor dictionaries to avoid escaping during `dumps()` to `loads()` round-trips.