limbo.watch
Menu

In limbo for 111 days

GHSA-9h7x-pggj-f6mq

github.com/esm-dev/esm.sh on Go · published in esm-dev/esm.sh

Read the advisory on GitHub ↗

Facts

Severity
High · CVSS score 8.6CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Affected versions
commit 48d76b947d1f3185b3a7a9af4cdcaf02c263d938, server release line v137 as present in server/release.goAs entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in
not stated
CVE
CVE-2026-102545 · reserved, record not publishedThe ID is public but empty: looking it up returns nothing. The CVE Program expects publication within 72 hours.
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use github.com/esm-dev/esm.sh commit 48d76b947d1f3185b3a7a9af4cdcaf02c263d938, server release line v137 as present in server/release.go

No fixed version is listed yet. Check the advisory for workarounds. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2026-07-24 12:14 UTC

    Published by the maintainers

    Cites CVE-2026-102545

  2. 2026-10-28 07:19 UTC

    First seen by Limbowatch

    CVE still reserved · not reviewed · not in OSV

  3. Waiting

    CVE record published

  4. Waiting

    Reviewed by GitHub

  5. Waiting

    In OSV; scanners can see it

Machine-readable record: feed/GHSA-9h7x-pggj-f6mq.json