Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

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.

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.

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.

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.

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.)

Every security team is being told to adopt AI. Far fewer have been shown what "good" looks like in practice. Turnkey agents handle common, well-defined security tasks, but no two security teams operate the same way. Each has its own data, playbooks, escalation paths, and risk tolerances; unique context that no vendor can anticipate in a packaged solution.

Spend any time with senior infrastructure and IT leaders right now and one conversation keeps coming up. The business wants AI, and increasingly it wants agentic AI: systems that don’t just recommend an action but take it. Boards have seen the productivity numbers. Competitors are announcing pilots. The pressure to move is real. At the same time, those same leaders own the risk register. They answer to regulators, auditors, and, when something goes wrong, the front page.

Cloud applications are constantly evolving to accommodate new users, tools, and ways of working. However, every adjustment can also alter who has access to resources and what they can do with them. A misconfiguration occurs when an active setting fails to meet established security criteria. It can grant more access than necessary, keep an insecure protocol enabled, allow certain actions for too many users, or open a pathway for information to leave the organization.

The Homegrown Agent Maturity Model for Execution & Risk (HAMMER): is a five-level framework with seven domains for security teams to locate where they stand on securing homegrown agents, then make the case for what they need to advance. The most powerful AI agents in your enterprise may be ones you never bought. Your own teams are building them by wiring models, tools, and data into software that acts on its own, often with little security approval or oversight.

Vibe-coding platforms let you go from prompt to a deployed app in a single session, a pace that outpaces the review cycles most teams built for slower releases. With Lovable nearing 8 million users by late 2025, and Replit past 50 million by April 2026, we wanted to answer a sharper question than “is vibe coding safe?” Does the platform generating the code change the outcome, and does one security prompt give you the same security everywhere?