PULSE
LIVE23signals / 24h
FEED
ransomsafepay reclama a pradotuylaw.com · US · Professional Servicesransomsafepay reclama a naskdoorinc.com · US · Manufacturingransomsafepay reclama a new-point.it · IT · Technologyransomsafepay reclama a simonrack.com · ES · Manufacturingransomsafepay reclama a hanan-hov.co.il · IL · Otherransomanubis reclama a BLACKBURN'S · US · Healthcareransomanubis reclama a Cameron Regional Medical Center · US · Healthcareransomsafepay reclama a azn.co.jp · JP · Retail & E-Commerceransomsafepay reclama a southshorerecycling.com · US · Manufacturingransomsafepay reclama a cpu-ag.com · DE · Manufacturingransomsafepay reclama a multiaqua.com · US · Agriculture and Food Productionransomanubis reclama a Winn-Dixie · US · Retail & E-Commerceransomanubis reclama a BLACKBURN'S Physicians Pharmacy, Inc. · US · Healthcareransomqilin reclama a Service Electric · US · Energy & Utilitiesransomsafepay reclama a pradotuylaw.com · US · Professional Servicesransomsafepay reclama a naskdoorinc.com · US · Manufacturingransomsafepay reclama a new-point.it · IT · Technologyransomsafepay reclama a simonrack.com · ES · Manufacturingransomsafepay reclama a hanan-hov.co.il · IL · Otherransomanubis reclama a BLACKBURN'S · US · Healthcareransomanubis reclama a Cameron Regional Medical Center · US · Healthcareransomsafepay reclama a azn.co.jp · JP · Retail & E-Commerceransomsafepay reclama a southshorerecycling.com · US · Manufacturingransomsafepay reclama a cpu-ag.com · DE · Manufacturingransomsafepay reclama a multiaqua.com · US · Agriculture and Food Productionransomanubis reclama a Winn-Dixie · US · Retail & E-Commerceransomanubis reclama a BLACKBURN'S Physicians Pharmacy, Inc. · US · Healthcareransomqilin reclama a Service Electric · US · Energy & Utilities
← All CVEs
CVE WatchAug 3, 2026

CVE-2026-18248

@fastify/aws-lambda version 6.4.0 decorates each Fastify request with request.awsLambda.event and request.awsLambda.context, values that app

CVSS

9.1

Critical

EPSS

KEV

Exploit Today

0-100

Published: Aug 3, 2026 · Last modified: Aug 3, 2026 · CWE-345

EPSS · 30d

Not enough EPSS history yet.

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

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-68945
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.2, HttpTransferCache comma-joins repeated request parameters, allowing semantically distinct HttpClient requests to use the same transfer-cache key and reuse a wrong backend response. This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.2.2h
CVE-2026-59641
0In Bouncy Castle for Java before 1.85, S/MIME validator trusts signer-asserted signingTime for path validation. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bcmail-fips and bcjmail-fips 1.0.7 (1.0.X series), 2.0.7 (2.0.X series) and 2.1.7 (2.1.X series).5h
CVE-2026-673076.3 MED
6.6%
2Wazuh 5.0.0-beta1 (fixed in 5.0.0-beta3) does not validate or override the cluster_name and cluster_node fields in inventory-sync Start FlatBuffer messages, while validating only the agentid against the authenticated agent identity. This allows a low-privileged enrolled agent to spoof cluster attribution in indexed inventory and vulnerability documents by forging wazuh.cluster.name values and influencing the document _id prefix, potentially tampering with inventory records or, in shared-indexer multi-cluster deployments, poisoning another cluster's records when numeric agent IDs collide.2d
CVE-2026-281455.3 MED
1.5%
0Insufficient Verification of Data Authenticity vulnerability in StylemixThemes MasterStudy LMS allows Manipulating User State. This issue affects MasterStudy LMS: from n/a through 3.7.39.3d
CVE-2026-100798.5 HIG
6.2%
2A flaw was found in Red Hat Advanced Cluster Security for Kubernetes (RHACS). When processing Kubernetes Deployments, ACS replaces deployment identity metadata based on the openshift.io/encoded-deployment-config label. A user with permission to create Deployments can set this label to "null", causing ACS to treat the workload as having empty UID, name and labels and namespace "default". This bypasses deploy-time policy detection and enforcement visibility, prevents correct persistence in Central and breaks violation reporting and compliance correlation for the affected deployment.3h
CVE-2026-62995
1.3%
0joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. in versions 1.7.1 and prior, joserfc accepts JWTs with trailing padding (==) which are not conforming to the JOSE specifications. This leads to malleability of the JWTs when consumed by joserfc. Depending on this application this might or not be an issue. This could lead to bypass of token revocation or anti-replay protection when implemented as a deny list of tokens or a deny list of token hashes. Note that ECDSA JWS are always malleable because of the malleability of ECDSA signatures (first test case in the code bellow). This makes a scheme which assumes that JWTs are not malleable brittle. However for other signatures (or MAC) schemes it might make sense to assume non malleability of the token. This issue has been fixed in version 1.7.2.4d