limbo.watch

In limbo for < 1 day

GHSA-fvg8-f358-w2c8

@modelcontextprotocol/inspector on npm · published in modelcontextprotocol/inspector

Read the advisory on GitHub ↗

Fixed in 2.15.0. Dependabot, npm audit and OSV-Scanner won’t flag this yet. Find it in your project

Facts

Severity
Low · CVSS score 3.1CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Affected versions (@modelcontextprotocol/inspector)
>= 2.0.0, <= 2.14.0As entered by the maintainer. Not reviewed.
Fixed in (@modelcontextprotocol/inspector)
2.15.0
Affected versions (@modelcontextprotocol/inspector)
<= 1.0.4As entered by the maintainer. Not reviewed.
Fixed in (@modelcontextprotocol/inspector)
1.0.5
Affected versions (@modelcontextprotocol/inspector-server)
<= 1.0.4As entered by the maintainer. Not reviewed.
Fixed in (@modelcontextprotocol/inspector-server)
1.0.5
CVE
None cited by the advisory
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use @modelcontextprotocol/inspector >= 2.0.0, <= 2.14.0

Upgrade to 2.15.0 or later. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2026-11-12 01:33 UTC

    Published by the maintainers

    No CVE cited

  2. 2026-11-12 15:42 UTC

    First seen by Limbowatch

    not reviewed · not in OSV

  3. Waiting

    Reviewed by GitHub

  4. Waiting

    In OSV; scanners can see it

Machine-readable record: feed/GHSA-fvg8-f358-w2c8.json