Optimizely supply chain attack put malware on sites of CNN, BBC and Zoom
Visitors to at least 178 organisations' sites loaded malicious code, which could swap crypto wallet addresses and capture card details entered on pages.
Visitors to at least 178 organisations' sites loaded malicious code, which could swap crypto wallet addresses and capture card details entered on pages.
The safety of each workflow now depends largely on how its author configures write access and custom jobs.
Users who clone repositories with submodules are exposed until they install Git 2.56.1 or a patched 2.50 to 2.55 release.
Pull requests become a running record that agents update on each push, with merges blocked until review findings are closed.
Pinned commits now run even when tags or branches move, but the lockfile does not vouch that those commits are safe.
Operators still on unpatched GitLab releases remain exposed, with more than 1,000 internet-facing servers yet to be fixed.
Operators who build GitLab on their own Ruby or container images must patch Ruby as well as GitLab to close the hole.
Self-managed administrators on the affected releases need to upgrade, since over 2,700 Community Edition instances are publicly visible.
The stable release broadens where the toolchain fits into existing workflows and adds more visibility for setup and Git hooks.
Self-managed GitLab users need to upgrade now to close a flaw that could let an unauthenticated attacker run code on their servers.
The update gives teams a longer-running agent workflow while adding tighter controls for AI usage and billing.
The fix closes a route to command execution in self-hosted AI Gateway setups, while GitLab-hosted customers were already protected.
Leaked project email addresses can be abused to act as a maintainer, creating issues and merge requests that bypass IP restrictions.