Intel

AIKIDO-2026-399341

@fastify/reply-from is vulnerable to Improper Certificate Validation

CVE-2026-107318Published Nov 3, 2026
November 3, 2026

74

CVE Score

High

Improper Certificate Validation

Are you affected? Scan for Free

TL;DR

Before the fix, getUndiciOptions, getHttpOpts and getHttp2Opts in @fastify/reply-from forced rejectUnauthorized to false on all three built-in HTTPS transports whenever the application did not set it, so proxying to an https:// upstream skipped TLS certificate verification by default, including with partial option objects like tls: {}. An on-path network attacker could impersonate the upstream, read forwarded credentials and request bodies, and return forged responses the application trusts. The fix removes the forced value so Node.js and undici verify the upstream certificate by default; self-signed or private-CA upstreams now need an explicit ca or rejectUnauthorized: false.

How do I fix this?

Upgrade the @fastify/reply-from package to 12.7.0 or later.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and proxy requests to an https:// upstream without explicitly setting rejectUnauthorized on the undici, http or http2 transport options.

Versions

7.0.0 - 12.6.5

Fixed in 12.7.0

Background info

@fastify/reply-from is vulnerable to Improper Certificate Validation in versions 7.0.0 - 12.6.5.

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