CVE-2026-107318
validatedZero produced an exploit or a check.GHSA-j425-jw94-m29r ↗EUVD-2026-95261 ↗
description
@fastify/reply-from releases earlier than 12.7.0 may accept an untrusted certificate when forwarding requests to an HTTPS upstream through built-in transports. An attacker positioned to intercept that upstream connection could inspect forwarded sensitive data or provide responses posing as the upstream service.
mitigation
Upgrade @fastify/reply-from to 12.7.0 or later. Until upgrading, explicitly enable upstream certificate validation or use a preconfigured Undici client or global agent that enforces it.
fixed in 12.7.0
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-08 20:32Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-107318
{ "etk_id": "ETK-2026-1048", "cve_id": "CVE-2026-107318", "display_id": "CVE-2026-107318", "ghsa_id": "GHSA-j425-jw94-m29r", "euvd_id": "EUVD-2026-95261", "status": "published", "anchor_state": "anchored", "title": "TLS certificate validation bypass in @fastify/reply-from", "summary": "@fastify/reply-from releases earlier than 12.7.0 may accept an untrusted certificate when forwarding requests to an HTTPS upstream through built-in transports. An attacker positioned to intercept that upstream connection could inspect forwarded sensitive data or provide responses posing as the upstream service.", "mitigation": "Upgrade @fastify/reply-from to 12.7.0 or later. Until upgrading, explicitly enable upstream certificate validation or use a preconfigured Undici client or global agent that enforces it.", "vendor": "@fastify/reply-from", "product": "@fastify/reply-from", "affected": [ { "affected_notes": [], "affected_ranges": [ "< 12.7.0" ], "ecosystem": "npm", "fixed_versions": [ "12.7.0" ], "package_name": "@fastify/reply-from", "purl": "pkg:npm/@fastify/reply-from" } ], "cwes": [ 295 ], "cvss_score": 7.4, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N", "epss_score": 0.0015, "epss_percentile": 0.0345, "epss_asof": "2026-10-21", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 7.259325516666666, "t0_at": "2026-10-08T20:32:03.483000+00:00", "signals": { "check": { "at": "2026-10-09T05:54:54.061121+00:00", "days": 0.39086317269675924, "is_lower_bound": false, "measured_at": "2026-10-08T20:32:03.483000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-08T20:32:03.483000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-08T20:32:03.483000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-107318" } } }
published 2026-10-09 05:47Z
last change 2026-10-21 22:02Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.