Fastify Async Validator Request Body Manipulation

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 property's value before the handler runs, so the handler receives a different object than the one that satisfied the schema. An authenticated low-privilege caller can use this to make nested data replace the validated body and trigger an operation the route schema did not authorize, leading to unauthorized state changes and data disclosure. Users should upgrade to fastify 5.12.2 or later.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-84504 is an input validation vulnerability (CWE-20) affecting Fastify versions before 5.12.2 where the framework incorrectly interprets successful async validator responses. When a request contains a root-level property named 'value' that passes schema validation, Fastify mistakenly treats this property as the result protocol from the validator and replaces the entire request body with its contents before passing it to the route handler. This creates a critical disconnect between what the schema validated and what the application logic receives. Any organization running vulnerable Fastify versions is affected, particularly those handling authenticated requests where low-privilege users could exploit this for privilege escalation, data manipulation, or injection attacks by crafting specially-formed payloads that pass validation but transform into malicious content.

Casky's 323 mapped security skills leverage Claude's extended reasoning to detect this vulnerability pattern across TA0001 (Initial Access) and TA0043 (Reconnaissance) attack phases. Practitioners using Casky would identify suspicious patterns including: anomalous schema validation passing followed by unexpected request body mutations, cases where validated input structure diverges from handler-received payloads, and authentication bypass attempts using nested 'value' properties to escalate privileges. By correlating validator compiler logs with actual handler inputs and monitoring for request transformation anomalies, Claude-powered analysis reveals the root cause—malicious actors exploiting the validator response misinterpretation to inject nested data into unexpected locations, effectively bypassing input sanitization controls that rely on schema validation alone.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-84504.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-84504

Casky has 323 skills that investigate the attack patterns behind CVE-2026-84504. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn