# CVE-2026-110816: qs.stringify with arrayFormat comma throws TypeError on array elements that cannot be coerced to a string

> Attackers can cause a TypeError and application crash by providing specific array elements to qs.stringify with comma format, requiring non-default parsing options.

- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-108309, AZL-108477, CLSA-2026-1792139175, DEBIAN-CVE-2026-110816, ECHO-560f-cf0a-9378, GHSA-6pq8-jhm2-2vcw, MINI-557x-736r-c3wg, MINI-5958-r47m-5q7p, MINI-5g35-x89h-p38w, MINI-9vw6-g5hg-cx78, MINI-mwvm-j3qj-56h9, MINI-p663-vj39-xp83, MINI-q5qf-crgg-c8m9, MINI-rgp3-7wx3-jgmw, UBUNTU-CVE-2026-110816

## What is CVE-2026-110816?

CVE-2026-110816 is a medium-severity denial of service vulnerability in ljharb qs, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### 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.

Weakness: CWE-704 (Incorrect Type Conversion or Cast), CWE-248 (Uncaught Exception)

## Which versions are affected by CVE-2026-110816?

2 open source packages ship an affected version, including qs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qs` | npm | From 6.7.0 | 6.16.1 |
| `qs` | npm | From 6.7.0 | 6.16.1 |

## How do I fix CVE-2026-110816?

Upgrade qs to 6.16.1 or later.

## Is CVE-2026-110816 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110816 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110816 and fix it if it is affected.

What it is: CVE-2026-110816 is a medium-severity denial of service vulnerability in ljharb qs, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110816 exists.

Affected packages and fixed versions:
- qs (npm): affected from 6.7.0; fixed in 6.16.1
- qs (npm): affected from 6.7.0; fixed in 6.16.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110816/ (Markdown: https://insights.sbomify.com/CVE-2026-110816/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110816
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110816
- OSV: https://osv.dev/vulnerability/CVE-2026-110816

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110816/
Summaries are generated and may contain mistakes; the official description above is the record.