1085 matches found
PT-2026-85467
Name of the Vulnerable Software and Affected Versions fastify versions prior to 5.12.2 Description Fastify incorrectly determines whether to compile a request schema based on JavaScript truthiness. According to JSON Schema Draft 7, a boolean false is a valid schema that rejects all instances...
PT-2026-85472
Name of the Vulnerable Software and Affected Versions fastify versions prior to 5.12.2 Description An issue exists in how HTTP header names are handled during the compilation of a route's header schema. The software attempts to implement the case-insensitive nature of HTTP headers by lowercasing...
PT-2026-85451
Name of the Vulnerable Software and Affected Versions fastify versions prior to 5.12.2 Description An issue exists where the object resolved by a successful Ajv async validator is treated as the value result protocol used by custom validator compilers. If a request that passes its route schema...
CVE-2026-84469: Improper Input Validation
fastify versions before 5.12.2 decide whether to compile a request schema based on JavaScript truthiness, but JSON Schema Draft 7 defines the boolean false as a valid schema that rejects every instance. When an application assigns false to a route's body, querystring, params, or headers schema to...
PT-2026-85449
Name of the Vulnerable Software and Affected Versions fastify versions 4.0.0 through 5.12.1 Description An unauthenticated attacker can bypass authentication hooks and break prefix encapsulation by sending a malformed URL. The internal not-found router for encapsulated handlers dispatches malform...
CVE-2026-84428: Improper Handling of Case Sensitivity
fastify versions before 5.12.2 implement the case-insensitive nature of HTTP header names by lowercasing names in a route's header schema before compiling it, but the transformation is incomplete: it lowercases the properties keys and the root-level required array, and does not lowercase the...
PT-2026-85452
Name of the Vulnerable Software and Affected Versions @fastify/middie versions 9.1.0 through 9.3.3 Description A mismatch occurs because the middleware evaluates the raw request target to determine if path-scoped middleware should run, whereas the Fastify router resolves an absolute-form request...
CVE-2026-84504: Improper Input Validation
fastify versions before 5.12.2 treat the object resolved by a successful Ajv async validator as the value result protocol used by custom validator compilers. If a request that passes its route schema contains a property named value at the root, fastify replaces the entire request body with that...
CVE-2026-76169: Authentication Bypass Using an Alternate Path or Channel
fastify versions = 4.0.0 and before 5.12.2 can route a malformed URL sent under one plugin prefix to the custom not-found handler of a different sibling plugin, and invoke it without the preHandler hook declared for that handler. The internal not-found router for encapsulated handlers dispatches...
CVE-2026-85184: Interpretation Conflict
@fastify/middie versions = 9.1.0 and before 9.3.4 decide whether to run path-scoped middleware by matching against the raw request target, while the Fastify router resolves an absolute-form request target to its path before dispatching. Because the two layers evaluate different strings, a request...
CLSA-2026-1788457323 TuxCare security update for fastify (2 CVEs)
TuxCare rebuilt fastify to address 2 CVEs. Fixed in 5.11.3-tuxcare.1...
CVE-2026-85124
@fastify/http-proxy versions before 11.6.2 do not validate proxied HTTP request paths for backslash based dot-segments before forwarding them to the configured upstream. The plain HTTP request handler skips the destination validation that the WebSocket path performs, and the underlying reply-from...
Directory Traversal
Overview @fastify/http-proxy is a proxy http requests, for Fastify Affected versions of this package are vulnerable to Directory Traversal through the HTTP request path handling in index.js, including fastifyHttpProxy and reply.fromParameters. An attacker can bypass rewritePrefix path restriction...
@cedarjs/api-server (>=1.0.0-canary.12281, <=9.0.0-canary.1784), @cedarjs/api-server-watch (>=5.0.7-next.219, <=7.0.0-canary.3116) +41 more potentially affected by CVE-2026-85124 via @fastify/http-proxy (>=11.1.2, <=11.6.1)
@fastify/http-proxy NPM version =11.1.2, =1.0.0-canary.12281, =5.0.7-next.219, =1.0.0-canary.12281, =5.0.4-next.167, =1.0.0-canary.12281, =1.0.0-canary.12281, =4.0.0-canary.13864, =4.0.0-canary.13864, =1.0.0-canary.12281, =3.0.0-alpha-1, =0.0.4, =0.3.0, =0.1.0, =0.4.22 and more Source cves:...
CVE-2026-85124 @fastify/http-proxy vulnerable to prefix escape via backslash dot-segments
@fastify/http-proxy versions before 11.6.2 do not validate proxied HTTP request paths for backslash based dot-segments before forwarding them to the configured upstream. The plain HTTP request handler skips the destination validation that the WebSocket path performs, and the underlying reply-from...
CVE-2026-85124
@fastify/http-proxy versions before 11.6.2 are vulnerable to a path traversal (CWE-22) caused by insufficient validation of backslash-based dot-segments in proxied HTTP request paths. The plain HTTP handler skips the destination validation performed on the WebSocket path, and the underlying reply...
EUVD-2026-70381
@fastify/http-proxy versions before 11.6.2 do not validate proxied HTTP request paths for backslash based dot-segments before forwarding them to the configured upstream. The plain HTTP request handler skips the destination validation that the WebSocket path performs, and the underlying reply-from...
CVE-2026-85124 @fastify/http-proxy vulnerable to prefix escape via backslash dot-segments
@fastify/http-proxy versions before 11.6.2 do not validate proxied HTTP request paths for backslash based dot-segments before forwarding them to the configured upstream. The plain HTTP request handler skips the destination validation that the WebSocket path performs, and the underlying reply-from...
CVE-2026-85124 @fastify/http-proxy vulnerable to prefix escape via backslash dot-segments
@fastify/http-proxy versions before 11.6.2 do not validate proxied HTTP request paths for backslash based dot-segments before forwarding them to the configured upstream. The plain HTTP request handler skips the destination validation that the WebSocket path performs, and the underlying reply-from...