Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

CVE-2026-97229: Alpine Linux GitLab Security Incident

A critical vulnerability in GitLab’s CI/CD processing became the focus of an attempted intrusion against Alpine Linux’s development infrastructure in October 2026. The incident prompted an extensive investigation, infrastructure rebuild and credential reset, despite the absence of confirmed remote code execution. What makes this case particularly important is not only the exploitation attempt itself, but a security issue discovered during remediation.

Your Artifactory is fine. Your Linux kernel hosting it might not be.

Summary As we’ve written, AI is shrinking the time between “a fix is public” and “someone has a working exploit” to near-zero. JFrog products are not affected by Linux kernel CVE-2026-98432. Artifactory, Xray, and the rest of the JFrog Platform do not contain this flaw, as it lives in the Linux kernel itself.

Why Your App Passes Security Testing but Gets Rejected at the Store

A security scan and an app store review ask different questions. Here's why app store rejection happens to secure builds, and what enterprise mobile teams check before they submit. Your build passed binary SAST. DAST ran clean on real devices. QA signed off, and the launch date went out to customers. Then the store console said no. Nothing in the security report was wrong. It was answering a different question.

PII and third-party apps: Don't trust, verify

You have likely heard the old Russian proverb: “доверяй, но проверяй.” It means “trust, but verify,” and it used to be a standard within the InfoSec community for decades. Slowly, many organizations have moved their infrastructure toward a Zero Trust Architecture, which has helped improve security postures further. But even still, unearned and unverified trust is rampant.

The Biggest Crypto Heist Ever - The 443 Podcast - Episode 394

This week on the podcast, we cover the $6 billion cryptocurrency theft from Binance. Before that, we give an update on PHP2Shell and one active exploit campaign targeting Palo Alot devices. Additionally, we discuss a compromised Claude Code extension on the Cursor AI marketplace.

Known Exploited Means Your Mitigation Is Next

Last month, the FBI arrested a suspect in its ongoing response to an attack on its job portal, allegedly carried out by criminal hacker and extortion group ShinyHunters. The agency said a contractor failed to apply a security patch to a third-party platform involved in the breach of its job portal, while Reuters reported that the contractor worked for Accenture and that the platform was Oracle PeopleSoft. (Fair warning: The Reuters article is behind a paywall.)

CRA 24-Hour Reporting Rule: What Happens If You Miss It?

The EU Cyber Resilience Act's 24-hour reporting deadline is already in force. Is your organisation prepared? Since 11 September 2026, manufacturers of covered software, IoT devices and connected products must report certain cybersecurity vulnerabilities and incidents within strict deadlines. Under the EU Cyber Resilience Act (CRA), manufacturers must submit: Within 24 hours: An early warning after becoming aware of an actively exploited vulnerability or severe incident affecting product security.

The 5 Biggest DORA Compliance Mistakes Financial Institutions Make

Are these common DORA compliance mistakes putting your financial organization at risk? The Digital Operational Resilience Act (DORA) requires financial entities to take a structured approach to ICT risk management and digital operational resilience. But organizations can still encounter gaps when translating regulatory requirements into day-to-day controls. In this video, we break down 5 common DORA compliance mistakes financial institutions should avoid, including.