CVE-2026-18248
CRITICALDescription
@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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-345 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-38831 | High | 7.8 | 98% | KEV + Ransom | Fix |
| CVE-2016-4553 | High | 8.6 | 80% | - | Fix |
| CVE-2016-4554 | High | 8.6 | 39% | - | Fix |
| CVE-2023-35719 | Medium | 6.8 | 26% | - | - |
| CVE-2022-26871 | Critical | 9.8 | 20% | KEV | - |
| CVE-2014-4936 | High | 9.3 | 17% | - | - |
Common questions
How do I fix CVE-2026-18248?
No published fix for CVE-2026-18248 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-18248?
CVE-2026-18248 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-18248
Markdown
[](https://tridentstack.com/cve/CVE-2026-18248)HTML
<a href="https://tridentstack.com/cve/CVE-2026-18248"><img src="https://tridentstack.com/cve/badge/CVE-2026-18248.svg" alt="CVE-2026-18248"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-03.