CVE-2026-18248
Last modified
CVE-2026-18248 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. @fastify/aws-lambda version 6.4.0 decorates each Fastify request with request.awsLambda.event and request.awsLambda.context, values that applications are documented to use for authorization decisions such as reading API Gateway authorizer claims. In the default configuration, the getter that populates this decoration reads the client-controlled x-apigateway-event and x-apigateway-context HTTP headers before falling back to the trusted internal request token, and those reserved headers are not stripped from the incoming event.
Description
@fastify/aws-lambda version 6.4.0 decorates each Fastify request with request.awsLambda.event and request.awsLambda.context, values that applications are documented to use for authorization decisions such as reading API Gateway authorizer claims. In the default configuration, the getter that populates this decoration reads the client-controlled x-apigateway-event and x-apigateway-context HTTP headers before falling back to the trusted internal request token, and those reserved headers are not stripped from the incoming event. An unauthenticated attacker who can set a single HTTP header can therefore forge the entire Lambda proxy event, including the authorizer context, and override the genuine one. This results in a full authentication and authorization bypass and privilege escalation for any application that trusts request.awsLambda.event for identity or access control. Only version 6.4.0 is affected. Patches: upgrade to @fastify/aws-lambda 6.4.1, which resolves the decoration only through the internal per-invocation token and strips the reserved headers before the request is processed.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| @fastify/aws-lambda | @fastify/aws-lambda | >= 6.4.0, < 6.4.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-18248?
How severe is CVE-2026-18248?
How do I fix CVE-2026-18248?
How Strix Helps
- Same Subject, Wrong User: A Cross-Issuer Account Takeover in n8nStrix found an identity-binding bug in n8n's token-exchange flow enabling account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-18230The WP Directory Kit WordPress plugin before 1.5.6 does not …
- CVE-2026-18236A vulnerability in the Agent Development Kit (ADK) allows fo…9.3
- CVE-2026-1824The Infomaniak Connect for OpenID plugin for WordPress is vu…6.4
- CVE-2026-18243Certain HP DesignJet products may be potentially vulnerable …6.9
- CVE-2026-18245Improper control of code generation in Amazon @aws-amplify/c…8.8
- CVE-2026-18247A Cross Site Scripting (XSS) vulnerability in the Web Portal…5.3
- CVE-2026-1825The Show YouTube video plugin for WordPress is vulnerable to…6.4
- CVE-2026-18255A flaw was found in Quay. A user configured in GLOBAL_READON…7.2
- CVE-2026-18257Improper validity period check for root issuer certificate i…5.6
- CVE-2026-18258Authorization bypass in the Line, LineTranscription, Virtual…8.8
- CVE-2026-1826The OpenPOS Lite – Point of Sale for WooCommerce plugin for …6.4
- CVE-2026-18266Dify AI Workflow oauth_redirect_url Open Redirect Vulnerabil…5.4
Are you affected by CVE-2026-18248?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
