CVE-2025-15284

LOWNVD 3.73.7
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.7 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
3.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.7Exploit: NoneExposed: 0

A fix is available — apply it.

Improper Input Validation vulnerability in qs (parse modules) allows HTTP DoS.This issue affects qs: < 6.14.1.

Summary

The arrayLimit option in qs did not enforce limits for bracket notation (a[]=1&a[]=2), only for indexed notation (a[0]=1). This is a consistency bug; arrayLimit should apply uniformly across all array notations.

Note: The default parameterLimit of 1000 effectively mitigates the DoS scenario originally described. With default options, bracket notation cannot produce arrays larger than parameterLimit regardless of arrayLimit, because each a[]=valueconsumes one parameter slot. The severity has been reduced accordingly.

Details

The arrayLimit option only checked limits for indexed notation (a[0]=1&a[1]=2) but did not enforce it for bracket notation (a[]=1&a[]=2).

Vulnerable code (lib/parse.js:159-162):

if (root === '[]' && options.parseArrays) { obj = utils.combine([], leaf); // No arrayLimit check }

Working code (lib/parse.js:175):

else if (index <= options.arrayLimit) { // Limit checked here obj = []; obj[index] = leaf; }

The bracket notation handler at line 159 uses utils.combine([], leaf) without validating against options.arrayLimit, while indexed notation at line 175 checks index <= options.arrayLimit before creating arrays.

PoC

const qs = require('qs'); const result = qs.parse('a[]=1&a[]=2&a[]=3&a[]=4&a[]=5&a[]=6', { arrayLimit: 5 }); console.log(result.a.length); // Output: 6 (should be max 5)

Note on parameterLimit interaction: The original advisory's "DoS demonstration" claimed a length of 10,000, but parameterLimit (default: 1000) caps parsing to 1,000 parameters. With default options, the actual output is 1,000, not 10,000.

Impact

Consistency bug in arrayLimit enforcement. With default parameterLimit, the practical DoS risk is negligible since parameterLimit already caps the total number of parsed parameters (and thus array elements from bracket notation). The risk increases only when parameterLimit is explicitly set to a very high value.

CVSS v3
3.7
EG Score
3.7(medium)
EPSS
33.2%
KEV
Not listed

Published

December 29, 2025

Last Modified

February 26, 2026

Patch Availability(29)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/nmstate-console-plugin-rhel9:17792499202026-05-27redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17786669872026-05-20redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17786450082026-05-20redhat
redhatlinux-sgx-0:2.26-7.el92026-05-19redhat
redhatlinux-sgx-0:2.26-7.el102026-05-19redhat
redhatquay/quay-rhel8:17730976212026-03-10redhat
redhatquay/quay-rhel8:17730888622026-03-10redhat
redhatopenshift-pipelines/pipelines-console-plugin-rhel9:17709880202026-03-05redhat
redhatopenshift-pipelines/pipelines-hub-ui-rhel8:17720364712026-03-04redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17718741812026-03-04redhat
redhatnetwork-observability/network-observability-console-plugin-rhel9:17712276502026-02-18redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17707751422026-02-18redhat
redhatquay/quay-rhel8:17702491832026-02-16redhat
redhatquay/quay-rhel9:17708369012026-02-12redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17701265372026-02-11redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17700747132026-02-11redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17702348952026-02-11redhat
redhatdevspaces/pluginregistry-rhel9:17698697862026-02-10redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17697299242026-02-10redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17701094052026-02-09redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17702508892026-02-09redhat
redhatopenshift-service-mesh/kiali-rhel9:17701385132026-02-05redhat
redhatopenshift-service-mesh/kiali-rhel9:17701387272026-02-05redhat
redhatopenshift-service-mesh/kiali-rhel9:17701408532026-02-05redhat
redhatopenshift-service-mesh/kiali-rhel8:17701404702026-02-05redhat
redhatquay/quay-rhel8:17701465652026-02-04redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17689983342026-02-04redhat
redhatquay/quay-rhel8:17698520132026-02-02redhat
redhatansible-automation-platform-26/gateway-rhel9:17688899392026-01-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
qs6.14.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(20)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 01:59 UTCEPSS rescore
  4. 2026-07-15 01:59 UTCEPSS rescore
  5. 2026-07-13 22:29 UTCEPSS rescore
  6. 2026-07-13 22:29 UTCEPSS rescore
  7. 2026-07-13 06:12 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-12 05:45 UTCEPSS rescore
  10. 2026-07-11 08:26 UTCEPSS rescore
  11. 2026-07-11 08:26 UTCEPSS rescore
  12. 2026-07-09 19:09 UTCEPSS rescore
  13. 2026-07-08 15:14 UTCEPSS rescore
  14. 2026-07-07 13:45 UTCEPSS rescore
  15. 2026-07-06 16:26 UTCEPSS rescore
  16. 2026-07-06 06:32 UTCOSV refresh
  17. 2026-07-06 02:22 UTCEPSS rescore
  18. 2026-07-06 02:22 UTCEPSS rescore
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 06:30 UTCEPSS rescore
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-06-30 23:21 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 51 more
  1. 2026-06-28 04:55 UTCEPSS rescore
  2. 2026-06-27 03:08 UTCEPSS rescore
  3. 2026-06-27 03:08 UTCEPSS rescore
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 14:04 UTCEPSS rescore
  7. 2026-06-24 14:04 UTCEPSS rescore
  8. 2026-06-23 21:32 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-19 19:25 UTCEPSS rescore
  16. 2026-06-19 19:25 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-17 18:13 UTCOSV refresh
  20. 2026-06-17 17:52 UTCEPSS rescore
  21. 2026-06-16 17:52 UTCEPSS rescore
  22. 2026-06-15 17:48 UTCEPSS rescore
  23. 2026-06-14 23:17 UTCEPSS rescore
  24. 2026-06-13 22:59 UTCEPSS rescore
  25. 2026-06-13 22:59 UTCEPSS rescore
  26. 2026-06-12 23:11 UTCEPSS rescore
  27. 2026-06-11 13:59 UTCEPSS rescore
  28. 2026-06-10 22:18 UTCEPSS rescore
  29. 2026-06-10 13:21 UTCEPSS rescore
  30. 2026-06-08 14:16 UTCEPSS rescore
  31. 2026-06-08 14:16 UTCEPSS rescore
  32. 2026-06-07 15:24 UTCEPSS rescore
  33. 2026-06-06 13:47 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-05 22:46 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-05 06:10 UTCEPSS rescore
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-04 13:11 UTCEPSS rescore
  40. 2026-06-04 13:11 UTCEPSS rescore
  41. 2026-06-02 20:12 UTCEPSS rescore
  42. 2026-06-02 20:12 UTCEPSS rescore
  43. 2026-06-01 13:51 UTCEPSS rescore
  44. 2026-06-01 13:51 UTCEPSS rescore
  45. 2026-05-31 22:30 UTCEPSS rescore
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 00:16 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-29 16:53 UTCEG score recompute
  50. 2026-05-29 16:53 UTCVendor advisory
  51. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-15284?
CVE-2025-15284 is a low vulnerability published on December 29, 2025. Improper Input Validation vulnerability in qs (parse modules) allows HTTP DoS.This issue affects qs: < 6.14.1. Summary The arrayLimit option in qs did not enforce limits for bracket notation (a[]=1&a[]=2), only for indexed notation (a[0]=1). This is a consistency bug; arrayLimit should apply…
When was CVE-2025-15284 disclosed?
CVE-2025-15284 was first published in the National Vulnerability Database on December 29, 2025, with the most recent update on February 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-15284 actively exploited?
CVE-2025-15284 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-15284?
CVE-2025-15284 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2025-15284?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-15284, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-15284

Explore →

Is Your Infrastructure Affected by CVE-2025-15284?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.