Container: Go standard library vulnerability reporting
Snyk Container will automatically report vulnerabilities found in the Go standard library for all container images built from Go binaries. The stdlib dependency is now included in the dependency graph versioned to the Go release used for the build, with automatic detection enabled for all organizations starting October 7, 2026.
Snyk Container will begin reporting vulnerabilities from the Go standard library for all customers. Scans of container images built from Go binaries identify the standard library version the binary was compiled with and report known vulnerabilities against it.
Affected images gain a new stdlib dependency in the dependency graph, versioned to the Go release used for the build, for example stdlib@1.25.10. Detection works for standard, stripped, and CGo builds.
No configuration is required, and reporting is enabled automatically for all organizations. Standard library reporting in the Snyk CLI requires v1.1303.2 or later.
This change is scheduled to take effect on October 7, 2026.
Source: original entry ↗
More from Snyk
Follow Snyk to get its new changes in your feed and email digest.
Snyk Code October update: improved analysis and more findings
Snyk Code now analyzes projects more deeply and accurately across Java, Kotlin, Go, TypeScript, JavaScript, Python, C#, PHP and Ruby, with significantly more findings reported. Improvements include better import resolution via config files, corrected PHP typing, expanded library coverage, new vulnerability detection rules, and enhanced template and serverless application analysis.
Snyk CLI v1.1308.0 released
Introducing HTML report generation for test commands, experimental agent-scan improvements with risk indicators, and substantial reliability fixes for Maven, Gradle, and .NET projects to prevent stack overflows and scanning failures.
ADS installer now available as packaged binary
The Agent Supply Chain Security installer now ships as signed macOS .pkg and Windows .msi packages, eliminating the need for custom scripts and MDM integration. The installer registers scheduled jobs automatically for independent scan execution.