GitLab Ten Out of Ten Flaw Under Active Probing: Your Weekend Update Checklist

GitLab has patched a flaw rated ten out of ten, the highest severity there is. In plain terms, it could let someone who should not have access read files off a server. Security teams began seeing probes against it almost as soon as the fix was published. So far there is no confirmed mass exploitation, but probing is how these things begin. Attackers look for the unlocked doors first.

If you or your employer use GitLab to store code, the action is straightforward. Check which version you are running and make sure it is the fixed one. If you are not sure, ask whoever looks after your systems. This is not a job to leave until Monday.

There was other news this week worth knowing. Two alleged members of a group called TeamPCP were arrested in Australia. Separately, Anthropic says seven China-based AI labs ran industrial-scale attempts to copy the behaviour of its Claude model, and that Claude itself was used to automate break-ins and data theft across several victims.

That last point matters because it shows the direction of travel. The tools attackers reach for are getting faster and more automated. The basics that protect the rest of us have not changed at all.

So here is the weekend job, and it takes about ten minutes. Go round your home and switch on automatic updates on every device: phones, laptops, tablets, smart TVs, and yes, the router. The router is the one everybody forgets. Then, if you use work software or run a server, confirm it is on the newest version.

Ten minutes now saves a very bad week later. Do it today.

If a scam message or a fake update alert is what pushed you into this in the first place, run it through our scam checker before you click anything. And if you have already lost money to a fake "security patch" email, our scam recovery guide walks you through what to do next, step by step — including how to get a crime reference number so the police can take your report forward.