Skip to content
Threat Feed

Tag

Arbitrary-File-Write

5 briefs RSS
high advisory

Zarf Path Traversal Vulnerability via Malicious Package Metadata.Name

Zarf is vulnerable to path traversal due to insufficient sanitization of the Metadata.Name field in package manifests when using the `zarf package inspect sbom` or `zarf package inspect documentation` commands, potentially leading to arbitrary file write.

zarf path-traversal arbitrary-file-write package-inspection linux
3r 1t
high advisory

TinaCMS GraphQL Path Traversal Vulnerability

A path traversal vulnerability in @tinacms/graphql allows unauthenticated users to write and overwrite arbitrary files within the project root by manipulating the relativePath parameter in GraphQL mutations, leading to potential arbitrary code execution.

path-traversal graphql tinacms arbitrary-file-write
2r 2t
critical advisory

Gigabyte Control Center Arbitrary File Write Vulnerability

Gigabyte Control Center has an Arbitrary File Write vulnerability (CVE-2026-4415) that allows unauthenticated remote attackers to write arbitrary files to any location on the underlying operating system, leading to arbitrary code execution or privilege escalation.

cve-2026-4415 arbitrary-file-write privilege-escalation code-execution gigabyte
2r 2t
high advisory

Evolver Path Traversal Vulnerability in `fetch` Command

A path traversal vulnerability exists in the `fetch` command of `@evomap/evolver` due to insufficient validation of the `--out` flag, allowing attackers to write files to arbitrary locations on the filesystem, potentially leading to overwriting critical system files and privilege escalation.

@evomap/evolver path-traversal arbitrary-file-write privilege-escalation evolver
2r 2t
high advisory

i18next-fs-backend Path Traversal Vulnerability

i18next-fs-backend versions before 2.6.4 are vulnerable to path traversal due to insufficient sanitization of the lng and ns values, potentially allowing attackers to read arbitrary files, overwrite files, or execute code if .js or .ts locale files are in use.

i18next-fs-backend path-traversal i18next arbitrary-file-read arbitrary-file-write code-execution
2r 1t