CVE-2025-30204VulnerabilityPublished 22 Dec 2025Updated 25 Oct 2026

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

Affects Red HatSource GCVE Database

Not known to be exploited : upgrade to 4.19 soon.

Data as of 25 Oct 2026, 22:09 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.19

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

Upgrade Red Hat to 4.19.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=4.18 <4.19 Red Hat Red Hat Openshift Data Foundation Red Hat Openshift Data Foundation 4.18 amd64 registry.redhat.io/odf4/cephcsi-rhel9@sha256:5d4bc3b8907f38bdaeaf9a1c12e0955a81021147b87e7203e94471356065df0a_amd64	Fixed in 4.19

AI-suggested

Red Hat Product Security currently does not recommend any specific mitigation for this vulnerability. Users should ensure all previously released errata relevant to their system are applied before updating. No workaround or temporary fix is provided at this time.

Description

Red Hat OpenShift Data Foundation 4.18 security, enhancement & bug fix update.

Impact

The vulnerability can cause denial of service through excessive resource consumption (CPU and memory) triggered by malicious JWT Authorization headers. This leads to significant performance degradation or application crashes in affected Red Hat OpenShift Data Foundation 4.18 deployments. There is no impact on confidentiality or integrity reported. No known exploits are currently active in the wild.

Summary

This vulnerability affects the golang-jwt library used in Red Hat OpenShift Data Foundation 4.18. It allows an attacker to send a malicious request with a specially crafted Authorization header that triggers excessive memory allocation during JWT header parsing. This asymmetric resource consumption (CWE-405) can cause high CPU and memory usage, potentially crashing the application or severely degrading performance, resulting in denial of service. The issue is tracked under CVE-2025-30204 and has a Red Hat CVSS v3 base score of 7.5 (high severity). Red Hat has not yet released a fix or mitigation and advises applying all previously released errata before updating. The vulnerability is documented in Red Hat advisory RHSA-2025:23916.

CWE-405Asymmetric Resource Consumption (Amplification) (opens in a new tab)
Class weakness
The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."
Architecture and Design
An application must make resources available to a client commensurate with the client's access level.
Architecture and Design
An application must, at all times, keep track of allocated resources and meter their usage appropriately.
System Configuration
Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (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

AI analysisMachine-generated, updated 14 Aug 2026, 22:15 UTC

WeaknessesCWE-405, CWE-362

Technical details

References

Community reviews

Related threats