gopkg.in/yaml.v2 vulnerabilities

Registry
Go
Latest
2.4.0

6 known advisories

The latest version, 2.4.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:go get gopkg.in/yaml.v2@v2.4.0

Is your project on an affected gopkg.in/yaml.v2?

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

Security advisories for gopkg.in/yaml.v2

  • MediumCVE-2021-4235GHSA-r88r-gmrh-7j8328 Dec 2022

    YAML Go package vulnerable to denial of service

    Affected
    <2.2.3
    Fixed in
    2.2.3
  • HighCVE-2022-3064GHSA-6q6q-88xp-6f2r28 Dec 2022

    yaml package for Go can consume excessive amounts of CPU or memory

    Affected
    <2.2.4
    Fixed in
    2.2.4
  • LowCVE-2022-3064GO-2022-095629 Aug 2022

    Excessive resource consumption in gopkg.in/yaml.v2

    Affected
    <2.2.4
    Fixed in
    2.2.4
  • MediumCVE-2019-11254GHSA-wxc4-f4m6-wwqv20 Dec 2021

    Excessive Platform Resource Consumption within a Loop in Kubernetes

    Affected
    <2.2.8
    Fixed in
    2.2.8
  • LowCVE-2019-11254GO-2020-003614 Apr 2021

    Excessive resource consumption in YAML parsing in gopkg.in/yaml.v2

    Affected
    <2.2.8
    Fixed in
    2.2.8
  • LowCVE-2021-4235GO-2021-006114 Apr 2021

    Denial of service in gopkg.in/yaml.v2

    Affected
    <2.2.3
    Fixed in
    2.2.3

Is your gopkg.in/yaml.v2 version vulnerable?

Which of your client projects still run an old gopkg.in/yaml.v2?

NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Go packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.