ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-110910

### Summary with writes the key of an empty array without encoding it, even though keys are encoded by default.

Published Oct 27, 2026 · catalog updated Nov 2, 2026 · ### Summary with writes

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-110910. EPSS is 0.29%. Act only if a listed version of ### Summary with writes is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (### Summary with writes).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.29%
Remediation
Advisory link
Affected products
Debian:12 node-qs · Debian:13 node-qs · Debian:14 node-qs

### Summary with writes the key of an empty array without encoding it, even though keys are encoded by default. A key that contains (or the configured ), , or therefore becomes query string syntax instead of data, so a caller-supplied key name can add parameters to the serialized query string, or cut it short. ### Details In , the branch returns early, before the code that passes every other key through and . So serializes as , but serializes as . The early return applies at any depth ( gives ), under every , with , and with a custom , which is never called for that key. With or , keys are intentionally left unencoded on every path; those configurations are not affected. #### PoC #### Fix Applied in 234d505 on and released as v6.17.0, and backported to v6.16.2, v6.15.4, v6.14.3, v6.13.4, and v6.12.6: the key of an empty array goes through and exactly as the key of any other value does, so now serializes as . Keys that need no encoding serialize as before, with two exceptions that match every other path: the brackets of a nested key are now encoded ( becomes , which reads identically), and with , a dot in the key becomes instead of (which previously misread as nesting). ### Affected versions - , fixed in v6.12.6 - , fixed in v6.13.4 - , fixed in v6.14.3 - , fixed in v6.15.4 - , fixed in v6.16.2 v6.17.0 and later are not affected. was introduced in f22b2bc and first shipped in v6.12.0, with this early return. Earlier versions have no option and are not affected. ### Impact An application that passes an object whose key names come from untrusted input to with (for example, to forward a parsed JSON body or user-selected fields to an upstream service) can have parameters injected into the resulting query string. The injected parameters are not keys of the object, so deleting or overwriting a key on the object (such as setting a trusted after copying the user's fields) does not remove them; whether the attacker's value or the application's wins depends on how the receivin

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Debian:12 node-qs6.11.0+ds+~6.9.7-3, 6.11.0+ds+~6.9.7-4, 6.13.0+ds+~6.9.16-1
  • Debian:13 node-qs6.13.0+ds+~6.9.16-1, 6.14.1+ds+~6.14.0-1, 6.15.0+ds+~6.15.0-1
  • Debian:14 node-qs6.13.0+ds+~6.9.16-1, 6.14.1+ds+~6.14.0-1, 6.15.0+ds+~6.15.0-1

How to fix CVE-2026-110910

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    Seen in 6.11.0+ds+~6.9.7-3 · 8 other packages on the advisory

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-110910. EPSS is 0.29%. Act only if a listed version of ### Summary with writes is installed.

Which versions are affected?

Compare what you have installed with 6.11.0+ds+~6.9.7-3, 6.11.0+ds+~6.9.7-4, 6.13.0+ds+~6.9.16-1, 6.13.0+ds+~6.9.16-1, 6.14.1+ds+~6.14.0-1, 6.15.0+ds+~6.15.0-1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.29%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Debian security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 27, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    ### Summary with writes the key of an empty array without encoding it, even though keys are encoded by default. A key that contains (or the configured ), , or therefore becomes query string syntax instead of data, so a caller-supplied key name can add parameters to the serialized query string, or cut it short. ### Details In , the branch returns early, before the code that passes every other key t

  2. Nov 2, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    ### Summary with writes the key of an empty array without encoding it, even though keys are encoded by default. A key that contains (or the configured ), , or therefore becomes query string syntax instead of data, so a caller-supplied key name can add parameters to the serialized query string, or cut it short. ### Details In , the branch returns early, before the code that passes every other key t

Sources

References

Freshness

Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 4, 2026
  • OpenSSF OSV / OSV ScannerNov 2, 2026