Report · pwn.watch
What's Getting Pwned

pwn.watch
Source published October 22, 2026
Summary: 1 min read
64/100
Summary
pwn.watch is a live security-incident tracker listing 236 incidents from the previous 12 months, including 37 current incidents, 16 rated critical and 18 not fully patched. Its tracker showed no incident-free days as of Oct. 22, 2026; its longest quiet period was 11 days, from Jan. 2 through Jan. 12. The latest entries include patches for an actively exploited CVSS 9.9 SQL-injection flaw in on-premises Arista VeloCloud Orchestrator and a CVSS 10.0 unauthenticated remote-code-execution flaw affecting self-managed GitLab CE/EE versions since 7.0. Linux kernel vulnerability reports containing technical reproduction details were inadvertently sent to public mailing lists before fixes were available, including two ksmbd remote-code-execution bugs rated CVSS 9.0 by Trend Micro’s Zero Day Initiative. LiteLLM’s release pipeline was compromised on Oct. 21, briefly publishing a malicious PyPI package and compromised container tags designed to steal credentials and install a remote-code loader. The tracker also reports alleged third-party AI agents operating in U.S. bank customer accounts, a Railway incident that may have exposed customer environment variables, and a Zeabur breach exposing about 3.22 million environment-variable records. Other listed incidents include actively exploited PHP, Plex, Ivanti, FortiMail and BeyondTrust vulnerabilities, plus a Capcom ID breach affecting 11.77 million email-address records.
Key Takeaways
- pwn.watch listed 236 security incidents from the previous 12 months as of Oct. 22, 2026, including 37 live incidents and 16 critical incidents.
- Arista patched CVE-2026-114625, an actively exploited CVSS 9.9 SQL-injection vulnerability in on-premises VeloCloud Orchestrator that can let authenticated users gain operator privileges.
- GitLab patched CVE-2026-110264 on Oct. 21, 2026; the CVSS 10.0 flaw can enable unauthenticated code execution on self-managed GitLab installations.
- LiteLLM’s compromised Oct. 21 release pipeline distributed malicious PyPI and container releases that targeted cloud, developer and AI-tool credentials.
- Zeabur said an attacker accessed shared clusters and exposed roughly 3.22 million environment-variable records across 321,810 accounts; the company plans to end all services on Dec. 31, 2026.
What the discussion said
Commenters spent less time on the incident tracker’s headline and more on the unsettling premise behind it: AI agents are beginning to act inside real financial and security-sensitive systems. Several readers see agent-enabled abuse as a looming acceleration of an already fragile security environment, where cheap capable models let attackers probe, automate, and scale faster than defenders can respond. The bank example especially prompted concern about accountability: customers may deliberately grant an agent access, yet an agent’s costly mistake leaves an ugly fight over whether the customer, bank, or tool provider absorbs the loss. That alarm was tempered by skepticism. One reader noted that reported compromise data does not yet show a clear pre-2026 explosion, while others argued the banking case was mislabeled because customers, not rogue intruders, authorized the agents. The thread also rejected the idea that AI-written software will soon eliminate bugs; commenters argued current generated code often misses security reasoning, even if models can help catch narrow error classes. The tracker itself became evidence for that criticism: readers found its dense, homogenous AI-generated visual style hard to trust, and broken links plus muddled incident labels made its automated presentation look careless rather than authoritative. A few still liked its practical agent-copying feature and welcomed improvements to its historical charts.
Where opinion split
The sharp dispute is whether AI agents are already creating a qualitatively new security crisis. Alarmed commenters argue increasingly capable, inexpensive agents will turn weak security practices into mass-scale incidents and make delegated access dangerously hard to govern. Skeptics counter that public incident data has not yet demonstrated a dramatic surge, and that examples framed as rogue-agent breaches may actually be customers choosing to authorize automation.
Coverage & discussions
Hacker News · pwn.watch
Community discussions
Community Sentiment
Positives
- The tracker’s copyable instructions for agents give responders a fast path from an incident page to practical automated follow-up.
- Historical data and clearer charts could turn scattered AI-era security anxiety into something measurable instead of pure hype.
- Agentic banking exposes a real accountability problem early, forcing clearer rules before autonomous tools handle larger sums.
Concerns
- Current AI-generated interfaces cram dense status data into generic layouts, making security information harder to scan precisely when clarity matters.
- Broken feeds, dead utility links, and contradictory incident states make an AI-assisted security tracker look unreliable rather than operationally useful.
- AI-written code is not yet a security cure: commenters expect shallow generated implementations to multiply vulnerabilities unless stronger models rigorously audit them.
- Delegated agents can move money or take damaging actions under customer-granted access, leaving liability conveniently blurred when something goes wrong.
Related Articles

We May Be Living Through the Most Consequential Hundred Days in Cyber History
Apr 13, 2026

NIST gives up enriching most CVEs
Apr 17, 2026

Config Files That Run Code: Supply Chain Security Blindspot
Jun 8, 2026

Incident CVE-2026-LGTM
Jun 26, 2026

Anonymous GitHub account mass-dropping undisclosed 0-days
Jun 27, 2026