CVE-2025-9086: Out of bounds read for cookie path
1. A cookie is set using the secure keyword for
Other sources
App Store. A permissions issue was addressed with additional restrictions.
— Apple
AppleJPEG. The issue was addressed with improved bounds checks.
— Apple
AppleMobileFileIntegrity. A downgrade issue affecting Intel-based Mac computers was addressed with additional code-signing restrictions.
— Apple
AppleMobileFileIntegrity. A permissions issue was addressed with additional restrictions.
— Apple
AppleMobileFileIntegrity. The issue was addressed by adding additional logic.
— Apple
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 14.8.3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.7.3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 26.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 18.7.3 - Compensating control
Ensure a cookie marked with the `secure` keyword is ignored when the client is redirected to or otherwise made to speak using clear-text HTTP (`http://target`), rather than allowing an insecure host to override the contents of the secure cookie.
Event History
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2025-43539
- CVE-2025-43519
- CVE-2025-46289
- CVE-2025-43482
- CVE-2025-43517
- CVE-2025-46287
- CVE-2024-7264
- CVE-2025-9086
- CVE-2025-43518
- CVE-2025-43532
- CVE-2025-43512
- CVE-2025-46285
- CVE-2025-5918
- CVE-2025-43513
- CVE-2025-46276
- CVE-2025-43509
- CVE-2025-43538
- CVE-2025-43463
- CVE-2025-43416
- CVE-2025-43516
- CVE-2025-43530
- CVE-2025-43320
- CVE-2025-43522
- CVE-2025-43521
- CVE-2025-43523
- CVE-2025-43542
- CVE-2025-43527
- CVE-2025-46279
- CVE-2025-43533
- CVE-2025-46300
- CVE-2025-46301
- CVE-2025-46302
- CVE-2025-46303
- CVE-2025-46304
- CVE-2025-46305
- CVE-2025-43531
- CVE-2025-14174
- CVE-2025-43529
- CVE-2025-46299
- CVE-2025-46298
- CVE-2025-46288
- CVE-2025-43428
- CVE-2025-46290
- CVE-2025-43541
- CVE-2025-43535
- CVE-2025-43501
- CVE-2025-43511
- CVE-2025-46277
- CVE-2025-46311
- CVE-2025-46292
- CVE-2025-43536
- CVE-2025-46286
- CVE-2025-43537
- CVE-2025-43534
- CVE-2025-43475
- CVE-2025-46297
- CVE-2025-46283
- CVE-2025-46281
- CVE-2025-43417
- CVE-2025-46278
- CVE-2025-43524
- CVE-2025-46291
- CVE-2025-43410
- CVE-2025-43526
- CVE-2024-8906
- CVE-2025-43514
- CVE-2025-46282
Frequently Asked Questions
What is the severity of CVE-2025-9086?
CVE-2025-9086 is considered a high-severity vulnerability due to risks associated with cookie security in mixed content environments.
How do I fix CVE-2025-9086?
To fix CVE-2025-9086, ensure that you only use secure cookies with the `secure` attribute and avoid transmitting sensitive cookies over HTTP.
What is the impact of CVE-2025-9086?
The impact of CVE-2025-9086 includes potential exposure of sensitive data and session hijacking through man-in-the-middle attacks.
Which versions of curl are affected by CVE-2025-9086?
CVE-2025-9086 affects various versions of curl where secure cookies can be mishandled during HTTP redirects.
How can I mitigate risks associated with CVE-2025-9086?
Mitigation strategies for CVE-2025-9086 include enforcing HTTPS across all communications and ensuring secure cookie handling.