What is confirmed
Alpine says the 20–21 October attack targeted CVE-2026-97229 in its GitLab deployment.
The project found no evidence of code execution or tampering with packages and releases, while acknowledging gaps in retained logs.
GitLab was rebuilt, passwords and application keys were rotated, and releases were verified against independent records.
What it means
The project explains that upgrading GitLab alone did not fix its custom image: the Ruby runtime also needed the patched version.
A precautionary rebuild does not establish that the attempted intrusion succeeded.
A fix dependent on the runtime
Custom container images may inadvertently miss fixes included in official packages when they use different runtime dependencies.
Evidence and release integrity
Comparing artifacts with records outside the GitLab server helped establish confidence in release integrity.
What to do
Inventory components bundled in GitLab images, including Ruby and runtime libraries.
Verify custom builds actually incorporate dependency patches.
Retain useful logs outside affected hosts and rehearse secret-rotation procedures.
Use the related SecurCheck tool, then confirm important decisions with an official source.