GHSA-4vmm-mhcq-4x9j

Sandbox Bypass Leading to Arbitrary Code Execution in constantinople

Critical highest severity reported

1
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

Catalog tools matching GHSA-4vmm-mhcq-4x9j

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1constantinople@3.0.2
npm
3.1.1not 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-4vmm-mhcq-4x9j · OSV GHSA-4vmm-mhcq-4x9j

Grype data sources: https://github.com/advisories/GHSA-4vmm-mhcq-4x9j