limbo.watch

In limbo for 143 days

GHSA-w9cj-mg3x-qjm4

@shriyanss/js-recon on npm · published in js-recon/js-recon

Read the advisory on GitHub ↗

Facts

Severity
Critical · CVSS score 9.3CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Affected versions
>= v1.2.1-beta.1As entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in
<= v1.3.1-beta.1
CVE
CVE-2026-55378 · published
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use @shriyanss/js-recon >= v1.2.1-beta.1

The fixed-version field says “<= v1.3.1-beta.1”. Check the advisory for which version fixes it. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2026-06-22 11:48 UTC

    Published by the maintainers

    Cites CVE-2026-55378

  2. 2026-10-31 12:45 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-w9cj-mg3x-qjm4.json