BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-8723High confidence

qs.stringify crashes on null/undefined entries in comma-format arrays under encodeValuesOnly

ljharb · qs

6.3MediumCVSS 4.0
Recommended action
Within 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 9 Sept 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.

1 current
CVE-2026-8723 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityqs: qs: Denial of Service due to improper handling of null/undefined array elements
180 known affected

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

  • openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation
  • cryostat-openshift-console-plugin-npm as a component of Cryostat 4
  • cryostat/cryostat-openshift-console-plugin-rhel9 as a component of Cryostat 4
  • grafana-infinity-datasource-npm as a component of Cryostat 4
  • qs as a component of Cryostat 4
  • gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3
  • mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8
  • mta/mta-ui-rhel8 as a component of Migration Toolkit for Applications 8
  • mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8
  • rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers
  • multicluster-engine/console-mce-rhel9 as a component of Multicluster Engine for Kubernetes
  • workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator
Summary
A flaw was found in the `qs` library. When the `qs.stringify` function processes arrays containing `null` or `undefined` elements, and is configured with both `arrayFormat: 'comma'` and `encodeValuesOnly: true`, it can trigger a `TypeError`. This error causes the application to crash or return a 500 error, leading to a Denial of Service (DoS) for affected requests.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-2026-30674

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 actionWithin 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

### Summary `qs.stringify` throws `TypeError` when called with `arrayFormat: 'comma'` and `encodeValuesOnly: true` on an array containing `null` or `undefined`. The throw is synchronous and not handled by any of qs's null-related options (`skipNulls`, `strictNullHandling`). ### Details In the comma + `encodeValuesOnly` branch, `lib/stringify.js:145` mapped the array through the raw encoder before joining: ```js obj = utils.maybeMap(obj, encoder); ``` `utils.encode` (`lib/utils.js:195`) reads `str.length` with no null guard, so a `null` or `undefined` element throws `TypeError`. `skipNulls` and `strictNullHandling` are both checked in the per-element loop below this line and never get a chance to run. Same class of bug as the filter-array path fixed in 0c180a4. The vulnerable shape of the comma + `encodeValuesOnly` branch was introduced in 4c4b23d ("encode comma values more consistently", PR #463, 2023-01-19), first released in v6.11.1. #### PoC ```js const qs = require('qs'); qs.stringify({ a: [null, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true }); qs.stringify({ a: [undefined, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true }); qs.stringify({ a: [null] }, { arrayFormat: 'comma', encodeValuesOnly: true }); // TypeError: Cannot read properties of null (reading 'length') // at encode (lib/utils.js:195:13) // at Object.maybeMap (lib/utils.js:322:37) // at stringify (lib/stringify.js:145:25) ``` #### Fix `lib/stringify.js:145`, applied in 21f80b3 on `main` and released as v6.15.2: ```diff - obj = utils.maybeMap(obj, encoder); + obj = utils.maybeMap(obj, function (v) { + return v == null ? v : encoder(v); + }); ``` `null` and `undefined` now pass through `maybeMap` unchanged and reach the `join(',')` step as-is. For `{ a: [null, 'b'] }` this produces `a=,b`, matching the non-`encodeValuesOnly` comma path (which already joins before encoding and produces `a=%2Cb` for the same input). Single-element `[null]` arrays still collapse via the existing `obj.join(',') || null` and remain subject to `skipNulls` / `strictNullHandling` in the main loop. ### Affected versions `>=6.11.1 <6.15.2` — fixed in v6.15.2. The vulnerable code shape was introduced in 4c4b23d and first shipped in v6.11.1. Earlier versions — including all of 6.7.x, 6.8.x, 6.9.x, 6.10.x, and 6.11.0 — implemented the comma + `encodeValuesOnly` path differently (joining before encoding) and are not affected. Empirically verified across released versions. ### Impact Application code that calls `qs.stringify` with both `arrayFormat: 'comma'` and `encodeValuesOnly: true` (both non-default) on input that may contain a `null` or `undefined` array element will throw synchronously instead of producing a query string. In a typical Node.js HTTP framework (Express, Fastify, Koa, hapi) the sync throw is caught by the framework's error boundary and the affected request returns a 500; the worker process does not exit and subsequent requests are unaffected. The "kills the worker process" framing applies only to call sites outside a request-handler error boundary (background jobs, startup paths, stream pipelines) or to deployments with framework error handling explicitly disabled. The vulnerable input is a `null` or `undefined` entry inside an array; this is reachable from JSON request bodies or from application code constructing arrays from user input, but not from standard HTML form submissions (which produce strings or omitted fields, not literal `null`).

