Menu

The scan failed on the vendor's own agent
📰

The scan failed on the vendor's own agent

DEV Community: go·Alexandru Cazan·about 5 hours ago
#lKbpjnxo
#devtogo#devto#dev#google#cloud
Long article (410 words) — no AI summary yet.
Reading 0:00
15s threshold

Originally published at tothenoc.substack.com

Our image was clean. The package that failed came from the cloud's own repository.

Before a hardened image goes public on Google Cloud, Google runs its own validation on it. Part of that is a vulnerability scan of every package, including the Go standard library compiled inside binaries.

Two of our images failed it: AlmaLinux 10 and Rocky Linux 10.

The finding was not in anything we added. It was google_osconfig_agent, Google's own management agent, installed from Google's own repository. It was built with Go 1.25.5. The scanner wanted at least 1.25.13 (CVE-2026-39821).

First idea: wait for a new package. I checked the repositories. Stable still had the same build. Unstable and the next upstream tag were built with Go 1.26.3, still under the line (the fix there is 1.26.6). Waiting would not fix it, not in days.

Second idea: remove the agent. No. Without it, patch management and inventory from the console stop working for the customer.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.