limbo.watch
Menu

In limbo for 20 days

GHSA-w3f2-pr6x-wwjc

github.com/git-lfs/git-lfs on Go · published in git-lfs/git-lfs

Read the advisory on GitHub ↗

Facts

Severity
High · CVSS score 7.6CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Affected versions (github.com/git-lfs/git-lfs)
0.5.0-2.13.3As entered by the maintainer. Not reviewed.
Fixed in (github.com/git-lfs/git-lfs)
not stated
Affected versions (github.com/git-lfs/git-lfs/v3)
3.0.0-3.8.0As entered by the maintainer. Not reviewed.
Fixed in (github.com/git-lfs/git-lfs/v3)
3.8.1
CVE
CVE-2026-69260 · 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/git-lfs/git-lfs 0.5.0-2.13.3

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-10-22 18:51 UTC

    Published by the maintainers

    Cites CVE-2026-69260

  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-w3f2-pr6x-wwjc.json