BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-15284High confidence

arrayLimit bypass in bracket notation allows DoS via memory exhaustion

Unknown · Unknown

Official source article: GitHub GHSA-6RW7-VPXM-498P ↗. Check the applicable product and release in the original source.

6.3MediumCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 10 Feb 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.45% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-qsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcenode-qsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcenode-qsVendor fix publishedDebian records a fixed source-package version for this release.6.14.1+ds+~6.14.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcenode-qsVendor fix publishedDebian records a fixed source-package version for this release.6.14.1+ds+~6.14.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenode-qsUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmqs< 6.14.16.14.1GitHub advisory ↗upstream repository advisory · 2 Mar 2026
npmqsSEMVER: introduced 0; fixed 6.14.16.14.1OSV record ↗aggregator derived · 10 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2025-15284 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityqs: qs: Denial of Service via improper input validation in array parsing
80 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openshift-logging/cluster-logging-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/cluster-logging-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/elasticsearch-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/elasticsearch-proxy-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/elasticsearch-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/elasticsearch6-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/eventrouter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/fluentd-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/kibana6-rhel8 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/log-file-metric-exporter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/logging-curator5-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/logging-view-plugin-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
Summary
A flaw was found in qs, a module used for parsing query strings. A remote attacker can exploit an improper input validation vulnerability by sending specially crafted HTTP requests that use bracket notation (e.g., `a[]=value`). This bypasses the `arrayLimit` option, which is designed to limit the size of parsed arrays and prevent resource exhaustion. Successful exploitation can lead to memory exhaustion, causing a Denial of Service (DoS) where the application crashes or becomes unresponsive, making the service unavailable to users.
Remediation
Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
SSA-485750 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-485750: Multiple Vulnerabilities in SIDIS Prime Before V4.0.800
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIDIS Prime
Summary
Improper Input Validation vulnerability in qs (parse modules) allows HTTP DoS.This issue affects qs: < 6.14.1. SummaryThe arrayLimit option in qs does not enforce limits for bracket notation (a[]=1&a[]=2), allowing attackers to cause denial-of-service via memory exhaustion. Applications using arrayLimit for DoS protection are vulnerable. DetailsThe arrayLimit option only checks limits for indexed notation (a[0]=1&a[1]=2) but completely bypasses 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. PoCTest 1 - Basic bypass: npm install qs 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) Test 2 - DoS demonstration: const qs = require('qs'); const attack = 'a[]=' + Array(10000).fill('x').join('&a[]='); const result = qs.parse(attack, { arrayLimit: 100 }); console.log(result.a.length); // Output: 10000 (should be max 100) Configuration: * arrayLimit: 5 (test 1) or arrayLimit: 100 (test 2) * Use bracket notation: a[]=value (not indexed a[0]=value) ImpactDenial of Service via memory exhaustion. Affects applications using qs.parse() with user-controlled input and arrayLimit for protection. Attack scenario: * Attacker sends HTTP request: GET /api/search?filters[]=x&filters[]=x&...&filters[]=x (100,000+ times) * Application parses with qs.parse(query, { arrayLimit: 100 }) * qs ignores limit, parses all 100,000 elements into array * Server memory exhausted → application crashes or becomes unresponsive * Service unavailable for all users Real-world impact: * Single malicious request can crash server * No authentication required * Easy to automate and scale * Affects any endpoint parsing query strings with bracket notation
Remediation
Update to V4.0.800 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-205660

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Input Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SALowSubsequent-system availability: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-20Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-3046IBM Concert: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Concert ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-1194Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-0177Atlassian Bamboo, Bitbucket, Confluence und Jira: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, um einen Denial of Service Angriff durchzuführen, und um einen Cross-Site Scripting Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0759IBM Planning Analytics: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Planning Analytics ausnutzen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-0301IBM App Connect Enterprise: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM App Connect Enterprise ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0243Red Hat OpenShift Container Platform: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat OpenShift Container Platform ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0181ILIAS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in ILIAS ausnutzen, um einen Denial of Service Angriff durchzuführen, und um einen Cross-Site Scripting Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0105Red Hat Developer Hub: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Red Hat Developer Hub ausnutzen, um einen Denial of Service Angriff durchzuführen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen und Daten zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2026-0943IBM DataPower Gateway: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM DataPower Gateway ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251231Security Bulletin 31 Dec 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 31 Dec 2025, published on 31 December 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2020-15366 Référence CVE CVE-2021-23337 https://www.cve.org/CVERecord?id=CVE-2021-23337 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-3517 https://www.cve.org/CVERecord?id=CVE-2022-3517 Référence CVE CVE-2024-55565 https://www.cve.org/CVERecord?id=CVE-2024-55565 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-27152 https://www.cve.org/CVERecord?id=CVE-2025-27152 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-39902 https://www.cve.org/CVERecord?id=CVE-2025-39902 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-46653 https://www.cve.org/CVERecord?id=CVE-2025-46653 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-58754 https://www.cve.org/CVERecord?id=CVE-2025-58754 Référence CVE CVE-2025-5889 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0958Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2024-45337 Référence CVE CVE-2024-52046 https://www.cve.org/CVERecord?id=CVE-2024-52046 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-2025-11187 Référence CVE CVE-2025-12183 https://www.cve.org/CVERecord?id=CVE-2025-12183 Référence CVE CVE-2025-12758 https://www.cve.org/CVERecord?id=CVE-2025-12758 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=CVE-2025-15469 Référence CVE CVE-2025-21502 https://www.cve.org/CVERecord?id=CVE-2025-21502 Référence CVE CVE-2025-22228 https://www.cve.org/CVERecord?id=CVE-2025-22228 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-47935 https://www.cve.org/CVERecord?id=CVE-2025-47935 Référence CVE CVE-2025-47944 https://www.cve.org/CVERecord?id=CVE-2025-47944 Référence CVE CVE-2025-48387 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0901Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2024-37891 Référence CVE CVE-2024-39689 https://www.cve.org/CVERecord?id=CVE-2024-39689 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-52804 https://www.cve.org/CVERecord?id=CVE-2024-52804 Référence CVE CVE-2024-6485 https://www.cve.org/CVERecord?id=CVE-2024-6485 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-14505 https://www.cve.org/CVERecord?id=CVE-2025-14505 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-15599 https://www.cve.org/CVERecord?id=CVE-2025-15599 Référence CVE CVE-2025-23165 https://www.cve.org/CVERecord?id=CVE-2025-23165 Référence CVE CVE-2025-47287 https://www.cve.org/CVERecord?id=CVE-2025-47287 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-59436 https://www.cve.org/CVERecord?id=CVE-2025-59436 Référence CVE CVE-2025-59437 https://www.cve.org/CVERecord?id=CVE-2025-59437 Référence CVE CVE-2025-59471 https://www.cve.org/CVERecord?id=CVE-2025-59471 Référence CVE CVE-2025-59472 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0834Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2024-29869 Référence CVE CVE-2024-7531 https://www.cve.org/CVERecord?id=CVE-2024-7531 Référence CVE CVE-2025-12183 https://www.cve.org/CVERecord?id=CVE-2025-12183 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-1371 https://www.cve.org/CVERecord?id=CVE-2025-1371 Référence CVE CVE-2025-13755 https://www.cve.org/CVERecord?id=CVE-2025-13755 Référence CVE CVE-2025-1376 https://www.cve.org/CVERecord?id=CVE-2025-1376 Référence CVE CVE-2025-1377 https://www.cve.org/CVERecord?id=CVE-2025-1377 Référence CVE CVE-2025-14688 https://www.cve.org/CVERecord?id=CVE-2025-14688 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-1795 https://www.cve.org/CVERecord?id=CVE-2025-1795 Référence CVE CVE-2025-36122 https://www.cve.org/CVERecord?id=CVE-2025-36122 Référence CVE CVE-2025-4516 https://www.cve.org/CVERecord?id=CVE-2025-4516 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-2025-48924 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-50182 https://www.cve.org/CVERecord?id=CVE-2025-50182 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0667Multiples vulnérabilités dans les produits IBM

