Microsoft · qs.stringify with arrayFormat comma throws TypeError on array elements that cannot be coerced to a string
Affects MicrosoftSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 6.16.1 when convenient.
Data as of 28 Oct 2026, 09:42 UTC
- Patch
- Available – fixed in 6.16.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade qs to 6.16.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ljharbqs | Affected
| Fixed in
|
npmqspkg:npm/qsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
A vulnerability exists in Microsoft product version 3.0 where using qs.stringify with the arrayFormat set to comma causes a TypeError when array elements cannot be coerced to strings. This issue is documented under CVE-2026-110816.