CVE-2026-115693
Custom cacerts or cacertfile do not restrict trust to the pinned CA in hackney
- State
- Published
- Severity
- 9.1 Critical
- Published
- Oct 26, 2026
- Updated
- Oct 26, 2026
- Reserved
- Oct 25, 2026
Description
Improper Certificate Validation vulnerability in hackney_ssl in benoitc hackney allows an on-path attacker to impersonate a server pinned to a private certificate authority via a certificate chain that ends in a publicly trusted root. hackney adds {partial_chain, fun hackney_ssl:partial_chain/1} to every verify_peer configuration. The callback returns any certificate in the peer chain whose public key matches a root in the bundled certifi store as the trust anchor, and OTP honours that callback over the configured cacerts. hackney_ssl:merge_ssl_opts/3 kept the callback when the caller replaced the trust store with cacerts or cacertfile in ssl_options, so a connection pinned to a private CA still accepted any chain that carried a publicly trusted root.
The hostname check still applies, so the attacker needs a publicly trusted certificate for the pinned hostname.
This issue affects hackney: from 1.24.0 before 4.9.0.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 9.1 Critical | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N | EEF |
Weaknesses
- CWE-295 Improper Certificate Validation
Affected Products
| Product | Versions |
|---|---|
hackneybenoitc |
|
hackneybenoitc |
|
References
- Drop the certifi partial_chain when the caller pins cacerts or cacertfile (benoitc/hackney#978)related
- EEF CNA record for CVE-2026-115693related
- OSV record EEF-CVE-2026-115693related
- hackney 4.9.0 release notesvendor-advisoryrelated
- Introducing commit d8a9afc in benoitc/hackneyrelated
- Fix commit 915eb57 in benoitc/hackneypatch
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.