rd?id=CVE-2024-9902 Référence CVE CVE-2025-11953 https://www.cve.org/CVERecord?id=CVE-2025-11953 Référence CVE CVE-2025-12635 https://www.cve.org/CVERecord?id=CVE-2025-12635 Référence CVE CVE-2025-12758 https://www.cve.org/CVERecord?id=CVE-2025-12758 Référence CVE CVE-2025-12816 https://www.cve.org/CVERecord?id=CVE-2025-12816 Référence CVE CVE-2025-13333 https://www.cve.org/CVERecord?id=CVE-2025-13333 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-14009 https://www.cve.org/CVERecord?id=CVE-2025-14009 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-40252 https://www.cve.org/CVERecord?id=CVE-2025-40252 Référence CVE CVE-2025-41248 https://www.cve.org/CVERecord?id=CVE-2025-41248 Référence CVE CVE-2025-41249 https://www.cve.org/CVERecord?id=CVE-2025-41249 Référence CVE CVE-2025-5187 https://www.cve.org/CVERecord?id=CVE-2025-5187 Référence CVE CVE-2025-53643 https://www.cve.org/CVERecord?id=CVE-2025-53643 Référence CVE CVE-2025-58754 https://www.cve.org/CVERecord?id=CVE-2025-58754 Référence CVE CVE-2025-59471 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0641Multiples vulnérabilités dans les produits IBM

