CVE-2026-115693

Custom cacerts or cacertfile do not restrict trust to the pinned CA in hackney

CRITICAL
9.1
CVSS Score
Published: October 26, 2026 at 01:49 PM UTC
Updated: October 26, 2026 at 04:59 PM UTC
1 product affected across 1 vendorHackney

Using hackney by benoitc?

Get instant alerts when new vulnerabilities affect hackney - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL9.1

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.24.0d8a9afcf5c3849904274e2eba1df56c63d1a1a0c

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

9.1CRITICALEEF
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-295

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card