What

### Summary `qs.stringify` throws `TypeError` when called with `arrayFormat: 'comma'` and `encodeValuesOnly: true` on an array containing `null` or `undefined`. The throw is synchronous and not handled by any of qs's null-related options (`skipNulls`, `strictNullHandling`). ### Details In the comma + `encodeValuesOnly` branch, `lib/stringify.js:145` mapped the array through the raw encoder before joining: ```js obj = utils.maybeMap(obj, encoder); ``` `utils.encode` (`lib/utils.js:195`) reads `str.length` with no null guard, so a `null` or `undefined` element throws `TypeError`. `skipNulls` and `strictNullHandling` are both checked in the per-element loop below this line and never get a chance to run. Same class of bug as the filter-array path fixed in 0c180a4. The vulnerable shape of the comma + `encodeValuesOnly` branch was introduced in 4c4b23d ("encode comma values more consistently", PR #463, 2023-01-19), first released in v6.11.1. #### PoC ```js const qs = require('qs'); qs.stringify({ a: [null, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true }); qs.stringify({ a: [undefined, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true }); qs.stringify({ a: [null] }, { arrayFormat: 'comma', encodeValuesOnly: true }); // TypeError: Cannot read properties of null (reading 'length') // at encode (lib/utils.js:195:13) // at Object.maybeMap (lib/utils.js:322:37) // at stringify (lib/stringify.js:145:25) ``` #### Fix `lib/stringify.js:145`, applied in 21f80b3 on `main` and released as v6.15.2: ```diff - obj = utils.maybeMap(obj, encoder); + obj = utils.maybeMap(obj, function (v) { + return v == null ? v : encoder(v); + }); ``` `null` and `undefined` now pass through `maybeMap` unchanged and reach the `join(',')` step as-is. For `{ a: [null, 'b'] }` this produces `a=,b`, matching the non-`encodeValuesOnly` comma path (which already joins before encoding and produces `a=%2Cb` for the same input). Single-element `[null]` arrays still collapse via the existing `obj.join(',') || null` and remain subject to `skipNulls` / `strictNullHandling` in the main loop. ### Affected versions `>=6.11.1 <6.15.2` — fixed in v6.15.2. The vulnerable code shape was introduced in 4c4b23d and first shipped in v6.11.1. Earlier versions — including all of 6.7.x, 6.8.x, 6.9.x, 6.10.x, and 6.11.0 — implemented the comma + `encodeValuesOnly` path differently (joining before encoding) and are not affected. Empirically verified across released versions. ### Impact Application code that calls `qs.stringify` with both `arrayFormat: 'comma'` and `encodeValuesOnly: true` (both non-default) on input that may contain a `null` or `undefined` array element will throw synchronously instead of producing a query string. In a typical Node.js HTTP framework (Express, Fastify, Koa, hapi) the sync throw is caught by the framework's error boundary and the affected request returns a 500; the worker process does not exit and subsequent requests are unaffected. The "kills the worker process" framing applies only to call sites outside a request-handler error boundary (background jobs, startup paths, stream pipelines) or to deployments with framework error handling explicitly disabled. The vulnerable input is a `null` or `undefined` entry inside an array; this is reachable from JSON request bodies or from application code constructing arrays from user input, but not from standard HTML form submissions (which produce strings or omitted fields, not literal `null`).

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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