d?id=CVE-2021-43784 Référence CVE CVE-2023-47038 https://www.cve.org/CVERecord?id=CVE-2023-47038 Référence CVE CVE-2024-45310 https://www.cve.org/CVERecord?id=CVE-2024-45310 Référence CVE CVE-2024-47072 https://www.cve.org/CVERecord?id=CVE-2024-47072 Référence CVE CVE-2024-50301 https://www.cve.org/CVERecord?id=CVE-2024-50301 Référence CVE CVE-2025-12801 https://www.cve.org/CVERecord?id=CVE-2025-12801 Référence CVE CVE-2025-13867 https://www.cve.org/CVERecord?id=CVE-2025-13867 Référence CVE CVE-2025-14689 https://www.cve.org/CVERecord?id=CVE-2025-14689 Référence CVE CVE-2025-14831 https://www.cve.org/CVERecord?id=CVE-2025-14831 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-21614 https://www.cve.org/CVERecord?id=CVE-2025-21614 Référence CVE CVE-2025-22227 https://www.cve.org/CVERecord?id=CVE-2025-22227 Référence CVE CVE-2025-2668 https://www.cve.org/CVERecord?id=CVE-2025-2668 Référence CVE CVE-2025-27221 https://www.cve.org/CVERecord?id=CVE-2025-27221 Référence CVE CVE-2025-32988 https://www.cve.org/CVERecord?id=CVE-2025-32988 Référence CVE CVE-2025-32989 https://www.cve.org/CVERecord?id=CVE-2025-32989 Référence CVE CVE-2025-32990 https://www.cve.org/CVERecord?id=CVE-2025-32990 Référence CVE CVE-2025-33042 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0523Multiples vulnérabilités dans les produits IBM

w.ibm.com/support/pages/node/7270827 Bulletin de sécurité IBM 7270845 du 27 avril 2026 https://www.ibm.com/support/pages/node/7270845 Bulletin de sécurité IBM 7270868 du 27 avril 2026 https://www.ibm.com/support/pages/node/7270868 Bulletin de sécurité IBM 7270869 du 27 avril 2026 https://www.ibm.com/support/pages/node/7270869 Référence CVE CVE-2021-23337 https://www.cve.org/CVERecord?id=CVE-2021-23337 Référence CVE CVE-2024-29371 https://www.cve.org/CVERecord?id=CVE-2024-29371 Référence CVE CVE-2024-31033 https://www.cve.org/CVERecord?id=CVE-2024-31033 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-15599 https://www.cve.org/CVERecord?id=CVE-2025-15599 Référence CVE CVE-2025-66035 https://www.cve.org/CVERecord?id=CVE-2025-66035 Référence CVE CVE-2025-66412 https://www.cve.org/CVERecord?id=CVE-2025-66412 Référence CVE CVE-2025-67030 https://www.cve.org/CVERecord?id=CVE-2025-67030 Référence CVE CVE-2025-68470 https://www.cve.org/CVERecord?id=CVE-2025-68470 Référence CVE CVE-2026-0540 https://www.cve.org/CVERecord?id=CVE-2026-0540 Référence CVE CVE-2026-22029 https://www.cve.org/CVERecord?id=CVE-2026-22029 Référence CVE CVE-2026-22610 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0281Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2025-13227 Référence CVE CVE-2025-13228 https://www.cve.org/CVERecord?id=CVE-2025-13228 Référence CVE CVE-2025-13229 https://www.cve.org/CVERecord?id=CVE-2025-13229 Référence CVE CVE-2025-13230 https://www.cve.org/CVERecord?id=CVE-2025-13230 Référence CVE CVE-2025-13601 https://www.cve.org/CVERecord?id=CVE-2025-13601 Référence CVE CVE-2025-14087 https://www.cve.org/CVERecord?id=CVE-2025-14087 Référence CVE CVE-2025-14104 https://www.cve.org/CVERecord?id=CVE-2025-14104 Référence CVE CVE-2025-14512 https://www.cve.org/CVERecord?id=CVE-2025-14512 Référence CVE CVE-2025-14874 https://www.cve.org/CVERecord?id=CVE-2025-14874 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-15467 https://www.cve.org/CVERecord?id=CVE-2025-15467 Référence CVE CVE-2025-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-1594 https://www.cve.org/CVERecord?id=CVE-2025-1594 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0249Multiples vulnérabilités dans les produits IBM

