CVE-2024-38368: CocoaPods · Resource Exposure
Affects CocoaPodsSource CVE Database V5
Not known to be exploited · 14% EPSS · CVSS 9.3 Critical.
Data as of 4 Nov 2026, 00:28 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 9.3 |
|---|
- EPSS
- 14.8% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2024-07-30.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2024
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 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CocoaPodsCocoaPods | Affected
| Fixed in– |
AI-suggested
This vulnerability has been patched server-side as of September 2023 in commit 71be5440906b6bdfbc0bcc7f8a9fec33367ea0f4. Users and administrators do not need to take additional action as the fix is managed by the CocoaPods server. Verify that you are using the updated CocoaPods services and monitor official vendor advisories for confirmation.
Description
trunk.cocoapods.org is the authentication server for the CoacoaPods dependency manager. A vulnerability affected older pods which migrated from the pre-2014 pull request workflow to trunk. If the pods had never been claimed then it was still possible to do so. It was also possible to have all owners removed from a pod, and that made the pod available for the same claiming system. This was patched server-side in commit 71be5440906b6bdfbc0bcc7f8a9fec33367ea0f4 in September 2023.
References
- github.com/CocoaPods/CocoaPods/security/advisories/GHSA-j483-qm5c-7hqx (opens in a new tab)
- github.com/CocoaPods/trunk.cocoapods.org/commit/71be5440906b6bdfbc0bcc7f8a9fec33367ea0f4 (opens in a new tab)
- blog.cocoapods.org/Claim-Your-Pods (opens in a new tab)
- blog.cocoapods.org/CocoaPods-Trunk-RCEs-2023 (opens in a new tab)
- evasec.webflow.io/blog/eva-discovered-supply-chain-vulnerabities-in-cocoapods (opens in a new tab)