CVE-2025-15284

LOWNVD 3.73.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This low-severity CVE scores 3.7 under NVD CVSS v3. EPSS exploit probability: 0.4% (37th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
3.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.7Exploit: None knownExposed services: Not assessed

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.7LOWmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity37% × 45%
The EG Score, 3.7 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 29, 2025

Last Modified

October 14, 2026

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17836775332026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836853752026-07-20redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17822697942026-07-09redhat
redhateap7-wildfly-0:7.3.18-3.GA_redhat_00001.1.el7eap2026-06-30redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17798749672026-06-03redhat
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:17730888622026-03-10redhat
redhatquay/quay-rhel8:17730976212026-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
redhatopenshift4/ose-monitoring-plugin-rhel9:17707751422026-02-18redhat
redhatnetwork-observability/network-observability-console-plugin-rhel9:17712276502026-02-18redhat
redhatquay/quay-rhel8:17702491832026-02-16redhat
redhatquay/quay-rhel9:17708369012026-02-12redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17702348952026-02-11redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17701265372026-02-11redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17700747132026-02-11redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17697299242026-02-10redhat
redhatdevspaces/pluginregistry-rhel9:17698697862026-02-10redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17702508892026-02-09redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17701094052026-02-09redhat
redhatopenshift-service-mesh/kiali-rhel9:17701387272026-02-05redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-qs6.10.1+ds-1 ... 6.9.4+ds-1+deb11u1 (15 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-qs6.11.0+ds+~6.9.7-3 ... 6.16.0+ds+~6.15.1-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-qs6.13.0+ds+~6.9.16-1 ... 6.16.0+ds+~6.15.1-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-qs6.13.0+ds+~6.9.16-1
  • every version up to 6.14.1+ds+~6.14.0-1: fixed in 6.14.1+ds+~6.14.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
qs—
  • every version up to 6.14.1: fixed in 6.14.1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(19)

Data Freshness Timeline

(refreshed 13× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 169 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 19:41 UTCEG score recompute
  2. 2026-10-14 19:41 UTCVendor advisory
  3. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  5. 2026-10-12 17:22 UTCEG score recompute
  6. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-10-11 20:53 UTCEG score recompute
  8. 2026-10-11 19:03 UTCEG score recompute
  9. 2026-10-11 15:43 UTCEG score recompute
  10. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  12. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  14. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  15. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-10-03 10:09 UTCOSV refresh
  20. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Show 69 more
  1. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  2. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  3. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  4. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  5. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  6. 2026-09-14 04:49 UTCOSV refresh
  7. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  8. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  9. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  11. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  12. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  14. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  16. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  18. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  19. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  20. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  21. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  22. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  23. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  24. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  25. 2026-08-26 05:43 UTCOSV refresh
  26. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  27. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  28. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  29. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  31. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  32. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  33. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  34. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  35. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  38. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  39. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  40. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  41. 2026-08-09 22:30 UTCEG score recompute
  42. 2026-08-09 22:30 UTCVendor advisory
  43. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  44. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  45. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  46. 2026-08-06 06:53 UTCEG score recompute
  47. 2026-08-06 06:53 UTCVendor advisory
  48. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  50. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  51. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  53. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  55. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  56. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  57. 2026-07-27 14:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  58. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  59. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  60. 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  61. 2026-07-23 14:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  62. 2026-07-23 11:49 UTCOSV refresh
  63. 2026-07-23 02:49 UTCEG score recompute
  64. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  65. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  66. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  67. 2026-07-18 10:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  68. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  69. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.4% · 33rd percentile

Frequently asked(5)

What is CVE-2025-15284?
CVE-2025-15284 is a low-severity vulnerability; its CVE record was 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 the CVE record for CVE-2025-15284 published?
The CVE record for CVE-2025-15284 was published on December 29, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2025-15284 actively exploited?
CVE-2025-15284 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2025-15284 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-15284 are linked in the Vendor Advisories panel on this page.

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.