CVE-2026-6322VulnerabilityPublished 19 Aug 2026Updated 29 Oct 2026

Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.21.11 security, enhancement & bug fix update

Affects Red HatSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 00:02 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected Red Hat Red Hat Openshift Data Foundation Red Hat Openshift Data Foundation 4.21 amd64 registry.redhat.io/odf4/cephcsi-rhel9@sha256:83237116629c7b841876eeb0ee44a1b5d2aeb367e4f45378cf826ebcdb252fc8_amd64	Fixed in–

Description

Red Hat OpenShift Data Foundation 4.21.11 security, enhancement & bug fix update FIXED BUGS: ========== DFBUGS-9563: [Backport to odf-4.21.10] Race condition may allow multiple CephCluster reconciles in parallel DFBUGS-8999: [odf-4.21] - [GSS] Red Hat Virtualization VMs in Paused State - "VMI was paused, low-level IO error detected" w/rbd Volumes Impacted and Clients Blocklisted DFBUGS-8997: [4.21] CLONE - The console pod in openshift console is continuously restarting DFBUGS-8957: RHODF 4.21.11 release DFBUGS-8200: [Backport to odf-4.21.z] - [GSS] Red Hat Virtualization VMs in Paused State - "VMI was paused, low-level IO error detected" w/rbd Volumes Impacted and Clients Blocklisted DFBUGS-7048: Hide data replication separation option from UI in 4.21 as its not supported DFBUGS-7003: [Backport to odf-4.21.z] [GSS][Disconnected env] ODF is upgraded itself from ODF v4.20.2 to ODF v4.20.7 without Manual Approval when upgrdaing OCP v4.20.5 to OCP v4.20.16 DFBUGS-6995: [Backport to odf-4.21.z] [GSS][ODF] Noobaa DB_CLEANER not honoring set value DFBUGS-6938: [4.21.z] Integrate ibm-storage-odf-operator 1.9.0 DFBUGS-6813: release-4.21 - ODF must-gather missing CR storageclusterpeer.yaml DFBUGS-6510: CLONE 4.21 - Object Browser sends unnecessary getObject API calls DFBUGS-6471: CLONE - In storage cluster UI page , tick mark background colour changed from green to black in 4.22 DFBUGS-5965: [OLS]: RAG content image is using ODF 4.20 documentation when deployed on OCP/ODF 4.21 DFBUGS-4988: ocs-metrics-exporter does not provide metrics during cache refresh

CWE-140Improper Neutralization of Delimiters (opens in a new tab)
Base weakness
The product does not neutralize or incorrectly neutralizes delimiters.
Implementation · Input Validation
Developers should anticipate that delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Output Encoding
While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.2.2 (opens in a new tab)
Attack patterns
Command Delimiters (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-131Incorrect Calculation of Buffer Size (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product does not correctly calculate the size to be used when allocating a buffer.
Implementation
When allocating a buffer for the purpose of transforming, converting, or encoding an input, allocate enough memory to handle the largest possible encoding. For example, in a routine that converts "&" characters to "&" for HTML entity encoding, the output buffer needs to be at least 5 times as large as the input…
Implementation
Understand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how the language handles…
Implementation · Input Validation
Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
Attack patterns
Overflow Buffers (opens in a new tab)
Buffer Overflow via Parameter Expansion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

WeaknessesCWE-140, CWE-131

Technical details

References

Community reviews

Related threats