CVE-2026-18248

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

@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.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 3, 2026

Last Modified

September 4, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
No fix on record yet. Sources: github.
githubMentions a patch (unverified)

@fastify/aws-lambda vulnerable to Lambda event spoofing via client-controlled x-apigateway-event header · Advisory · fastify/aws-lambda-fastify · GitHub

https://github.com/fastify/aws-lambda-fastify/security/advisories/GHSA-m93c-jj3f-68ph
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 116 total refreshes for this CVE.

  1. 2026-10-10 19:59 UTCEPSS rescore
  2. 2026-10-09 20:06 UTCEPSS rescore
  3. 2026-10-08 17:11 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 23:46 UTCEG score recompute
  6. 2026-10-06 15:17 UTCEPSS rescore
  7. 2026-10-05 19:48 UTCEG score recompute
  8. 2026-10-05 17:42 UTCEPSS rescore
  9. 2026-10-04 23:45 UTCEG score recompute
  10. 2026-10-04 23:21 UTCEPSS rescore
  11. 2026-10-04 06:19 UTCEG score recompute
  12. 2026-10-03 14:25 UTCEPSS rescore
  13. 2026-10-02 16:46 UTCEG score recompute
  14. 2026-10-02 10:18 UTCEG score recompute
  15. 2026-10-01 19:49 UTCEPSS rescore
  16. 2026-10-01 02:33 UTCEG score recompute
  17. 2026-09-30 15:02 UTCEPSS rescore
  18. 2026-09-29 15:20 UTCEPSS rescore
  19. 2026-09-29 06:39 UTCEG score recompute
  20. 2026-09-28 13:51 UTCEPSS rescore
  21. 2026-09-27 18:15 UTCEG score recompute
  22. 2026-09-27 13:47 UTCEPSS rescore
  23. 2026-09-26 15:58 UTCEPSS rescore
  24. 2026-09-25 04:46 UTCEG score recompute
  25. 2026-09-23 16:16 UTCEG score recompute
Show 75 more
  1. 2026-09-22 21:26 UTCEG score recompute
  2. 2026-09-22 05:28 UTCEG score recompute
  3. 2026-09-20 20:56 UTCEG score recompute
  4. 2026-09-19 17:50 UTCEG score recompute
  5. 2026-09-18 23:59 UTCEG score recompute
  6. 2026-09-18 19:27 UTCEPSS rescore
  7. 2026-09-18 01:11 UTCEG score recompute
  8. 2026-09-17 01:14 UTCEG score recompute
  9. 2026-09-16 14:07 UTCEPSS rescore
  10. 2026-09-16 05:18 UTCEG score recompute
  11. 2026-09-16 05:14 UTCEPSS rescore
  12. 2026-09-15 07:01 UTCEG score recompute
  13. 2026-09-13 19:36 UTCEG score recompute
  14. 2026-09-13 16:46 UTCEPSS rescore
  15. 2026-09-12 17:35 UTCEG score recompute
  16. 2026-09-12 15:00 UTCEPSS rescore
  17. 2026-09-11 14:53 UTCEG score recompute
  18. 2026-09-11 14:52 UTCEPSS rescore
  19. 2026-09-11 09:36 UTCEPSS rescore
  20. 2026-09-10 12:51 UTCEG score recompute
  21. 2026-09-10 09:34 UTCEPSS rescore
  22. 2026-09-09 06:46 UTCEG score recompute
  23. 2026-09-08 22:00 UTCEPSS rescore
  24. 2026-09-07 18:54 UTCEG score recompute
  25. 2026-09-07 16:01 UTCEPSS rescore
  26. 2026-09-06 16:33 UTCEG score recompute
  27. 2026-09-06 13:47 UTCEPSS rescore
  28. 2026-09-05 18:39 UTCEG score recompute
  29. 2026-09-05 04:22 UTCEG score recompute
  30. 2026-09-04 10:16 UTCEG score recompute
  31. 2026-09-04 05:06 UTCEPSS rescore
  32. 2026-09-03 08:48 UTCEG score recompute
  33. 2026-09-02 14:11 UTCEPSS rescore
  34. 2026-09-01 22:16 UTCEG score recompute
  35. 2026-09-01 13:53 UTCEPSS rescore
  36. 2026-09-01 07:19 UTCEG score recompute
  37. 2026-09-01 04:39 UTCEPSS rescore
  38. 2026-08-30 19:30 UTCEG score recompute
  39. 2026-08-30 19:17 UTCEPSS rescore
  40. 2026-08-30 02:17 UTCEG score recompute
  41. 2026-08-30 01:22 UTCEPSS rescore
  42. 2026-08-29 22:01 UTCEG score recompute
  43. 2026-08-28 21:41 UTCEPSS rescore
  44. 2026-08-27 20:02 UTCEG score recompute
  45. 2026-08-27 14:25 UTCEPSS rescore
  46. 2026-08-26 19:12 UTCEG score recompute
  47. 2026-08-26 14:46 UTCEPSS rescore
  48. 2026-08-25 15:13 UTCEG score recompute
  49. 2026-08-25 13:48 UTCEPSS rescore
  50. 2026-08-24 17:44 UTCEG score recompute
  51. 2026-08-24 12:56 UTCEG score recompute
  52. 2026-08-22 00:36 UTCEG score recompute
  53. 2026-08-21 23:49 UTCEPSS rescore
  54. 2026-08-21 03:11 UTCEG score recompute
  55. 2026-08-20 22:55 UTCEPSS rescore
  56. 2026-08-19 20:36 UTCEG score recompute
  57. 2026-08-19 17:03 UTCEPSS rescore
  58. 2026-08-18 18:21 UTCEG score recompute
  59. 2026-08-18 13:48 UTCEPSS rescore
  60. 2026-08-17 14:37 UTCEG score recompute
  61. 2026-08-17 13:47 UTCEPSS rescore
  62. 2026-08-16 17:10 UTCEG score recompute
  63. 2026-08-16 14:56 UTCEPSS rescore
  64. 2026-08-16 04:19 UTCEG score recompute
  65. 2026-08-16 02:14 UTCEPSS rescore
  66. 2026-08-15 02:21 UTCEG score recompute
  67. 2026-08-15 01:30 UTCEPSS rescore
  68. 2026-08-14 00:41 UTCEG score recompute
  69. 2026-08-13 22:00 UTCEPSS rescore
  70. 2026-08-12 14:27 UTCEG score recompute
  71. 2026-08-12 13:50 UTCEPSS rescore
  72. 2026-08-11 17:00 UTCEG score recompute
  73. 2026-08-11 13:42 UTCEPSS rescore
  74. 2026-08-11 04:10 UTCEG score recompute
  75. 2026-08-11 00:00 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18248?
CVE-2026-18248 is a critical vulnerability published on August 3, 2026. @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…
When was CVE-2026-18248 disclosed?
CVE-2026-18248 was first published on August 3, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18248 actively exploited?
CVE-2026-18248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18248?
CVE-2026-18248 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18248?
No fix for CVE-2026-18248 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18248

Explore →

Is Your Infrastructure Affected by CVE-2026-18248?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs