CVE-2025-66418: Icloudpd · urllib3 allows an unbounded number of links in the decompression chain
Affects icloudpdSource GCVE Database
Not known to be exploited · CVSS 8.9 High : upgrade to 1.33.0 soon.
Data as of 9 Nov 2026, 19:47 UTC
- Patch
- Available – fixed in 1.33.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 13 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 9 Nov 2026.
What to do
Upgrade icloudpd to 1.33.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewicloudpdpkg:brew/icloudpdOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade urllib3 to version 2.6.0 or later, where the decompression chain length is limited to 5. If upgrading is not immediately feasible, disable automatic content decoding by setting preload_content=False and manually verify that the 'content-encoding' header contains a safe number of encodings before reading the response content.
Description
urllib3 versions 2.5.0 and earlier allow an unbounded number of chained HTTP content encodings, which can be exploited by a malicious server to cause excessive CPU and memory usage during decompression. This affects applications using urllib3 for HTTP requests to untrusted sources unless content decoding is disabled. The issue is fixed in urllib3 version 2.6.0 by limiting the decompression chain to 5 links. For users unable to upgrade immediately, disabling automatic content decoding and manually checking the content-encoding header is recommended.