Snyk Security Database

agentenact is a malicious package. This package contains malicious code, and its content was removed from the official package manager. While this package might be attempting to impersonate a valid organization, there is no connection between that organization and this package authorship.

mlflow is a platform to streamline machine learning development, including tracking experiments, packaging code into reproducible runs, and sharing and deploying models.

Affected versions of this package are vulnerable to Directory Traversal via the _create_model_version handler in mlflow/server/handlers.py, which fails to reject schemeless relative path sources for prompt-tagged model versions. An attacker can supply a relative path such as ../../../tmp as the source field when creating a prompt model version, causing the server to register a LocalArtifactRepository rooted at that traversed directory. The attacker then retrieves arbitrary files from the server's filesystem by calling the get-artifact endpoint with a target filename in the path parameter, exposing sensitive files such as /etc/passwd or the tracking database.

Note: This is only exploitable against MLflow tracking servers with model registry endpoints enabled and reachable by the attacker.

org.webjars.npm:dompurify is a DOM-only XSS sanitizer for HTML, MathML and SVG.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via a sanitization bypass in _scrubTemplateExpressions when SAFE_FOR_TEMPLATES is enabled alongside a DOM-returning mode. The post-walk safety net _scrubTemplateExpressions (src/purify.ts:1717) recurses into <template>.content but never into attached shadow roots. An attacker who controls a DOM node carrying an attached shadow root can split a template expression (e.g. ${...}, {{...}}, or <%...%>) across text nodes separated by disallowed elements. After sanitization removes those elements, the fragments become adjacent and reconstitute a complete expression that a downstream template engine evaluates, resulting in cross-site scripting or template injection.

Note: This is only exploitable when SAFE_FOR_TEMPLATES: true is set together with a DOM-returning mode (RETURN_DOM: true, RETURN_DOM_FRAGMENT: true, or IN_PLACE: true), and the sanitized content is fed into a downstream template evaluator.