Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Adobe Experience Manager (AEM) Forms on Java Enterprise Edition (JEE) has suffered two critical vulnerabilities CVE‑2025‑54253 and CVE‑2025‑54254 disclosed in early August 2025. According to Adobe, both flaws carry public proof-of-concept (PoC) exploits, though there are no known in-the-wild attacks as of today.

In our recent webinar featuring Enterprise Strategy Group Principal Analyst, Tyler Shields, we discussed the widening gap between vulnerabilities organizations know about and what they can realistically fix. Most teams are swamped. Too much data, too many tools, and not enough people. Naturally, automation and AI come up as potential solutions. One comment from Tyler has stuck with me since watching and subsequently reviewing the webinar recording.

Azure CSPM (Cloud Security Posture Management) helps users maintain secure cloud setups. This post covers the basics, including the role of scanning virtual machines, various scan methods, and methods for viewing results.

Today, Snyk is launching a powerful enhancement to our API discovery capabilities through a strategic partnership with Akamai. This integration is designed to solve one of the most significant challenges in modern application security: the difficulty of providing API schemas for DAST scanning. By directly ingesting API inventories and their corresponding schemas from Akamai, we are transforming a difficult manual process into a seamless, automated workflow within the Snyk platform.

On August 5, 2025, Trend Micro released a short-term mitigation tool addressing two critical command injection vulnerabilities (CVE-2025-54948 and CVE-2025-54987) in Apex One. These flaws affect the on-premise Apex One Management Console and have been exploited in the wild. Both stem from a command injection issue that allows unauthenticated, remote threat actors to execute arbitrary code on vulnerable systems. While the vulnerabilities are similar, they differ based on the targeted CPU architectures.

For years, the cybersecurity community has discussed the theoretical risks of artificial intelligence. We’ve imagined biased algorithms and adversarial attacks, but these conversations usually stayed hypothetical. That era is over. It’s time to move beyond the theory and into the practical “how-to” of finding and exploiting vulnerabilities in AI systems. To execute this, the new OWASP AI Testing Guide (AITG) is indispensable.

Generative AI is reshaping how software is made, secured, and scaled. At Snyk’s Lighthouse event in Silicon Valley, leaders from engineering, security, and platform teams gathered to explore one big question: How do we build AI-powered systems that move fast, without breaking trust? For many, that future is already here — 60% of organizations at the Summit reported building agentic apps internally. The answers weren’t just technical. They were cultural. Organizational. Strategic.