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.
go get gopkg.in/yaml.v2@v2.4.0Is your project on an affected gopkg.in/yaml.v2?
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
YAML Go package vulnerable to denial of service
- Affected
- <2.2.3
- Fixed in
- 2.2.3
yaml package for Go can consume excessive amounts of CPU or memory
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Excessive resource consumption in gopkg.in/yaml.v2
- Affected
- <2.2.4
- Fixed in
- 2.2.4
Excessive Platform Resource Consumption within a Loop in Kubernetes
- Affected
- <2.2.8
- Fixed in
- 2.2.8
Excessive resource consumption in YAML parsing in gopkg.in/yaml.v2
- Affected
- <2.2.8
- Fixed in
- 2.2.8
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.