rg/CVERecord?id=CVE-2024-6531 Référence CVE CVE-2024-7143 https://www.cve.org/CVERecord?id=CVE-2024-7143 Référence CVE CVE-2024-8176 https://www.cve.org/CVERecord?id=CVE-2024-8176 Référence CVE CVE-2024-8184 https://www.cve.org/CVERecord?id=CVE-2024-8184 Référence CVE CVE-2024-9042 https://www.cve.org/CVERecord?id=CVE-2024-9042 Référence CVE CVE-2025-0426 https://www.cve.org/CVERecord?id=CVE-2025-0426 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-13867 https://www.cve.org/CVERecord?id=CVE-2025-13867 Référence CVE CVE-2025-14689 https://www.cve.org/CVERecord?id=CVE-2025-14689 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-15467 https://www.cve.org/CVERecord?id=CVE-2025-15467 Référence CVE CVE-2025-1767 https://www.cve.org/CVERecord?id=CVE-2025-1767 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-21613 https://www.cve.org/CVERecord?id=CVE-2025-21613 Référence CVE CVE-2025-21905 https://www.cve.org/CVERecord?id=CVE-2025-21905 Référence CVE CVE-2025-22085 https://www.cve.org/CVERecord?id=CVE-2025-22085 Référence CVE CVE-2025-22091 https://www.cve.org/CVERecord?id=CVE-2025-22091 Référence CVE CVE-2025-22113 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0224Multiples vulnérabilités dans les produits IBM

2026 https://www.ibm.com/support/pages/node/7261890 Bulletin de sécurité IBM 7261935 du 26 février 2026 https://www.ibm.com/support/pages/node/7261935 Bulletin de sécurité IBM 7261959 du 26 février 2026 https://www.ibm.com/support/pages/node/7261959 Référence CVE CVE-2023-53673 https://www.cve.org/CVERecord?id=CVE-2023-53673 Référence CVE CVE-2024-29371 https://www.cve.org/CVERecord?id=CVE-2024-29371 Référence CVE CVE-2025-12816 https://www.cve.org/CVERecord?id=CVE-2025-12816 Référence CVE CVE-2025-13601 https://www.cve.org/CVERecord?id=CVE-2025-13601 Référence CVE CVE-2025-14847 https://www.cve.org/CVERecord?id=CVE-2025-14847 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=CVE-2025-39993 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40240 https://www.cve.org/CVERecord?id=CVE-2025-40240 Référence CVE CVE-2025-40248 https://www.cve.org/CVERecord?id=CVE-2025-40248 Référence CVE CVE-2025-40277 https://www.cve.org/CVERecord?id=CVE-2025-40277 Référence CVE CVE-2025-61140 https://www.cve.org/CVERecord?id=CVE-2025-61140 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CVE-2025-64756 Référence CVE CVE-2025-65106 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0196Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0188Multiples vulnérabilités dans les produits Splunk

