GHSA-ph9p-34f9-6g65

tmp has Path Traversal via unsanitized prefix/postfix that enables directory escape

High highest severity reported · also known as CVE-2026-44705

2
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.4%
EPSS for CVE-2026-44705, percentile 38

Catalog tools matching GHSA-ph9p-34f9-6g65

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1tmp@0.0.28
npm
0.2.6not analyzedpackage-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1tmp@0.0.29
npm
0.2.6not analyzedpackage-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1tmp@0.0.33
npm
0.2.6not analyzedlib/ui-toolkit/package-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1tmp@0.1.0
npm
0.2.6not analyzedpackage-lock.jsonDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3tmp@0.0.33
npm
0.2.6not analyzedpackage-lock.jsonDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-ph9p-34f9-6g65 · NVD CVE-2026-44705 · OSV GHSA-ph9p-34f9-6g65

Grype data sources: https://github.com/advisories/GHSA-ph9p-34f9-6g65