Improper Handling of Highly Compressed Data (Data Amplification) The advisory has been revoked - it doesn't affect any version of package openshift4/ose-csi-driver-nfs-rhel9 (opens in a new tab)
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL7-OPENSHIFT4OSECSIDRIVERNFSRHEL9-14920663
- published13 Jan 2026
- disclosed5 Dec 2025
Introduced: 5 Dec 2025
CVE-2025-66471 (opens in a new tab)Amendment
The Red Hat security team deemed this advisory irrelevant for RHEL:7.
NVD Description
Note: Versions mentioned in the description apply only to the upstream openshift4/ose-csi-driver-nfs-rhel9 package and not the openshift4/ose-csi-driver-nfs-rhel9 package as distributed by RHEL.
urllib3 is a user-friendly HTTP client library for Python. Starting in version 1.0 and prior to 2.6.0, the Streaming API improperly handles highly compressed data. urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once. When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation. The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data.