GHSA-q8mj-m7cp-5q26

qs has a remotely triggerable DoS: qs.stringify crashes with TypeError on null/undefined entries in comma-format arrays when encodeValuesOnly is set

Medium highest severity reported · also known as CVE-2026-8723

4
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-8723, percentile 34

Catalog tools matching GHSA-q8mj-m7cp-5q26

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1qs@6.11.2
npm
6.15.2not analyzedpackage-lock.jsonDispute
infisical
Secret Management
v0.167.4qs@6.15.0
npm
6.15.2not analyzedfrontend/package-lock.jsonDispute
infisical
Secret Management
v0.167.4qs@6.15.1
npm
6.15.2not analyzedsink/oidc-server/package-lock.jsonDispute
gatekeeper
Policy as Code
v3.23.1qs@6.14.2
npm
6.15.2not analyzedwebsite/yarn.lockDispute
slsa-verifier
Supply Chain Compliance
v2.7.1qs@6.12.1
npm
6.15.2not 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-q8mj-m7cp-5q26 · NVD CVE-2026-8723 · OSV GHSA-q8mj-m7cp-5q26

Grype data sources: https://github.com/advisories/GHSA-q8mj-m7cp-5q26