Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.3amended

The fuels-ts typescript SDK has no awareness of to-be-spent transactions

CVE-2024-41945GHSA-3jcg-vx7f-j6qf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@fuel-ts/account 0.93.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-41945: 0.31% estimated exploitation activity in the next 30 days; percentile 23.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Brief/Intro The typescript SDK has no awareness of to-be-spent transactions causing some transactions to fail or silently get pruned as they are funded with already used UTXOs. The Typescript SDK provides the fund function which retrieves UTXOs, which belong to the owner and can be used to fund the request in question, from fuel's graphql api. These then get added to the request making it possible to send it to the network as it now has inputs which can be spent by its outputs. Now this works when a user only wants to fund one transaction per block as in the next block, the spent UTXO will not exist anymore. However if a user wants to fund multiple transactions within one block, the following can happen: It is important to note, that the graphql API will return a random UTXO which has enough value to fund the transaction in question. - user has 2 spendable UTXOs in their wallet which can cover all expenses - user funds transaction tA with an input gotten from the API iA - user…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-3jcg-vx7f-j6qf

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-3jcg-vx7f-j6qf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-41945

Advisory: The fuels-ts typescript SDK has no awareness of to-be-spent transactions
IDs: CVE-2024-41945, GHSA-3jcg-vx7f-j6qf
Record: https://patchnext.com/advisories/cve-2024-41945 (revision 3, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @fuel-ts/account 0.93.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @fuel-ts/account: affected < 0.93.0; fixed in 0.93.0

## Suggested inspection (read-only)
- `npm ls @fuel-ts/account --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @fuel-ts/account.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3jcg-vx7f-j6qf (OSV record GHSA-3jcg-vx7f-j6qf lists affected ranges: npm @fuel-ts/account >=0 <0.93.0 (fixed))
- Verified: https://github.com/advisories/GHSA-3jcg-vx7f-j6qf (GitHub-reviewed advisory GHSA-3jcg-vx7f-j6qf lists affected ranges: npm @fuel-ts/account >=0 <0.93.0)

Commands are suggestions: review each one before running it.

Loading voting…