### Summary `qs.stringify` throws `TypeError` when called with `arrayFormat: 'comma'` and `encodeValuesOnly: true` on an array containing `null` or `undefined`. The throw is synchronous and not handled by any of qs's null-related options (`skipNulls`, `strictNullHandling`). ### Details In the comma + `encodeValuesOnly` branch, `lib/stringify.js:145` mapped the array through the raw encoder before joining: ```js obj = utils.maybeMap(obj, encoder); ``` `utils.encode` (`lib/utils.js:195`) reads `str.length` with no null guard, so a `null` or `undefined` element throws `TypeError`. `skipNulls` and `strictNullHandling` are both checked in the per-element loop below this line and never get a chance to run. Same class of bug as the filter-array path fixed in 0c180a4. The vulnerable shape of the comma + `encodeValuesOnly` branch was introduced in 4c4b23d ("encode comma values more consistently", PR #463, 2023-01-19), first released in v6.11.1. #### PoC ```js const qs = require('qs'); qs.stringify({ a: [null, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true }); qs.stringify({ a: [undefined, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true }); qs.stringify({ a: [null] }, { arrayFormat: 'comma', encodeValuesOnly: true }); // TypeError: Cannot read properties of null (reading 'length') // at encode (lib/utils.js:195:13) // at Object.maybeMap (lib/utils.js:322:37) // at stringify (lib/stringify.js:145:25) ``` #### Fix `lib/stringify.js:145`, applied in 21f80b3 on `main` and released as v6.15.2: ```diff - obj = utils.maybeMap(obj, encoder); + obj = utils.maybeMap(obj, function (v) { + return v == null ? v : encoder(v); + }); ``` `null` and `undefined` now pass through `maybeMap` unchanged and reach the `join(',')` step as-is. For `{ a: [null, 'b'] }` this produces `a=,b`, matching the non-`encodeValuesOnly` comma path (which already joins before encoding and produces `a=%2Cb` for the same input). Single-element `[null]` arrays still collapse via the existing `obj.join(',') || null` and remain subject to `skipNulls` / `strictNullHandling` in the main loop. ### Affected versions `>=6.11.1 <6.15.2` — fixed in v6.15.2. The vulnerable code shape was introduced in 4c4b23d and first shipped in v6.11.1. Earlier versions — including all of 6.7.x, 6.8.x, 6.9.x, 6.10.x, and 6.11.0 — implemented the comma + `encodeValuesOnly` path differently (joining before encoding) and are not affected. Empirically verified across released versions. ### Impact Application code that calls `qs.stringify` with both `arrayFormat: 'comma'` and `encodeValuesOnly: true` (both non-default) on input that may contain a `null` or `undefined` array element will throw synchronously instead of producing a query string. In a typical Node.js HTTP framework (Express, Fastify, Koa, hapi) the sync throw is caught by the framework's error boundary and the affected request returns a 500; the worker process does not exit and subsequent requests are unaffected. The "kills the worker process" framing applies only to call sites outside a request-handler error boundary (background jobs, startup paths, stream pipelines) or to deployments with framework error handling explicitly disabled. The vulnerable input is a `null` or `undefined` entry inside an array; this is reachable from JSON request bodies or from application code constructing arrays from user input, but not from standard HTML form submissions (which produce strings or omitted fields, not literal `null`).

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → NULL Pointer Dereference → 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-476

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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:N

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.SANoneSubsequent-system availability: No direct loss is represented by this metric.
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-476Public 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-W-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-W-2026-2118IBM App Connect Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um einen Denial of Service Angriff durchzuführen, und um Informationen offenzulegen.

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