de sécurité Splunk SVD-2026-0208 du 18 février 2026 https://advisory.splunk.com/advisories/SVD-2026-0208 Bulletin de sécurité Splunk SVD-2026-0209 du 18 février 2026 https://advisory.splunk.com/advisories/SVD-2026-0209 Bulletin de sécurité Splunk SVD-2026-0210 du 18 février 2026 https://advisory.splunk.com/advisories/SVD-2026-0210 Bulletin de sécurité Splunk SVD-2026-0211 du 18 février 2026 https://advisory.splunk.com/advisories/SVD-2026-0211 Bulletin de sécurité Splunk SVD-2026-0212 du 18 février 2026 https://advisory.splunk.com/advisories/SVD-2026-0212 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23166 https://www.cve.org/CVERecord?id=CVE-2025-23166 Référence CVE CVE-2025-27210 https://www.cve.org/CVERecord?id=CVE-2025-27210 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2025-47907 Référence CVE CVE-2025-47912 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0171Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0112Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-11413 Référence CVE CVE-2025-11414 https://www.cve.org/CVERecord?id=CVE-2025-11414 Référence CVE CVE-2025-11494 https://www.cve.org/CVERecord?id=CVE-2025-11494 Référence CVE CVE-2025-12817 https://www.cve.org/CVERecord?id=CVE-2025-12817 Référence CVE CVE-2025-12818 https://www.cve.org/CVERecord?id=CVE-2025-12818 Référence CVE CVE-2025-13601 https://www.cve.org/CVERecord?id=CVE-2025-13601 Référence CVE CVE-2025-14087 https://www.cve.org/CVERecord?id=CVE-2025-14087 Référence CVE CVE-2025-14512 https://www.cve.org/CVERecord?id=CVE-2025-14512 Référence CVE CVE-2025-14762 https://www.cve.org/CVERecord?id=CVE-2025-14762 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-22228 https://www.cve.org/CVERecord?id=CVE-2025-22228 Référence CVE CVE-2025-22233 https://www.cve.org/CVERecord?id=CVE-2025-22233 Référence CVE CVE-2025-22235 https://www.cve.org/CVERecord?id=CVE-2025-22235 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0065Multiples vulnérabilités dans les produits Atlassian

De multiples vulnérabilités ont été découvertes dans les produits Atlassian. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-026171qs projectのqsにおける入力確認に関する脆弱性

qs（parseモジュール）の不適切な入力検証の脆弱性によりHTTP DoSが発生します。この問題はqsのバージョン6.14.1未満に影響します。概要として、qsのarrayLimitオプションは角括弧表記（a[]=1&a[]=2）には制限を適用せず、インデックス表記（a[0]=1）にのみ制限を適用していました。これは一貫性のバグであり、arrayLimitはすべての配列表記に均一に適用されるべきです。注意点として、デフォルトのparameterLimit（1000）が当初説明されたDoSシナリオを実質的に軽減します。デフォルトオプションでは、角括弧表記はarrayLimitに関わらずparameterLimitを超える配列を生成できません。これは各a[]=valueが1つのパラメータスロットを消費するためです。このため、深刻度は適宜軽減されています。詳細として、arrayLimitオプションはインデックス表記（a[0]=1&a[1]=2）にのみ制限をチェックし、角括弧表記（a[]=1&a[]=2）には適用していませんでした。脆弱なコード(lib/parse.js:159-162)は、if (root === '[]' && options.parseArrays) {obj = utils.combine([], leaf); // arrayLimitチェックなし}となっており、動作コード(lib/parse.js:175)はelse if (index = options.arrayLimit) {obj = []; obj[index] = leaf;}と記述されています。角括弧表記のハンドラ（159行目）はoptions.arrayLimitを検証せずにutils.combine([], leaf)を使用していますが、インデックス表記（175行目）はindex = options.arrayLimitをチェックしています。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); // 出力：6（最大5であるべき）。パラメータ制限の注意点として、元の勧告のDoSデモは長さ10,000と主張しましたが、parameterLimit（デフォルト1000）が解析パラメータを最大1,000に制限します。デフォルト設定の場合、実際の出力は10,000ではなく1,000になります。影響としては、arrayLimit適用の一貫性のバグであり、デフォルトのparameterLimitが既に解析パラメータ数（および角括弧表記からの配列要素数）を制限しているため、実際のDoSリスクはほとんどありません。リスクはparameterLimitを非常に高く設定した場合にのみ増加します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0079Kwetsbaarheden verholpen in Siemens producten

The qs library's `arrayLimit` option fails to enforce limits on bracket notation arrays, enabling denial-of-service attacks via memory exhaustion by parsing large arrays from user input.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0034Kwetsbaarheden verholpen in Atlassian producten

The `qs` module's `arrayLimit` option is vulnerable to denial-of-service attacks due to its failure to enforce limits for bracket notation, allowing attackers to exploit memory exhaustion.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 29 Dec 2025 · Last source change 10 Feb 2026, 20:06 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-205660
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 6.14.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 6.14.1 · Fixed: Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-205660↗Red Hat Product Security security advisory↗Public exploit reference · GitHub GHSA-6RW7-VPXM-498P↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-15284 · cve.blacktree.nl