Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

On June 5, 2026, ServiceNow quietly pushed a security update to hosted customer instances. The fix, described in an internal knowledge base article, addressed a flaw that let unauthenticated users gain more access to ServiceNow-hosted data than they were ever supposed to have. No password. No credentials. The remediation itself tells the whole story: ServiceNow changed an endpoint configuration to restrict access to authenticated users only. Read that again.

When an enterprise deploys an MCP-powered AI agent, such as a coding assistant, a customer workflow automaton, an IT helpdesk bot, something quietly dangerous happens at startup. The agent inherits the full permission set of the application that launched it. If the orchestrating app holds write access to a production database, the MCP agent does too. If it can call financial APIs, trigger deployments, or read HR records, the agent inherits all of that, without ever explicitly being granted those rights.

On April 27, 2026, a threshold was crossed that the internet had never hit before. Cloudflare Radar data confirmed that automated systems, such as bots, crawlers, and autonomous AI agents, now generate 57.4% of all HTTP requests for web content. Human traffic accounts for just 42.6%. What is accelerating this transformation is agentic AI: autonomous systems that browse, search, authenticate, and transact on behalf of users without any human intervention mid-task.

As enterprises adopt AI agents, two control points are becoming common: AI Gateways and MCP Gateways. They sound similar, but they solve different problems. An AI Gateway controls how applications interact with AI models. An MCP Gateway controls how AI agents interact with tools, systems, and data exposed through MCP. Both are useful. Neither is enough on its own.

An account-takeover campaign against Instagram shows why agentic AI inherits every business logic blind spot we already had and then hands it a megaphone. Over the past weekend, a number of Instagram users, including the long-dormant Obama-era White House handle and a U.S. Space Force senior enlisted leader found their accounts hijacked. As reported by TechCrunch, the entry point wasn’t a stolen password, a phishing kit, or a zero-day in Instagram’s code.

Traditional API security protects deterministic systems with known endpoints and explicit actions, while MCP-powered AI agents operate through inferred intent, dynamic tool chaining, and natural language interactions. This requires MCP-specific security controls such as tool governance, behavioral monitoring, and semantic anomaly detection.

The enterprise security world is having two separate conversations that desperately need to collide. On one side, application security (AppSec) teams are scrambling to secure APIs – the connective tissue of every modern application. On the other, a new wave of “AI security” vendors promise to protect your LLMs from prompt injection, data leakage, and hallucinations. Both groups are solving real problems. Both are missing half the picture.

The non-human identity (NHI) problem was always the same problem: too many service accounts, too few owners, too many secrets in too many places. They sat where we left them, quietly piling up privilege, outliving the engineer who created them. Eventually someone, an auditor, sometimes an attacker, went looking and found them. Agents are a different problem.

Let’s start with a scenario. This is illustrative, not a single reported incident. A developer shares a Postman collection in Slack to move faster. “Here’s the Postman collection for the payment API. It has live auth headers so you can test prod endpoints.” The team uses it, work gets done, and the link stays. What no one realizes is that the collection lives inside a public Postman workspace. Weeks later, it is indexed by search engines. The URL requires no login.

A newly disclosed security issue, tracked as CVE-2026-44578, affecting Next.js applications is raising concerns across the developer and security communities after researchers identified multiple authorization bypass and middleware evasion paths that could expose protected application data and credentials. The vulnerabilities impact several versions of Next.js and allow attackers to bypass middleware-based authorization controls using crafted requests and route manipulation techniques.