arrayLimit bypass in bracket notation allows DoS via memory exhaustion
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
cve-program · CVE-2025-15284
PublishedImproper 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.
- Source published
- 29 Dec 2025 22:56:45 UTC
- Source modified
- 10 Feb 2026 20:06:42 UTC
- Observed here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 4.0 · 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:L
CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
euvd · EUVD-2025-205660
PublishedImproper 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.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Dec 29, 2025, 10:56:45 PM
dateUpdated: Feb 10, 2026, 8:06:42 PM
56 related source bulletins · separate from aliases
RHSA-2026:20042: Red Hat Security Advisory: OpenShift Container Platform 4.19.32 security and extras update
CVE-2025-13465 · CVE-2025-15284 · CVE-2025-58183 · CVE-2026-4800 · CVE-2026-22029 · CVE-2026-29063 · CVE-2026-33186 · CVE-2026-35469
RHSA-2026:2762: Red Hat Security Advisory: Red Hat Quay 3.10.18
CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049
RHSA-2026:19712: Red Hat Security Advisory: RHOAI 3.3.3 - Red Hat OpenShift AI
CVE-2025-6242 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-59057 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-62164 · CVE-2025-62718 · CVE-2025-64756 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66448 · CVE-2025-66471 · CVE-2025-69223 · CVE-2025-69873 · CVE-2026-0846 · CVE-2026-0847 · CVE-2026-4800 · CVE-2026-21441 · CVE-2026-21884 · CVE-2026-22029 · CVE-2026-22778 · CVE-2026-23490 · CVE-2026-23745 · CVE-2026-24049 · CVE-2026-24486 · CVE-2026-24779 · CVE-2026-25639 · CVE-2026-25990 · CVE-2026-27893 · CVE-2026-28684 · CVE-2026-29063 · CVE-2026-29074 · CVE-2026-30922 · CVE-2026-31812 · CVE-2026-32597 · CVE-2026-32829 · CVE-2026-32981 · CVE-2026-33186 · CVE-2026-33231 · CVE-2026-33236 · CVE-2026-34986 · CVE-2026-40175 · CVE-2026-40192 · CVE-2026-40895
WID-SEC-W-2026-0181: ILIAS: Mehrere Schwachstellen
CVE-2025-15284 · CVE-2025-55166
NCSC-2026-0079: Kwetsbaarheden verholpen in Siemens producten
CVE-2024-29857 · CVE-2024-30171 · CVE-2024-30172 · CVE-2024-41996 · CVE-2025-6965 · CVE-2025-7783 · CVE-2025-9230 · CVE-2025-9232 · CVE-2025-9670 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-27769 · CVE-2025-40943 · CVE-2025-55018 · CVE-2025-58751 · CVE-2025-58752 · CVE-2025-58754 · CVE-2025-62439 · CVE-2025-62522 · CVE-2025-64157 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-66030 · CVE-2025-66031 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69277 · CVE-2026-22610 · CVE-2026-24858 · CVE-2026-25569 · CVE-2026-25570 · CVE-2026-25571 · CVE-2026-25572 · CVE-2026-25573 · CVE-2026-25605
NCSC-2026-0034: Kwetsbaarheden verholpen in Atlassian producten
CVE-2021-3807 · CVE-2022-25883 · CVE-2022-45693 · CVE-2024-21538 · CVE-2024-38286 · CVE-2024-45296 · CVE-2024-45801 · CVE-2025-12383 · CVE-2025-15284 · CVE-2025-27152 · CVE-2025-41249 · CVE-2025-48976 · CVE-2025-48989 · CVE-2025-49146 · CVE-2025-52434 · CVE-2025-52999 · CVE-2025-53689 · CVE-2025-54988 · CVE-2025-55163 · CVE-2025-55752 · CVE-2025-64775 · CVE-2025-66516 · CVE-2025-9287 · CVE-2025-9288 · CVE-2026-21569
RHSA-2026:3825: Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.20.3
CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-66506 · CVE-2025-66564
RHSA-2026:41928: Red Hat Security Advisory: Red Hat Migration Toolkit for Containers
CVE-2025-7783 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-58754 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-62718 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2025-68121 · CVE-2025-69223 · CVE-2025-69227 · CVE-2025-69228 · CVE-2026-4800 · CVE-2026-6322 · CVE-2026-9277 · CVE-2026-9595 · CVE-2026-12143 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-21441 · CVE-2026-22029 · CVE-2026-23490 · CVE-2026-23745 · CVE-2026-25679 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27137 · CVE-2026-29063 · CVE-2026-30922 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32283 · CVE-2026-33186 · CVE-2026-33810 · CVE-2026-33811 · CVE-2026-34986 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-40895 · CVE-2026-42264 · CVE-2026-42338 · CVE-2026-42499 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-45736 · CVE-2026-45822 · CVE-2026-48779
ICSA-26-071-03: Siemens SIDIS Prime
CVE-2024-29857 · CVE-2024-30171 · CVE-2024-30172 · CVE-2024-41996 · CVE-2025-6965 · CVE-2025-7783 · CVE-2025-9230 · CVE-2025-9232 · CVE-2025-9670 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-58751 · CVE-2025-58752 · CVE-2025-58754 · CVE-2025-62522 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-66030 · CVE-2025-66031 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69277 · CVE-2026-22610
RHSA-2026:41941: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.18.25 security, enhancement & bug fix update
CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-47907 · CVE-2025-58183 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-66031 · CVE-2025-68157 · CVE-2025-68458 · CVE-2025-69873 · CVE-2026-4800 · CVE-2026-25896 · CVE-2026-26278 · CVE-2026-26996 · CVE-2026-27904 · CVE-2026-27942 · CVE-2026-29063 · CVE-2026-33036 · CVE-2026-33186 · CVE-2026-34986 · CVE-2026-48779
RHSA-2026:17469: Red Hat Security Advisory: OpenShift Container Platform 4.20.23 security and extras update
CVE-2025-13465 · CVE-2025-15284 · CVE-2026-4800 · CVE-2026-22029 · CVE-2026-29063 · CVE-2026-35469
WID-SEC-W-2026-0301: IBM App Connect Enterprise: Schwachstelle ermöglicht Denial of Service
CVE-2025-15284
RHSA-2026:2500: Red Hat Security Advisory: Red Hat multicluster global hub 1.4.4 security update
CVE-2025-12816 · CVE-2025-15284 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-68429 · CVE-2026-21441
RHSA-2026:4185: Red Hat Security Advisory: Red Hat Quay 3.13.11
CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049
RHSA-2026:3712: Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.15.4
CVE-2024-37890 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-66031 · CVE-2025-66506 · CVE-2025-66564
WID-SEC-W-2026-0105: Red Hat Developer Hub: Mehrere Schwachstellen
CVE-2025-15284 · CVE-2025-64756 · CVE-2025-65945
RHSA-2026:2568: Red Hat Security Advisory: RHACS 4.9.3 security and bug fix update
CVE-2025-12816 · CVE-2025-15284 · CVE-2025-58183 · CVE-2025-66031 · CVE-2025-66506 · CVE-2025-66564 · CVE-2025-68428 · CVE-2025-68973 · CVE-2026-22029
RHSA-2026:1552: Red Hat Security Advisory: OpenShift Container Platform 4.19.23 bug fix and security update
CVE-2025-15284 · CVE-2025-58068 · CVE-2025-58183 · CVE-2025-65637
WID-SEC-W-2026-0177: Atlassian Bamboo, Bitbucket, Confluence und Jira: Mehrere Schwachstellen
CVE-2021-3807 · CVE-2022-25883 · CVE-2022-45693 · CVE-2024-21538 · CVE-2024-38286 · CVE-2024-45296 · CVE-2024-45801 · CVE-2025-12383 · CVE-2025-15284 · CVE-2025-27152 · CVE-2025-41249 · CVE-2025-48976 · CVE-2025-48989 · CVE-2025-49146 · CVE-2025-52434 · CVE-2025-52999 · CVE-2025-53689 · CVE-2025-54988 · CVE-2025-55163 · CVE-2025-55752 · CVE-2025-64775 · CVE-2025-66516 · CVE-2025-9287 · CVE-2025-9288 · CVE-2026-21569
SSA-485750: SSA-485750: Multiple Vulnerabilities in SIDIS Prime Before V4.0.800
CVE-2024-29857 · CVE-2024-30171 · CVE-2024-30172 · CVE-2024-41996 · CVE-2025-6965 · CVE-2025-7783 · CVE-2025-9230 · CVE-2025-9232 · CVE-2025-9670 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-58751 · CVE-2025-58752 · CVE-2025-58754 · CVE-2025-62522 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-66030 · CVE-2025-66031 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69277 · CVE-2026-22610
RHSA-2026:83622: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.17.28 security, enhancement & bug fix update
CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-58183 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-66031 · CVE-2025-68157 · CVE-2025-68458 · CVE-2025-69873 · CVE-2026-4800 · CVE-2026-6321 · CVE-2026-22029 · CVE-2026-26996 · CVE-2026-27904 · CVE-2026-29063 · CVE-2026-33186
msrc_CVE-2025-15284: arrayLimit bypass in bracket notation allows DoS via memory exhaustion
CVE-2025-15284
RHSA-2026:2078: Red Hat Security Advisory: OpenShift Container Platform 4.18.33 bug fix and security update
CVE-2025-13465 · CVE-2025-15284 · CVE-2025-65637
RHSA-2026:4215: Red Hat Security Advisory: Red Hat Quay 3.14.6
CVE-2022-30187 · CVE-2024-34156 · CVE-2024-47081 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-45768 · CVE-2025-47273 · CVE-2025-47913 · CVE-2025-50181 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-58754 · CVE-2025-59420 · CVE-2025-61729 · CVE-2025-61920 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049
RHSA-2026:2681: Red Hat Security Advisory: Red Hat Quay 3.16.2
CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-15284 · CVE-2025-31133 · CVE-2025-52881 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2026-21441 · CVE-2026-24049
RHSA-2026:2350: Red Hat Security Advisory: RHACS 4.9.3 security and bug fix update
CVE-2025-12816 · CVE-2025-15284 · CVE-2025-58183 · CVE-2025-66031 · CVE-2025-66506 · CVE-2025-66564 · CVE-2025-68428 · CVE-2025-68973 · CVE-2026-22029
RHSA-2026:1730: Red Hat Security Advisory: Red Hat Quay 3.12.13
CVE-2024-34156 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441
RHSA-2026:2129: Red Hat Security Advisory: OpenShift Container Platform 4.21.1 bug fix and security update
CVE-2025-15284 · CVE-2025-55198 · CVE-2025-55199 · CVE-2025-58068 · CVE-2025-58183 · CVE-2025-65637
RHSA-2026:0761: Red Hat Security Advisory: Red Hat build of Cryostat security update
CVE-2025-15284 · CVE-2025-66566
RHSA-2026:2456: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.26.0 Release.
CVE-2024-25621 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-61729 · CVE-2025-64756 · CVE-2025-65945 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66490 · CVE-2026-21441 · CVE-2026-22029
RHSA-2026:18480: Red Hat Security Advisory: linux-sgx security update
CVE-2025-13465 · CVE-2025-15284 · CVE-2026-23745 · CVE-2026-23950 · CVE-2026-24842
RHSA-2026:2145: Red Hat Security Advisory: Kiali 1.73.26 for Red Hat OpenShift Service Mesh 2.6
CVE-2025-13465 · CVE-2025-15284
RHSA-2026:0531: Red Hat Security Advisory: Red Hat Developer Hub 1.8.2 release.
CVE-2025-15284 · CVE-2025-64756 · CVE-2025-65945
RHSA-2026:2148: Red Hat Security Advisory: Kiali 2.11.6 for Red Hat OpenShift Service Mesh 3.1
CVE-2025-13465 · CVE-2025-15284 · CVE-2025-61729 · CVE-2026-22029
RHSA-2026:2256: Red Hat Security Advisory: Red Hat multicluster global hub 1.5.3 security update
CVE-2025-12816 · CVE-2025-15284 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-68429 · CVE-2026-21441
WID-SEC-W-2026-3046: IBM Concert: Mehrere Schwachstellen
CVE-2019-19921 · CVE-2021-23337 · CVE-2024-3651 · CVE-2024-39338 · CVE-2024-45590 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-15599 · CVE-2025-22874 · CVE-2025-47273 · CVE-2025-47907 · CVE-2025-52881 · CVE-2025-53643 · CVE-2025-55184 · CVE-2025-58056 · CVE-2025-58188 · CVE-2025-58189 · CVE-2025-61723 · CVE-2025-61730 · CVE-2025-64649 · CVE-2025-64756 · CVE-2025-67221 · CVE-2025-68121 · CVE-2025-68146 · CVE-2026-0540 · CVE-2026-2327 · CVE-2026-23490 · CVE-2026-23897 · CVE-2026-2391 · CVE-2026-23949 · CVE-2026-24486 · CVE-2026-25528 · CVE-2026-25547 · CVE-2026-25639 · CVE-2026-25990 · CVE-2026-26007 · CVE-2026-26019 · CVE-2026-26996 · CVE-2026-27142 · CVE-2026-27212 · CVE-2026-27699 · CVE-2026-27903 · CVE-2026-27904 · CVE-2026-28684 · CVE-2026-29063 · CVE-2026-29181 · CVE-2026-2950 · CVE-2026-31808 · CVE-2026-31900 · CVE-2026-32274 · CVE-2026-32288 · CVE-2026-32597 · CVE-2026-32630 · CVE-2026-32887 · CVE-2026-32952 · CVE-2026-33186 · CVE-2026-33532 · CVE-2026-33750 · CVE-2026-33814 · CVE-2026-33816 · CVE-2026-33916 · CVE-2026-34043 · CVE-2026-34073 · CVE-2026-34077 · CVE-2026-3520 · CVE-2026-35469 · CVE-2026-35515 · CVE-2026-3627 · CVE-2026-39823 · CVE-2026-39825 · CVE-2026-39826 · CVE-2026-39892 · CVE-2026-39984 · CVE-2026-40175 · CVE-2026-40179 · CVE-2026-40181 · CVE-2026-40190 · CVE-2026-40347 · CVE-2026-41066 · CVE-2026-41182 · CVE-2026-41238 · CVE-2026-41239 · CVE-2026-41240 · CVE-2026-41305 · CVE-2026-41324 · CVE-2026-41425 · CVE-2026-41481 · CVE-2026-41488 · CVE-2026-41602 · CVE-2026-41636 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-42198 · CVE-2026-42211 · CVE-2026-42338 · CVE-2026-42342 · CVE-2026-42561 · CVE-2026-42577 · CVE-2026-43870 · CVE-2026-44405 · CVE-2026-44431 · CVE-2026-44432 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44496 · CVE-2026-44728 · CVE-2026-4539 · CVE-2026-45409 · CVE-2026-45736 · CVE-2026-46625 · CVE-2026-4800 · CVE-2026-4923 · CVE-2026-4926 · CVE-2026-7246 · CVE-2026-8723
RHSA-2026:0414: Red Hat Security Advisory: A Subscription Management tool for finding and reporting Red Hat product usage
CVE-2024-5642 · CVE-2025-4598 · CVE-2025-6069 · CVE-2025-6075 · CVE-2025-8291 · CVE-2025-9714 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-45582 · CVE-2025-59375 · CVE-2025-59682 · CVE-2025-61984 · CVE-2025-61985 · CVE-2025-64460 · CVE-2025-64720 · CVE-2025-64756 · CVE-2025-65018 · CVE-2025-66031 · CVE-2025-66293 · CVE-2025-66418
RHSA-2026:2900: Red Hat Security Advisory: Network Observability 1.11.0 for OpenShift
CVE-2024-25621 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-64329 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-23745 · CVE-2026-24049 · CVE-2026-24842
RHSA-2026:33371: Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.3.18 security update
CVE-2024-29371 · CVE-2025-9784 · CVE-2025-12543 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-23184 · CVE-2025-23368 · CVE-2025-66412 · CVE-2025-69873 · CVE-2026-1002 · CVE-2026-24842
WID-SEC-W-2026-0243: Red Hat OpenShift Container Platform: Schwachstelle ermöglicht Denial of Service
CVE-2025-15284
RHSA-2026:1942: Red Hat Security Advisory: Red Hat Quay 3.15.3
CVE-2024-34156 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-47907 · CVE-2025-47913 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-58754 · CVE-2025-59420 · CVE-2025-61729 · CVE-2025-65945 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2026-21441 · CVE-2026-24049
RHSA-2026:1517: Red Hat Security Advisory: RHACS 4.8.8 security and bug fix update
CVE-2025-12816 · CVE-2025-15284 · CVE-2025-58183 · CVE-2025-61729 · CVE-2025-66031 · CVE-2025-66506 · CVE-2025-66564 · CVE-2025-68428 · CVE-2025-68973 · CVE-2026-22029
RHSA-2026:1000: Red Hat Security Advisory: OpenShift Container Platform 4.20.12 bug fix and security update
CVE-2025-15284
RHSA-2026:3710: Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.15.3
CVE-2024-37890 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-66031 · CVE-2025-66506 · CVE-2025-66564
RHSA-2026:21658: Red Hat Security Advisory: OpenShift Container Platform 4.18.43 security and extras update
CVE-2025-13465 · CVE-2025-15284 · CVE-2025-58183 · CVE-2026-4800 · CVE-2026-22029 · CVE-2026-29063 · CVE-2026-33186 · CVE-2026-35469
RHSA-2026:1596: Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.6 Container Release Update
CVE-2025-15284 · CVE-2025-62706 · CVE-2025-64459 · CVE-2025-66031 · CVE-2025-66416 · CVE-2025-66471 · CVE-2025-69223 · CVE-2026-21441
RHSA-2026:3713: Red Hat Security Advisory: RHOAI 3.3 - Red Hat OpenShift AI
CVE-2024-25621 · CVE-2025-6242 · CVE-2025-12638 · CVE-2025-12816 · CVE-2025-14180 · CVE-2025-14920 · CVE-2025-14921 · CVE-2025-14922 · CVE-2025-14924 · CVE-2025-14925 · CVE-2025-14926 · CVE-2025-14927 · CVE-2025-14928 · CVE-2025-14929 · CVE-2025-14930 · CVE-2025-15284 · CVE-2025-48956 · CVE-2025-52881 · CVE-2025-59425 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-62164 · CVE-2025-62593 · CVE-2025-64756 · CVE-2025-66031 · CVE-2025-66034 · CVE-2025-66416 · CVE-2025-66418 · CVE-2025-66448 · CVE-2025-66471 · CVE-2025-66506 · CVE-2025-66626 · CVE-2025-67725 · CVE-2025-67726 · CVE-2025-68156 · CVE-2025-68476 · CVE-2025-68665 · CVE-2025-69223 · CVE-2025-69872 · CVE-2026-0897 · CVE-2026-1260 · CVE-2026-21441 · CVE-2026-22778 · CVE-2026-22807 · CVE-2026-24049 · CVE-2026-24486
RHSA-2026:2672: Red Hat Security Advisory: OpenShift Container Platform 4.17.49 bug fix and security update
CVE-2025-13465 · CVE-2025-15284 · CVE-2025-65637
RHSA-2026:34100: Red Hat Security Advisory: OpenShift Container Platform 4.17.55 security and extras update
CVE-2025-13465 · CVE-2025-15284 · CVE-2026-4800 · CVE-2026-22029 · CVE-2026-29063 · CVE-2026-33186 · CVE-2026-35469
RHSA-2026:0261: Red Hat Security Advisory: Red Hat Developer Hub 1.7.4 release.
CVE-2025-12816 · CVE-2025-15284 · CVE-2025-64756 · CVE-2025-65945 · CVE-2025-66031
RHSA-2026:18868: Red Hat Security Advisory: linux-sgx security update
CVE-2025-13465 · CVE-2025-15284 · CVE-2026-23745 · CVE-2026-23950 · CVE-2026-24842
RHSA-2026:2147: Red Hat Security Advisory: Kiali 2.4.12 for Red Hat OpenShift Service Mesh 3.0
CVE-2025-13465 · CVE-2025-15284 · CVE-2025-61729 · CVE-2026-22029
RHSA-2026:41944: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.19.20 security, enhancement & bug fix update
CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-66031 · CVE-2025-68157 · CVE-2025-68458 · CVE-2025-69873 · CVE-2026-4800 · CVE-2026-25128 · CVE-2026-25896 · CVE-2026-26278 · CVE-2026-26996 · CVE-2026-27904 · CVE-2026-27942 · CVE-2026-29063 · CVE-2026-33036 · CVE-2026-33186 · CVE-2026-34986 · CVE-2026-48779
RHSA-2026:40984: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.20.15 security, enhancement & bug fix update
CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-66031 · CVE-2025-68157 · CVE-2025-68458 · CVE-2025-69873 · CVE-2026-4800 · CVE-2026-22029 · CVE-2026-25128 · CVE-2026-25896 · CVE-2026-26278 · CVE-2026-26996 · CVE-2026-27904 · CVE-2026-27942 · CVE-2026-29063 · CVE-2026-33036 · CVE-2026-33186 · CVE-2026-33815 · CVE-2026-33816 · CVE-2026-34986 · CVE-2026-48779
RHSA-2026:2149: Red Hat Security Advisory: Kiali 2.17.3 for Red Hat OpenShift Service Mesh 3.2
CVE-2025-13465 · CVE-2025-15284 · CVE-2025-61729 · CVE-2026-22029
RHSA-2026:83619: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.16.36 security, enhancement & bug fix update
CVE-2025-13465 · CVE-2025-15284 · CVE-2025-61726 · CVE-2025-66031 · CVE-2025-68157 · CVE-2025-68458 · CVE-2025-69873 · CVE-2026-4800 · CVE-2026-26996 · CVE-2026-27904 · CVE-2026-33186 · CVE-2026-33814 · CVE-2026-34986
- Source published
- Dec 29, 2025, 10:56:45 PM (timezone not stated)
- Source modified
- Feb 10, 2026, 8:06:42 PM (timezone not stated)
- Observed here
- 9 Nov 2026 02:12:18 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.
EUVD CVSS 4.0 · 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:L
nvd · CVE-2025-15284
PublishedImproper 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.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-20
Original publisher date fields
published: 2025-12-29T23:15:42.703
lastModified: 2026-10-14T19:10:00.297
1 source CPE criteria · context only
- cpe:2.3:a:qs_project:qs:*:*:*:*:*:node.js:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 29 Dec 2025 23:15:42 UTC
- Source modified
- 14 Oct 2026 19:10:00 UTC
- Observed here
- 25 Oct 2026 01:17:29 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 4.0 · 7ffcee3d-2c14-4c3e-b844-86c6a321a158 · Secondary · 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:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 · 7ffcee3d-2c14-4c3e-b844-86c6a321a158 · Secondary · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
osv · GHSA-6rw7-vpxm-498p
Published### 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[]=value` consumes 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`): ```javascript if (root === '[]' && options.parseArrays) { obj = utils.combine([], leaf); // No arrayLimit check } ``` **Working code** (`lib/parse.js:175`): ```javascript 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 ```javascript 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.
- Source published
- 30 Dec 2025 21:02:54 UTC
- Source modified
- 10 Sep 2026 03:50:31 UTC
- Observed here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L
Publisher rating · MODERATE