Intel

AIKIDO-2026-600231

hackney is vulnerable to Improper Certificate Validation

CVE-2026-115693Published 4 days ago
November 16, 2026

91

CVE Score

Critical

Improper Certificate Validation

Are you affected? Scan for Free

TL;DR

Affected versions of hackney retain a certificate validation callback that trusts bundled public certificate authorities even when an application configures a private CA trust store. An attacker positioned between the client and server who has a publicly trusted certificate for the pinned hostname can bypass the private CA restriction, impersonate the server, and read or modify traffic.

How do I fix this?

Upgrade hackney to 4.9.0 or later. The fix removes the bundled public-root partial_chain callback when a custom CA trust store is configured, unless the caller explicitly supplies a callback. If you cannot upgrade immediately, supply your own partial_chain callback that returns unknown_ca alongside cacerts or cacertfile so certificate validation uses the configured trust store.

Who does this affect?

You are affected if you use a vulnerable version of hackney and pass cacerts or cacertfile in ssl_options to restrict trust to a private CA without supplying your own partial_chain callback. Connections using hackney's default CA trust store are not affected. Exploitation requires an attacker on the network path with a publicly trusted certificate for the pinned hostname.

Package

Versions

1.24.0 - 4.8.7

Fixed in 4.9.0

Background info

hackney is vulnerable to Improper Certificate Validation in versions 1.24.0 - 4.8.7.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea