Vulnerability DatabaseGHSA-3v2v-wcw4-25q9

GHSA-3v2v-wcw4-25q9: 
JavaScript vulnerability analysis and mitigation

Summary

twzrd-x402-gate enforces three cumulative spend limits from a spend ledger: dailyCeilingUsd, monthlyCeilingUsd (mandate) and newCounterpartyCap. In 0.22.1 and earlier, a caller that set one of these limits and did not pass a ledger got no enforcement: every intent was allowed, and nothing reported that the limit was inactive.

Impact

An agent configured with a daily or monthly ceiling, or a new-counterparty cap, and no ledger could spend past that limit. Per-payment limits (maxAmountUsd, maxPerTransactionUsd) were enforced throughout and are not affected. Callers that pass a ledger are not affected.

Patches

Fixed in twzrd-x402-gate 0.23.0. A cumulative limit with no ledger is now refused with SPEND_CAP_NEEDS_LEDGER and a reason naming the limit, in evaluateIntent, the x402 client hook, the MPP hook and createTwzrdPolicyFetch, before any payment is built.

Workarounds

Pass a spend ledger wherever a cumulative limit is set: createMemorySpendLedger() for one process, or a file-backed ledger to survive a restart.

Second issue fixed in 0.23.0: concurrent paid calls through one createTwzrdPolicyFetch

Summary

createTwzrdPolicyFetch kept the offer it had cleared to pay in a single slot shared by every call on the instance. In 0.22.1 and earlier, with two calls in flight through one instance, the first call to finish recorded the other call's amount on the spend ledger and cleared the slot, so the second paid call was never recorded. Both calls were also checked against a cumulative limit before either was recorded.

Impact

An agent that makes concurrent paid requests through one policy fetch could spend past dailyCeilingUsd, a mandate's monthlyCeilingUsd or newCounterpartyCap, and its spend ledger could show less than it paid. In a local reproduction, two concurrent 0.01 payments left 0.01 on the ledger, and two 0.01 payments passed a 0.015 daily ceiling. Calls made one at a time are not affected. Per-payment limits were enforced throughout.

Patches

Fixed in twzrd-x402-gate 0.23.0. Each call keeps its own offer, an amount cleared to pay counts against the cumulative limits until the call ends, and offers are cleared one call at a time.

Workarounds

Do not issue concurrent requests through one createTwzrdPolicyFetch instance: await each call before starting the next.

Remaining limit

The reservation is per instance. Two instances, or two processes, that share one ledger can still clear payments at the same moment; hold one policy fetch per ledger.


Source: NVD

Related JavaScript vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-133867CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/express
NoYesNov 21, 2026
CVE-2026-133250CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/middie
NoYesNov 21, 2026
CVE-2026-133120CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/express
NoYesNov 21, 2026
CVE-2026-133312MEDIUM5.3
  • JavaScript logoJavaScript
  • @fastify/rate-limit
NoYesNov 21, 2026
CVE-2026-133273LOW3.7
  • JavaScript logoJavaScript
  • @fastify/swagger-ui
NoYesNov 21, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management