/CVERecord?id=CVE-2026-6918 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-69248 https://www.cve.org/CVERecord?id=CVE-2026-69248 Référence CVE CVE-2026-69249 https://www.cve.org/CVERecord?id=CVE-2026-69249 Référence CVE CVE-2026-7246 https://www.cve.org/CVERecord?id=CVE-2026-7246 Référence CVE CVE-2026-75838 https://www.cve.org/CVERecord?id=CVE-2026-75838 Référence CVE CVE-2026-8177 https://www.cve.org/CVERecord?id=CVE-2026-8177 Référence CVE CVE-2026-8400 https://www.cve.org/CVERecord?id=CVE-2026-8400 Référence CVE CVE-2026-8646 https://www.cve.org/CVERecord?id=CVE-2026-8646 Référence CVE CVE-2026-8723 https://www.cve.org/CVERecord?id=CVE-2026-8723 Référence CVE CVE-2026-9071 https://www.cve.org/CVERecord?id=CVE-2026-9071 Référence CVE CVE-2026-9171 https://www.cve.org/CVERecord?id=CVE-2026-9171 Référence CVE CVE-2026-9320 https://www.cve.org/CVERecord?id=CVE-2026-9320 Référence CVE CVE-2026-9322 https://www.cve.org/CVERecord?id=CVE-2026-9322 Référence CVE CVE-2026-9358 https://www.cve.org/CVERecord?id=CVE-2026-9358 Référence CVE CVE-2026-9563 https://www.cve.org/CVERecord?id=CVE-2026-9563 Référence CVE CVE-2026-9678 https://www.cve.org/CVERecord?id=CVE-2026-9678 Référence CVE CVE-2026-9679 https://www.cve.org/CVERecord?id=CVE-2026-9679 Ré

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

VERecord?id=CVE-2026-6478 Référence CVE CVE-2026-64958 https://www.cve.org/CVERecord?id=CVE-2026-64958 Référence CVE CVE-2026-65898 https://www.cve.org/CVERecord?id=CVE-2026-65898 Référence CVE CVE-2026-65899 https://www.cve.org/CVERecord?id=CVE-2026-65899 Référence CVE CVE-2026-65900 https://www.cve.org/CVERecord?id=CVE-2026-65900 Référence CVE CVE-2026-66010 https://www.cve.org/CVERecord?id=CVE-2026-66010 Référence CVE CVE-2026-6637 https://www.cve.org/CVERecord?id=CVE-2026-6637 Référence CVE CVE-2026-8368 https://www.cve.org/CVERecord?id=CVE-2026-8368 Référence CVE CVE-2026-8400 https://www.cve.org/CVERecord?id=CVE-2026-8400 Référence CVE CVE-2026-8723 https://www.cve.org/CVERecord?id=CVE-2026-8723 Référence CVE CVE-2026-8829 https://www.cve.org/CVERecord?id=CVE-2026-8829 Gestion détaillée du document le 21 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

e.org/CVERecord?id=CVE-2026-59874 Référence CVE CVE-2026-59875 https://www.cve.org/CVERecord?id=CVE-2026-59875 Référence CVE CVE-2026-6009 https://www.cve.org/CVERecord?id=CVE-2026-6009 Référence CVE CVE-2026-6100 https://www.cve.org/CVERecord?id=CVE-2026-6100 Référence CVE CVE-2026-6357 https://www.cve.org/CVERecord?id=CVE-2026-6357 Référence CVE CVE-2026-7769 https://www.cve.org/CVERecord?id=CVE-2026-7769 Référence CVE CVE-2026-8149 https://www.cve.org/CVERecord?id=CVE-2026-8149 Référence CVE CVE-2026-8286 https://www.cve.org/CVERecord?id=CVE-2026-8286 Référence CVE CVE-2026-8458 https://www.cve.org/CVERecord?id=CVE-2026-8458 Référence CVE CVE-2026-8723 https://www.cve.org/CVERecord?id=CVE-2026-8723 Référence CVE CVE-2026-8924 https://www.cve.org/CVERecord?id=CVE-2026-8924 Référence CVE CVE-2026-8927 https://www.cve.org/CVERecord?id=CVE-2026-8927 Référence CVE CVE-2026-8932 https://www.cve.org/CVERecord?id=CVE-2026-8932 Référence CVE CVE-2026-9277 https://www.cve.org/CVERecord?id=CVE-2026-9277 Référence CVE CVE-2026-9358 https://www.cve.org/CVERecord?id=CVE-2026-9358 Référence CVE CVE-2026-9547 https://www.cve.org/CVERecord?id=CVE-2026-9547 Gestion détaillée du document le 31 juillet 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Con

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

