Red Hat Security Advisory: Red Hat OpenShift Data Foundation 5.0.0 security, enhancement & bug fix update
🔗 CVE IDs covered (88)
📋 Description
CVE-2017-16137 — nodejs-debug: Regular expression Denial of Service
CVE-2020-7598 — nodejs-minimist: prototype pollution allows adding or modifying properties of Object.prototype using a constructor or proto payload
CVE-2020-7608 — nodejs-yargs-parser: prototype pollution vulnerability
CVE-2020-7610 — bson: Deserialization of Untrusted Data could result in Code injection or Excessive CPU load
CVE-2020-7788 — nodejs-ini: Prototype pollution via malicious INI file
CVE-2020-8203 — nodejs-lodash: prototype pollution in zipObjectDeep function
CVE-2020-8237 — nodejs-json-bigint: Prototype pollution via __proto__ assignment could result in DoS
CVE-2020-15168 — node-fetch: size of data after fetch() JS thread leads to DoS
CVE-2020-15366 — nodejs-ajv: prototype pollution via crafted JSON schema in ajv.validate function
CVE-2020-28500 — nodejs-lodash: ReDoS via the toNumber, trim and trimEnd functions
CVE-2021-3807 — nodejs-ansi-regex: Regular expression denial of service (ReDoS) matching ANSI escape codes
CVE-2021-23337 — nodejs-lodash: command injection via template
CVE-2021-23343 — nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe
CVE-2021-32640 — nodejs-ws: Specially crafted value of the Sec-Websocket-Protocol header can be used to significantly slow down a ws server
CVE-2021-32804 — nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite
CVE-2021-37701 — nodejs-tar: Insufficient symlink protection due to directory cache poisoning using symbolic links allowing arbitrary file creation and overwrite
CVE-2021-37712 — nodejs-tar: Insufficient symlink protection due to directory cache poisoning using symbolic links allowing arbitrary file creation and overwrite
CVE-2021-37713 — nodejs-tar: Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization
CVE-2021-43138 — async: Prototype Pollution in async
CVE-2021-44906 — minimist: prototype pollution
CVE-2022-0235 — node-fetch: exposure of sensitive information to an unauthorized actor
CVE-2022-3517 — nodejs-minimatch: ReDoS via the braceExpand function
CVE-2022-23539 — jsonwebtoken: Unrestricted key type could lead to legacy keys usagen
CVE-2022-23540 — jsonwebtoken: Insecure default algorithm in jwt.verify() could lead to signature validation bypass
CVE-2022-23541 — jsonwebtoken: Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC
CVE-2022-24785 — Moment.js: Path traversal in moment.locale
CVE-2022-24999 — express: "qs" prototype poisoning causes the hang of the node process
CVE-2022-25883 — nodejs-semver: Regular expression denial of service
CVE-2022-31129 — moment: inefficient parsing algorithm resulting in DoS
CVE-2023-0842 — node-xml2js: xml2js is vulnerable to prototype pollution
CVE-2023-45133 — babel: arbitrary code execution
CVE-2024-21538 — cross-spawn: regular expression denial of service
CVE-2024-28863 — node-tar: denial of service while parsing a tar file due to lack of folders depth validation
CVE-2024-29041 — express: cause malformed URLs to be evaluated
CVE-2024-37890 — nodejs-ws: denial of service when handling a request with many HTTP headers
CVE-2024-43796 — express: Improper Input Handling in Express Redirects
CVE-2024-43799 — send: Code Execution Vulnerability in Send Library
CVE-2024-43800 — serve-static: Improper Sanitization in serve-static
CVE-2024-45296 — path-to-regexp: Backtracking regular expressions cause ReDoS
CVE-2024-45590 — body-parser: Denial of Service Vulnerability in body-parser
CVE-2024-47764 — cookie: cookie accepts cookie name, path, and domain with out of bounds characters
CVE-2024-52798 — path-to-regexp: path-to-regexp Unpatched path-to-regexp ReDoS in 0.1.x
CVE-2025-5889 — brace-expansion: juliangruber brace-expansion index.js expand redos
CVE-2025-7339 — on-headers: on-headers vulnerable to http response header manipulation
CVE-2025-7783 — form-data: Unsafe random function in form-data
CVE-2025-8766 — noobaa-core: Excessive permissions of /etc could lead to escalation of privilege in the noobaa-core container
CVE-2025-13465 — lodash: prototype pollution in _.unset and _.omit functions
CVE-2025-64718 — js-yaml: js-yaml prototype pollution in merge
CVE-2025-65945 — node-jws: auth0/node-jws: Improper signature verification in HS256 algorithm
CVE-2025-69873 — ajv: ReDoS via $data reference
CVE-2026-2391 — qs: qs's arrayLimit bypass in comma parsing allows denial of service
CVE-2026-2950 — lodash: Lodash: Prototype pollution allows deletion of built-in prototype properties via array path bypass
CVE-2026-4800 — lodash: lodash: Arbitrary code execution via untrusted input in template imports
CVE-2026-4867 — path-to-regexp: path-to-regexp: Denial of Service via catastrophic backtracking from malformed URL parameters
CVE-2026-12143 — form-data: form-data: Form field override via CRLF injection
CVE-2026-12590 — body-parser: body-parser: Denial of Service via invalid limit option
CVE-2026-13149 — brace-expansion: Brace-expansion: Denial of Service due to exponential-time complexity
CVE-2026-23745 — node-tar: tar: node-tar: Arbitrary file overwrite and symlink poisoning via unsanitized linkpaths in archives
CVE-2026-23950 — node-tar: tar: node-tar: Arbitrary file overwrite via Unicode path collision race condition
CVE-2026-24842 — node-tar: tar: node-tar: Arbitrary file creation via path traversal bypass in hardlink security check
CVE-2026-26960 — node-tar: node-tar: Arbitrary file read/write via malicious archive hardlink creation
CVE-2026-26996 — minimatch: minimatch: Denial of Service via specially crafted glob patterns
CVE-2026-27903 — minimatch: minimatch: Denial of Service due to unbounded recursive backtracking via crafted glob patterns
CVE-2026-27904 — minimatch: Minimatch: Denial of Service via catastrophic backtracking in glob expressions
CVE-2026-29786 — node-tar: hardlink path traversal via drive-relative linkpath
CVE-2026-31802 — tar: tar: File overwrite via drive-relative symlink traversal
CVE-2026-33532 — yaml: yaml: Denial of Service via deeply nested YAML document parsing
CVE-2026-33750 — brace-expansion: brace-expansion: Denial of Service via zero step value in brace pattern
CVE-2026-48779 — ws: ws: Denial of Service via memory exhaustion from small WebSocket fragments
CVE-2026-53550 — js-yaml: js-yaml: Denial of Service via crafted YAML merge keys
CVE-2026-53655 — node-tar: node-tar: File smuggling due to inconsistent tar archive parsing
CVE-2026-56851 — golang.org/x/text: golang.org/x/text: Denial of Service via out-of-bounds slice error in Nickname profile
CVE-2026-59869 — js-yaml: js-yaml: Denial of Service via crafted YAML documents
CVE-2026-59871 — node-tar: node-tar: Denial of Service due to incorrect PAX path handling
CVE-2026-59873 — tar: node-tar: Denial of Service via crafted gzip bomb
CVE-2026-59874 — tar: Node-tar: Denial of Service via malformed tar archive header
CVE-2026-59875 — node-tar: node-tar: Denial of Service via crafted archive with NUL bytes in metadata
CVE-2026-61801 — github.com/moby/sys/user: moby/sys/user: Denial of Service via crafted user or group database files
CVE-2026-69152 — brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation
CVE-2026-73566 — tar: node-tar: Denial of Service via crafted long-path tar archive
CVE-2026-82417 — qs: qs: Denial of Service via improper validation in stringify function
CVE-2026-84304 — google.golang.org/grpc: gRPC-Go: Denial of Service via HTTP/2 DATA Frame Fragmentation
CVE-2026-84375 — js-yaml: js-yaml: Denial of Service vulnerability in YAML parsing
CVE-2026-87776 — compression: compression: Denial of Service via memory leak on premature response close
CVE-2026-90711 — proxy-addr: proxy-addr vulnerable to IP spoofing via IPv4-mapped IPv6 trust subnet
CVE-2026-102276 — brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns
CVE-2026-102277 — brace-expansion: brace-expansion: Denial of Service via crafted brace patterns
CVE-2026-102278 — brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns
🎯 Affected products129
- Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/cephcsi-operator-bundle@sha256:6dfe9ef65f59fc5fc620611e6c2c5fa7cbbd6575c4e936d3ad96599b01e6dda1_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/cephcsi-rhel9-operator@sha256:3954ff5c8da1993547303c641604c2002739edc878a0a2062d17e6cea4071cda_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/cephcsi-rhel9-operator@sha256:8376d6e4c62bf903f9e2c1c1f4e45c8a7c6c617655ed8f5153e4e3dfc8b4a4eb_arm64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/cephcsi-rhel9-operator@sha256:d737ed13a06e36bb93c17728393a7c216f5667d0233df7556c3786fac82bb260_ppc64le as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/cephcsi-rhel9-operator@sha256:dade610585b4e1e159bd40785ce6d69194a0fd7e8ef40e1ed51384a642d74b8a_s390x as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/cephcsi-rhel9@sha256:8a9a05194af5c2dab7a8ebbe4d1bcbe3fdfd2f93a680a963a246ec47549eb62c_ppc64le as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/cephcsi-rhel9@sha256:acb5843a600baec7676a2c1649dba00ceba6570ac03cf7df93f777fc09bbfd6d_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/cephcsi-rhel9@sha256:d4aed7f044ecad6e3dc7ff71a2a0259cae69f222e11a87d627cc1db887a52dcc_arm64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/cephcsi-rhel9@sha256:f8d58f3536b4a2f5c9489b911a933e1f95bb662840034e9d9d80da33a2dc490c_s390x as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/devicefinder-rhel9@sha256:33df00c12005c944bfd5840ba3e7fcaba1a195038543e86d6032bbc499a06dd7_arm64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/devicefinder-rhel9@sha256:5dacf80a95c235df6959c6a11458a2241faabf13aa96a62364f5f707fea54aaf_s390x as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/devicefinder-rhel9@sha256:a1c792404cee8722b4cd39c1d119f0321c127c10632aa46c8aaa502351c713af_ppc64le as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/devicefinder-rhel9@sha256:b7471c1f72365b09ed49160d167a5afce3275589929caf80a1f006127193f233_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/mcg-core-rhel9@sha256:4525e5ad6789136739e183e0d335f66c6550143aa854c449b6379da55c313ac5_s390x as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/mcg-core-rhel9@sha256:5f53404f9a27cf4f244d4446f9a23fff1801de8556e3abb6a0ca2eca1143034c_ppc64le as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/mcg-core-rhel9@sha256:96ab00f4732ea7cf07965c0060fdb6f8053abf65f54d03d3c140f3515d2ad406_arm64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/mcg-core-rhel9@sha256:fd48f1efb11dd1242b09dbb5805dfc8043daed18dcbf3ebcde93c42b2a41a2bd_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/mcg-operator-bundle@sha256:7ca393f05ef391b3caebbea25e26c08da5d7835c23baae10f24f96fdcbea225a_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/mcg-rhel9-operator@sha256:100f94a65671c8d68104730e9547ea8848c1f112b48a1461e62c01fc37f7f3c5_s390x as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/mcg-rhel9-operator@sha256:75c14be6187ac292170764aa422c376fecc7250fe5ec4704c60222e6a42bc667_arm64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/mcg-rhel9-operator@sha256:87974d8bbfc5dece632e878c9fc0c7aca4b5bca39aeb09bd14b5dcf31d2f0f95_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/mcg-rhel9-operator@sha256:c5791f8b736487b6ce6d8d23911e910a4a18acff3a2925c2ef58fdddac281b60_ppc64le as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/ocs-client-console-rhel9@sha256:5ebdb12fc37a7933133908c542a85d3b40e9d85d7cb7784b9e0b4dad0b01dada_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/ocs-client-console-rhel9@sha256:91a61737fb3512e817dcaf339875bdffef2ad8229ba7da12e06f323a4e52af36_ppc64le as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/ocs-client-console-rhel9@sha256:a7e8457b050f1f1c9558ac842e9ddb356810c01b2b23766048b6d5a7573d7306_s390x as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/ocs-client-console-rhel9@sha256:d3e04b57ee9c3031c4bd11cafa9242b1d55ec8a78250487d4393b1fa09dcfdd8_arm64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/ocs-client-operator-bundle@sha256:6ef7d250a42285239c62230e098848335f25cbc8a35707d6882388b51b85caca_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/ocs-client-rhel9-operator@sha256:24914917fd2e949e5a9cd4e013660ddd36b19d6434da8c75be6d371175ba53a7_ppc64le as a component of Red Hat Openshift Data Foundation 5.0
- registry.redhat.io/odf5/ocs-client-rhel9-operator@sha256:2efdcf33c4948a144328bbef0c4449697b755857f63a40074850fdc5780d4182_amd64 as a component of Red Hat Openshift Data Foundation 5.0
- +99 more not shown
✅ Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/5.0/html/updating_openshift_data_foundation/updating-ocs-to-odf_rhodf Workaround: In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options. Workaround: Sanitize the user-provided locale name before passing it to Moment.js. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible. Workaround: The issue can be mitigated by reducing the maximum allowed length of the request headers using the --max-http-header-size=size or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. The issue can be mitigated also by seting server.maxHeadersCount to 0. Workaround: Avoid using two parameters within a single path segment when the separator is not, for example, /:a-:b. Alternatively, you can define the regex used for both parameters and ensure they do not overlap to allow backtracking. Workaround: Currently, no mitigation is available for this vulnerability. Workaround: Users may work around this issue by passing an object rather than an array to the `response.writeHead()` function. Workaround: To mitigate this issue, implement strict input validation before passing any property paths to the _.unset and _.omit functions to block attempts to access the prototype chain. Ensure that strings like __proto__, constructor and prototype are blocked, for example. Workaround: To mitigate this issue, disable the $data feature if your application does not require it. If $data must be used, implement strict validation of the input fields that are referenced by the pattern keyword to ensure they contain only expected and safe characters. Workaround: To mitigate this issue, applications using `path-to-regexp` can implement custom regular expressions for parameters beyond the first in a single URL segment. For example, a route like `/:a-:b-:c` can be rewritten as `/:a-:b([^-/]+)-:c([^-/]+)`. Alternatively, limiting the maximum length of incoming URLs can also reduce the risk of exploitation. These changes require application-level configuration and may necessitate a service restart to take effect. Workaround: Applications using the `form-data` library should implement strict input validation and sanitization for all field names and filenames derived from untrusted sources. This prevents the injection of control characters (CR, LF, ") that could lead to header injection or form field overrides. Deployments that exclusively use fixed or trusted field names are not impacted. Workaround: There is no practical mitigation for this vulnerability. The brace-expansion package is typically a transitive dependency pulled in via minimatch and glob, making it difficult to isolate. Users should upgrade to a fixed version of brace-expansion when one becomes available. Workaround: To reduce exposure, restrict the processing of untrusted YAML documents by applications that rely on `js-yaml`. Implement robust input validation and sanitization for all YAML data originating from external or untrusted sources. Consider limiting network access to services that parse YAML content to trusted networks or clients through appropriate firewall configurations. Workaround: To mitigate this vulnerability, do not pass untrusted input to the expand() function. Workaround: If an immediate upgrade to qs 6.16.0 is not feasible, avoid re-serializing attacker-influenced parsed query or body objects with qs.stringify. Where qs.parse is used directly, set allowPrototypes: false unless prototype keys are required. For Express applications, review whether the default query parser configuration is necessary. Wrapping qs.stringify calls in try/catch can limit impact to individual requests. Workaround: Update the compression middleware to version 1.8.2 or later. No supported workaround is currently available if the affected version cannot be updated. Workaround: To mitigate this flaw through configuration: 1. Configure trusted proxy definitions using standard IPv4 notation (such as `10.0.0.0/8`) rather than IPv4-mapped IPv6 notation. 2. If IPv4-mapped IPv6 notation is required, set the subnet prefix length to at least 97 to cover the mapped boundary (for example, specify `::ffff:10.0.0.0/104` instead of `::ffff:10.0.0.0/8`). 3. Alternatively, sanitize or strip incoming `X-Forwarded-For` headers at edge load balancers or boundary reverse proxies before passing traffic to backend applications. Warning: Modifying application configuration files requires restarting the Node.js application service, which will temporarily interrupt service availability and active connections. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Updating the bundled brace-expansion dependency to a version that contains the upstream fix (1.1.21, 2.1.7, 3.0.9, or 5.0.12, depending on the major version in use) resolves the issue.
🔗 References (92)
- selfhttps://access.redhat.com/errata/RHSA-2026:100741
- externalhttps://access.redhat.com/security/cve/CVE-2017-16137
- externalhttps://access.redhat.com/security/cve/CVE-2020-15168
- externalhttps://access.redhat.com/security/cve/CVE-2020-15366
- externalhttps://access.redhat.com/security/cve/CVE-2020-28500
- externalhttps://access.redhat.com/security/cve/CVE-2020-7598
- externalhttps://access.redhat.com/security/cve/CVE-2020-7608
- externalhttps://access.redhat.com/security/cve/CVE-2020-7610
- externalhttps://access.redhat.com/security/cve/CVE-2020-7788
- externalhttps://access.redhat.com/security/cve/CVE-2020-8203
- externalhttps://access.redhat.com/security/cve/CVE-2020-8237
- externalhttps://access.redhat.com/security/cve/CVE-2021-23337
- externalhttps://access.redhat.com/security/cve/CVE-2021-23343
- externalhttps://access.redhat.com/security/cve/CVE-2021-32640
- externalhttps://access.redhat.com/security/cve/CVE-2021-32804
- externalhttps://access.redhat.com/security/cve/CVE-2021-37701
- externalhttps://access.redhat.com/security/cve/CVE-2021-37712
- externalhttps://access.redhat.com/security/cve/CVE-2021-37713
- externalhttps://access.redhat.com/security/cve/CVE-2021-3807
- externalhttps://access.redhat.com/security/cve/CVE-2021-43138
- externalhttps://access.redhat.com/security/cve/CVE-2021-44906
- externalhttps://access.redhat.com/security/cve/CVE-2022-0235
- externalhttps://access.redhat.com/security/cve/CVE-2022-23539
- externalhttps://access.redhat.com/security/cve/CVE-2022-23540
- externalhttps://access.redhat.com/security/cve/CVE-2022-23541
- externalhttps://access.redhat.com/security/cve/CVE-2022-24785
- externalhttps://access.redhat.com/security/cve/CVE-2022-24999
- externalhttps://access.redhat.com/security/cve/CVE-2022-25883
- externalhttps://access.redhat.com/security/cve/CVE-2022-31129
- externalhttps://access.redhat.com/security/cve/CVE-2022-3517
- externalhttps://access.redhat.com/security/cve/CVE-2023-0842
- externalhttps://access.redhat.com/security/cve/CVE-2023-45133
- externalhttps://access.redhat.com/security/cve/CVE-2024-21538
- externalhttps://access.redhat.com/security/cve/CVE-2024-28863
- externalhttps://access.redhat.com/security/cve/CVE-2024-29041
- externalhttps://access.redhat.com/security/cve/CVE-2024-37890
- externalhttps://access.redhat.com/security/cve/CVE-2024-43796
- externalhttps://access.redhat.com/security/cve/CVE-2024-43799
- externalhttps://access.redhat.com/security/cve/CVE-2024-43800
- externalhttps://access.redhat.com/security/cve/CVE-2024-45296
- externalhttps://access.redhat.com/security/cve/CVE-2024-45590
- externalhttps://access.redhat.com/security/cve/CVE-2024-47764
- externalhttps://access.redhat.com/security/cve/CVE-2024-52798
- externalhttps://access.redhat.com/security/cve/CVE-2025-13465
- externalhttps://access.redhat.com/security/cve/CVE-2025-5889
- externalhttps://access.redhat.com/security/cve/CVE-2025-64718
- externalhttps://access.redhat.com/security/cve/CVE-2025-65945
- externalhttps://access.redhat.com/security/cve/CVE-2025-69873
- externalhttps://access.redhat.com/security/cve/CVE-2025-7339
- externalhttps://access.redhat.com/security/cve/CVE-2025-7783
- externalhttps://access.redhat.com/security/cve/CVE-2025-8766
- externalhttps://access.redhat.com/security/cve/CVE-2026-102276
- externalhttps://access.redhat.com/security/cve/CVE-2026-102277
- externalhttps://access.redhat.com/security/cve/CVE-2026-102278
- externalhttps://access.redhat.com/security/cve/CVE-2026-12143
- externalhttps://access.redhat.com/security/cve/CVE-2026-12590
- externalhttps://access.redhat.com/security/cve/CVE-2026-13149
- externalhttps://access.redhat.com/security/cve/CVE-2026-23745
- externalhttps://access.redhat.com/security/cve/CVE-2026-2391
- externalhttps://access.redhat.com/security/cve/CVE-2026-23950
- externalhttps://access.redhat.com/security/cve/CVE-2026-24842
- externalhttps://access.redhat.com/security/cve/CVE-2026-26960
- externalhttps://access.redhat.com/security/cve/CVE-2026-26996
- externalhttps://access.redhat.com/security/cve/CVE-2026-27903
- externalhttps://access.redhat.com/security/cve/CVE-2026-27904
- externalhttps://access.redhat.com/security/cve/CVE-2026-2950
- externalhttps://access.redhat.com/security/cve/CVE-2026-29786
- externalhttps://access.redhat.com/security/cve/CVE-2026-31802
- externalhttps://access.redhat.com/security/cve/CVE-2026-33532
- externalhttps://access.redhat.com/security/cve/CVE-2026-33750
- externalhttps://access.redhat.com/security/cve/CVE-2026-4800
- externalhttps://access.redhat.com/security/cve/CVE-2026-4867
- externalhttps://access.redhat.com/security/cve/CVE-2026-48779
- externalhttps://access.redhat.com/security/cve/CVE-2026-53550
- externalhttps://access.redhat.com/security/cve/CVE-2026-53655
- externalhttps://access.redhat.com/security/cve/CVE-2026-56851
- externalhttps://access.redhat.com/security/cve/CVE-2026-59869
- externalhttps://access.redhat.com/security/cve/CVE-2026-59871
- externalhttps://access.redhat.com/security/cve/CVE-2026-59873
- externalhttps://access.redhat.com/security/cve/CVE-2026-59874
- externalhttps://access.redhat.com/security/cve/CVE-2026-59875
- externalhttps://access.redhat.com/security/cve/CVE-2026-61801
- externalhttps://access.redhat.com/security/cve/CVE-2026-69152
- externalhttps://access.redhat.com/security/cve/CVE-2026-73566
- externalhttps://access.redhat.com/security/cve/CVE-2026-82417
- externalhttps://access.redhat.com/security/cve/CVE-2026-84304
- externalhttps://access.redhat.com/security/cve/CVE-2026-84375
- externalhttps://access.redhat.com/security/cve/CVE-2026-87776
- externalhttps://access.redhat.com/security/cve/CVE-2026-90711
- externalhttps://access.redhat.com/security/updates/classification/
- externalhttps://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_100741.json