Is github.com/ipld/go-codec-dagpb 1.0 vulnerable?

Go · 2 releases from 1.0.0 to 1.0.1 · latest github.com/ipld/go-codec-dagpb is 1.7.0 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. github.com/ipld/go-codec-dagpb 1.0.1, the last 1.0 release, is affected by 2 known security advisories (1 high, 1 low), including CVE-2022-2584, CVE-2022-2584. Upgrade to 1.3.1 or later to fix all of them.

Upgrade with:go get github.com/ipld/go-codec-dagpb@v1.3.1

Is your project on an affected github.com/ipld/go-codec-dagpb?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting github.com/ipld/go-codec-dagpb 1.0.1

  • LowCVE-2022-2584GO-2022-04221 Jul 2022

    Panic when decoding invalid blocks in github.com/ipld/go-codec-dagpb

    Affected
    <1.3.1
    Fixed in
    1.3.1
  • HighCVE-2022-2584GHSA-g3vv-g2j5-45f28 Apr 2022

    ipld/go-codec-dagpb panics when processing certain blocks

    Affected
    <1.3.1
    Fixed in
    1.3.1

Every github.com/ipld/go-codec-dagpb 1.0.x release

Affected: 1.0.0 to 1.0.1. Latest github.com/ipld/go-codec-dagpb: 1.7.0.

VersionKnown advisories
github.com/ipld/go-codec-dagpb 1.0.1CVE-2022-2584, CVE-2022-2584
github.com/ipld/go-codec-dagpb 1.0.0CVE-2022-2584, CVE-2022-2584

Which of your client projects are still on github.com/ipld/go-codec-dagpb 1.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/ipld/go-codec-dagpb version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/ipld/go-codec-dagpb versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.