Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Broken dropper in @mistralai/mistralai, @mistralai/mistralai-azure, @mistralai/mistralai-gcp

GHSA-jgg6-4rpr-wfh7

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

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

  • npm @mistralai/mistralai

    Affected
    >= 2.2.2, <= 2.2.2>= 2.2.3, <= 2.2.3>= 2.2.4, <= 2.2.4
    Fixed in
    no fixed version recorded

  • npm @mistralai/mistralai-azure

    Affected
    >= 1.7.1, <= 1.7.1>= 1.7.2, <= 1.7.2>= 1.7.3, <= 1.7.3
    Fixed in
    no fixed version recorded

  • npm @mistralai/mistralai-gcp

    Affected
    >= 1.7.1, <= 1.7.1>= 1.7.2, <= 1.7.2>= 1.7.3, <= 1.7.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
0.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Mistral npm @mistralai/mistralai, @mistralai/mistralai-azure, @mistralai/mistralai-gcp were compromised by a supply chain attack related to the TanStack security incident. An automated worm associated with the attack led to compromised npm package versions being published. Current investigation indicates that an affected developer device was involved. We have no indication that Mistral infrastructure was compromised. The compromised versions were removed from npm. They were available only between May 11 at 22\:45 UTC and May 12 at 01\:53 UTC. Previous and later versions are not affected by this advisory. Impact The dropper is broken, it has no impact. - setup.mjs references tanstackrunner.js but the payload file is named routerinit.js - execFileSync throws ENOENT and the tmpdir is wiped before payload runs. Bun gets downloaded to a tmpdir but no payload execution. We still recommend removing the packages, see below for remediation. Check whether you are affected You are affected if…

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

    Amended from ghsa record GHSA-jgg6-4rpr-wfh7

  2. Revision 1 · created ·

    Published from osv record GHSA-jgg6-4rpr-wfh7

Agent brief

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

# Patch Next advisory brief: GHSA-jgg6-4rpr-wfh7

Advisory: Broken dropper in @mistralai/mistralai, @mistralai/mistralai-azure, @mistralai/mistralai-gcp
IDs: GHSA-jgg6-4rpr-wfh7
Record: https://patchnext.com/advisories/ghsa-jgg6-4rpr-wfh7 (revision 2, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated (CVSS 0.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @mistralai/mistralai: affected >= 2.2.2, <= 2.2.2; >= 2.2.3, <= 2.2.3; >= 2.2.4, <= 2.2.4
- npm @mistralai/mistralai-azure: affected >= 1.7.1, <= 1.7.1; >= 1.7.2, <= 1.7.2; >= 1.7.3, <= 1.7.3
- npm @mistralai/mistralai-gcp: affected >= 1.7.1, <= 1.7.1; >= 1.7.2, <= 1.7.2; >= 1.7.3, <= 1.7.3

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @mistralai/mistralai, @mistralai/mistralai-azure, @mistralai/mistralai-gcp.
- 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-jgg6-4rpr-wfh7 (OSV record GHSA-jgg6-4rpr-wfh7 lists affected ranges: npm @mistralai/mistralai >=2.2.2 =2.2.3 =2.2.4 =1.7.1 =1.7.2 =1.7.3 =1.7.1 =1.7.2 =1.7.3 <=1.7.3)
- Verified: https://github.com/advisories/GHSA-jgg6-4rpr-wfh7 (GitHub-reviewed advisory GHSA-jgg6-4rpr-wfh7 lists affected ranges: npm @mistralai/mistralai >=2.2.2 =2.2.3 =2.2.4 =1.7.1 =1.7.2 =1.7.3 =1.7.1 =1.7.2 =1.7.3 <=1.7.3)

Commands are suggestions: review each one before running it.

Loading voting…