.cve.org/CVERecord?id=CVE-2026-6474 Référence CVE CVE-2026-6475 https://www.cve.org/CVERecord?id=CVE-2026-6475 Référence CVE CVE-2026-6477 https://www.cve.org/CVERecord?id=CVE-2026-6477 Référence CVE CVE-2026-6478 https://www.cve.org/CVERecord?id=CVE-2026-6478 Référence CVE CVE-2026-6479 https://www.cve.org/CVERecord?id=CVE-2026-6479 Référence CVE CVE-2026-6637 https://www.cve.org/CVERecord?id=CVE-2026-6637 Référence CVE CVE-2026-6638 https://www.cve.org/CVERecord?id=CVE-2026-6638 Référence CVE CVE-2026-6918 https://www.cve.org/CVERecord?id=CVE-2026-6918 Référence CVE CVE-2026-8646 https://www.cve.org/CVERecord?id=CVE-2026-8646 Référence CVE CVE-2026-8723 https://www.cve.org/CVERecord?id=CVE-2026-8723 Référence CVE CVE-2026-9006 https://www.cve.org/CVERecord?id=CVE-2026-9006 Référence CVE CVE-2026-9071 https://www.cve.org/CVERecord?id=CVE-2026-9071 Référence CVE CVE-2026-9311 https://www.cve.org/CVERecord?id=CVE-2026-9311 Référence CVE CVE-2026-9320 https://www.cve.org/CVERecord?id=CVE-2026-9320 Référence CVE CVE-2026-9330 https://www.cve.org/CVERecord?id=CVE-2026-9330 Gestion détaillée du document le 19 juin 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr

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.
Patch available
Affected
openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; cryostat/cryostat-openshift-console-plugin-rhel9 as a component of Cryostat 4; grafana-infinity-datasource-npm as a component of Cryostat 4; qs as a component of Cryostat 4; gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3; mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel8 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; multicluster-engine/console-mce-rhel9 as a component of Multicluster Engine for Kubernetes; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; workload-availability/node-remediation-console-rhel8 as a component of Node HealthCheck Operator; openshift-lightspeed/lightspeed-console-plugin-419-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-pf5-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel9 as a component of OpenShift Pipelines; openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless; and 150 more
Fixed
dotnet8-0-main@src as a component of Red Hat Hardened Images; nodejs20-main@aarch64 as a component of Red Hat Hardened Images; nodejs20-main@noarch as a component of Red Hat Hardened Images; nodejs20-main@src as a component of Red Hat Hardened Images; nodejs20-main@x86_64 as a component of Red Hat Hardened Images; python3-14-main@aarch64 as a component of Red Hat Hardened Images; python3-14-main@src as a component of Red Hat Hardened Images; python3-14-main@x86_64 as a component of Red Hat Hardened Images
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
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.
04

Evidence and provenance

Published 16 May 2026 · Last source change 18 May 2026, 14:02 UTC · CWE-476 · NULL Pointer Dereference

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-2026-30674
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; cryostat/cryostat-openshift-console-plugin-rhel9 as a component of Cryostat 4; grafana-infinity-datasource-npm as a component of Cryostat 4; qs as a component of Cryostat 4; gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3; mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel8 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; multicluster-engine/console-mce-rhel9 as a component of Multicluster Engine for Kubernetes; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; workload-availability/node-remediation-console-rhel8 as a component of Node HealthCheck Operator; openshift-lightspeed/lightspeed-console-plugin-419-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-pf5-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel9 as a component of OpenShift Pipelines; openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless; and 151 more · Fixed: nodejs20-main@aarch64 as a component of Red Hat Hardened Images; nodejs20-main@noarch as a component of Red Hat Hardened Images; nodejs20-main@src as a component of Red Hat Hardened Images; nodejs20-main@x86_64 as a component of Red Hat Hardened Images; python3-14-main@aarch64 as a component of Red Hat Hardened Images; python3-14-main@src as a component of Red Hat Hardened Images; python3-14-main@x86_64 as a component of Red Hat Hardened Images
    After
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; cryostat/cryostat-openshift-console-plugin-rhel9 as a component of Cryostat 4; grafana-infinity-datasource-npm as a component of Cryostat 4; qs as a component of Cryostat 4; gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3; mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel8 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; multicluster-engine/console-mce-rhel9 as a component of Multicluster Engine for Kubernetes; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; workload-availability/node-remediation-console-rhel8 as a component of Node HealthCheck Operator; openshift-lightspeed/lightspeed-console-plugin-419-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-pf5-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel9 as a component of OpenShift Pipelines; openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless; and 150 more · Fixed: dotnet8-0-main@src as a component of Red Hat Hardened Images; nodejs20-main@aarch64 as a component of Red Hat Hardened Images; nodejs20-main@noarch as a component of Red Hat Hardened Images; nodejs20-main@src as a component of Red Hat Hardened Images; nodejs20-main@x86_64 as a component of Red Hat Hardened Images; python3-14-main@aarch64 as a component of Red Hat Hardened Images; python3-14-main@src as a component of Red Hat Hardened Images; python3-14-main@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; cryostat/cryostat-openshift-console-plugin-rhel9 as a component of Cryostat 4; grafana-infinity-datasource-npm as a component of Cryostat 4; qs as a component of Cryostat 4; gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3; mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel8 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; multicluster-engine/console-mce-rhel9 as a component of Multicluster Engine for Kubernetes; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; workload-availability/node-remediation-console-rhel8 as a component of Node HealthCheck Operator; openshift-lightspeed/lightspeed-console-plugin-419-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-pf5-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel9 as a component of OpenShift Pipelines; openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless; and 152 more · Fixed: python3-14-main@aarch64 as a component of Red Hat Hardened Images; python3-14-main@src as a component of Red Hat Hardened Images; python3-14-main@x86_64 as a component of Red Hat Hardened Images
    After
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; cryostat/cryostat-openshift-console-plugin-rhel9 as a component of Cryostat 4; grafana-infinity-datasource-npm as a component of Cryostat 4; qs as a component of Cryostat 4; gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3; mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel8 as a component of Migration Toolkit for Applications 8; mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 8; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; multicluster-engine/console-mce-rhel9 as a component of Multicluster Engine for Kubernetes; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; workload-availability/node-remediation-console-rhel8 as a component of Node HealthCheck Operator; openshift-lightspeed/lightspeed-console-plugin-419-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-pf5-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-console-plugin-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-hub-ui-rhel9 as a component of OpenShift Pipelines; openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless; and 151 more · Fixed: nodejs20-main@aarch64 as a component of Red Hat Hardened Images; nodejs20-main@noarch as a component of Red Hat Hardened Images; nodejs20-main@src as a component of Red Hat Hardened Images; nodejs20-main@x86_64 as a component of Red Hat Hardened Images; python3-14-main@aarch64 as a component of Red Hat Hardened Images; python3-14-main@src as a component of Red Hat Hardened Images; python3-14-main@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-2026-8723 · cve.blacktree.nl