CVE-2026-110816 (Medium) detected in qs-6.15.1.tgz
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 2/5
- Temps estimé
- 1-3 heures
- Accessibilité débutants
- 45/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- javascript, node.js
Piste de recherche
The vulnerable qs 6.15.1 is pulled in transitively under the /ui project (via cypress and request), so start with ui/package.json and the pnpm lockfile to see how qs is resolved. The advisory says the fix ships in qs 6.16.1, so the change is a resolution bump, possibly with a pnpm override. Done when the lockfile resolves qs to 6.16.1 or later and the UI install and build still pass.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
CVE-2026-110816 - Medium Severity Vulnerability
Vulnerable Library - qs-6.15.1.tgz
A querystring parser that supports nesting and arrays, with a depth limit
Library home page: https://registry.npmjs.org/qs/-/qs-6.15.1.tgz
Sample Path to Dependency File: /ui/package.json
Path to vulnerable library: /ui/node_modules/.pnpm/[email protected]/node_modules/qs/package.json
Dependency Hierarchy:
- @postgres.ai/ce-4.0.3.tgz (Root Library)
- cypress-14.5.4.tgz
- request-3.0.10.tgz
- ❌ qs-6.15.1.tgz (Vulnerable Library)
- request-3.0.10.tgz
- cypress-14.5.4.tgz
Found in base branch: master
Vulnerability Details
Summary
"qs.stringify" with "arrayFormat: 'comma'" throws "TypeError: Cannot convert object to primitive value" when an array element cannot be coerced to a string, such as an object with an own non-callable "toString" ("{ "toString": "x" }") or a null-prototype object. The comma format joins array elements with "Array.prototype.join" and, under "encodeValuesOnly", first passes each element through "String()" in "utils.encode"; neither guards against an element whose string coercion fails.
Details
In "lib/stringify.js", the comma branch collapses the array with "obj.join(',')". For an element whose own "toString" is not callable, "ToPrimitive" skips it, falls through to "Object.prototype.valueOf" (which returns the object itself), and throws. Under "encodeValuesOnly: true", the same element first reaches "String(str)" in "utils.encode" ("lib/utils.js") and throws there. Nested arrays ("{ "a": [[{ "toString": "x" }]] }") throw the same way, through "Array.prototype.toString". The "indices", "brackets", and "repeat" formats walk into object elements instead of coercing them, and are not affected.
Such elements can come from untrusted input. "JSON.parse" produces "{ "a": [{ "toString": "x" }] }" with no qs option involved. "qs.parse("a[0][toString]=x", { allowPrototypes: true })" keeps the "toString" key, and "qs.parse("a[][b]=c", { plainObjects: true })" produces a null-prototype element; the default parse options drop "toString" and produce ordinary objects, which do not throw. Express 4's default "query parser", Express 5's "extended" query parser, and body-parser's "urlencoded({ extended: true })" all call "qs.parse" with "allowPrototypes: true".
PoC
Fix
Applied in a952e75 on "main" and released as v6.16.1: an element whose string coercion would fail is coerced to its primitive "valueOf", if any, or else to "Object.prototype.toString", so it renders as "[object Object]", the same as any other object element already does under the comma format. Nested arrays are walked the way "join" walks them. Every input that did not previously throw serializes exactly as before, and a "toString" or "valueOf" that itself throws still propagates.
Affected versions
">=6.7.0 <6.16.1", fixed in v6.16.1.
The "join" path was introduced with the comma format in b84acba and first shipped in v6.7.0; v6.6.x and earlier ignore "arrayFormat: 'comma'" and are not affected. The "encodeValuesOnly" "String()" site was introduced in 4c4b23d (v6.11.1); before that, the same input throws at "join". Every release from v6.7.0 through v6.16.0 is affected.
Impact
An unauthenticated request can make any code path that re-serializes attacker-influenced data with "qs.stringify" and "arrayFormat: 'comma'" (for example, rebuilding a query string from "req.query" for a redirect or an upstream request, or serializing a parsed JSON body) throw synchronously. In a typical Node.js HTTP framework the throw is caught by the framework error boundary and the affected request returns a 500; the process survives and other requests are unaffected. Where the call runs outside an error boundary, such as an "async" Express 4 handler (where the throw becomes an unhandled promise rejection) or a bare "http" request handler, the process exits, so the impact in that case depends on the application error handling rather than on qs. The default "arrayFormat" ("indices") is not affected.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2026-10-14
URL: CVE-2026-110816
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-6pq8-jhm2-2vcw
Release Date: 2026-10-14
Fix Resolution: qs - 6.16.1
Step up your Open Source Security Game with Mend here
- Langage dominant
- Go
- Étoiles
- 2.8k
- Forks
- 90
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de postgres-ai/database-lab-engine
-
Mend: dependency security vulnerability
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
-
Difficulté 4/5 3-5 jours Accessibilité débutants 45/100
-
good first issue
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
postgres-ai/database-lab-engine#203 · 2 commentaires ·
Toutes les issues de postgres-ai/database-lab-engine
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 62/100
-
evener-transcript-v2-upgrade tool still scans transcript files through bufio's 4 KiB default bufferOuverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 78/100
prime-radiant-inc/evener#6370 ·
Les mainteneurs répondent en général sous 1 jour
-
ManageSieve proxy: a backend's NO/BYE greeting is skipped as a capability line and reported as EOFOuvertebug
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 1 jour
-
Mend: dependency security vulnerability
Difficulté 2/5 1-3 heures Accessibilité débutants 62/100
ManageIQ/manageiq-pods#1476 ·
Les mainteneurs répondent en général sous 1 jour
-
mcp: typed tool handlers lose wrapped JSON-RPC errorsPeut-être à nouveau libre Une pull request pour cette issue a été fermée sans être fusionnée. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 85/100
modelcontextprotocol/go-sdk#1529 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour