cve.bz

CVE-2026-110816 ljharb qs: Uncaught Exception

6.3 mediumEPSS 0.4%Fix available

Medium (6.3) in ljharb qs. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in qs 6.16.1.

On this page
### 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 ```js var qs = require("qs"); qs.stringify(JSON.parse("{\"a\":[{\"toString\":\"x\"}]}"), { arrayFormat: "comma" }); qs.stringify(qs.parse("a[0][toString]=x", { allowPrototypes: true }), { arrayFormat: "comma" }); qs.stringify(qs.parse("a[][b]=c", { plainObjects: true }), { arrayFormat: "comma", encodeValuesOnly: true }); // TypeError: Cannot convert object to primitive value ``` #### 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.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-248 Uncaught Exception
CWE-704 Incorrect Type Conversion or Cast
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-110816 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110816?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110816?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110816 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ljharb qsfrom 6.7.0 before 6.16.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6pq8-jhm2-2vcwnpmqs>=6.7.0 <6.16.16.16.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14node-qsno fix listedDEBIAN-CVE-2026-110816
Ubuntu16.04:LTS, 18.04:LTS, 22.04:LTS and 5 morenode-qsno fix listedUBUNTU-CVE-2026-110816
Red Hathummingbird:1grafana12.40:12.4.13-0.4.hum1RHSA-2026:90388
Red Hathummingbird:1grafana13.10:13.1.8-0.3.hum1RHSA-2026:87077
Red Hathummingbird:1grafana13.20:13.2.3-0.3.hum1RHSA-2026:85266
openSUSETumbleweedgit-bug0.11.0-3.1openSUSE-SU-2026:12261-1
Azure Linux3js-jqueryno fix listedAZL-108309
Azure Linux3python-tensorboardno fix listedAZL-108477

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat Product Security has rated this vulnerability as Moderate severity because successful exploitation requires an application to explicitly select the non-default comma array formatting option when processing untrusted input. Under typical Node.js deployment frameworks, the resulting uncaught exception is trapped within request-level boundaries, terminating only the isolated request instead of crashing the hosting service. A complete process failure is restricted to environments lacking top-level exception handlers.

ProductPackageStateAdvisory
Red Hat Hardened Imagesgrafana13-2-main-13.2.3-0.3.hum1Fixed 2026-10-19RHSA-2026:85266
Red Hat Hardened Imagesgrafana13-1-main-13.1.8-0.3.hum1Fixed 2026-10-21RHSA-2026:87077
Red Hat Hardened Imagesgrafana12-4-main-12.4.13-0.4.hum1Fixed 2026-10-26RHSA-2026:90388
Red Hat Hardened Imagesprometheus3.13Not affected
Red Hat Hardened ImagesyarnpkgNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-110816.

References

Check your stackJSON