G2

Nathan P.

Sr. Software Engineer

Mid-Market (51-1000 emp.)

6/26/2026

"CVE Management and Remediation: A return to sanity"

5/5

What do you like best about Chainguard?

At first, I assumed it would be more like, “oh, they’ll make my life easier with CVEs.” But after using the service, I’ve found the real strength is the ability to build custom images that include the packages and libraries you actually need. In a lot of architectures you end up with plenty of one-off images, and with Chainguard you can replace those with their CVE-hardened versions. Review collected by and hosted on G2.com.

What do you dislike about Chainguard?

This isn’t a complaint, and I know it’s already on their roadmap, but I’d really like to see STIG and FIPS VMs offered in addition to their container images. That would help a lot with on-prem infrastructure, especially if I could swap out all the OSs on my bare-metal servers and OpenStack VMs. Review collected by and hosted on G2.com.

What problems is Chainguard solving and how is that benefiting you?

Time.

The open source images, as well as the base images we use for our own applications, create a large attack surface. We can remediate issues ourselves by swapping libraries, patching images, or forking upstream, but it turns into a never-ending game of whack-a-mole. Chainguard changes that by letting me continuously update and address CVEs across all of our images, in seconds rather than hours.

Also the price point for their product catalog is more than worth it if you consider the worth of several engineers consistently focusing (and repeating) on CVE tasks. Review collected by and hosted on G2.com.