limbo.watch
Menu

Likely permanent: GitHub doesn’t review this ecosystem

GHSA-6rx6-q6r6-mmj5

EVerest on other · published in everest/everest

Read the advisory on GitHub ↗

Fixed in 2026.02.1+. Dependabot, npm audit and OSV-Scanner probably never will. Find it in your project

Facts

Severity
Medium · CVSS score 6.5CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected versions
Confirmed on commit 284864ebacb3f565363e9616da9a5ce4de5759a8 when the Huawei FusionCharge V100R023C10 driver is deployed and an attacker has same-L2 raw Ethernet access to the GOOSE interface.As entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in
2026.02.1+
CVE
CVE-2026-42292 · 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 EVerest Confirmed on commit 284864ebacb3f565363e9616da9a5ce4de5759a8 when the Huawei FusionCharge V100R023C10 driver is deployed and an attacker has same-L2 raw Ethernet access to the GOOSE interface.

Upgrade to 2026.02.1+ or later. Dependabot, npm audit and OSV-Scanner probably never will.

Timeline

  1. 2026-07-16 15:36 UTC

    Published by the maintainers

    Cites CVE-2026-42292

  2. 2026-10-31 12:45 UTC

    First seen by Limbowatch

    CVE still reserved · not reviewed · not in OSV

  3. Waiting

    CVE record published

  4. Not expected

    Reviewed by GitHub

    GitHub doesn’t review this ecosystem

Machine-readable record: feed/GHSA-6rx6-q6r6-mmj5.json