Today's picture
Three different threat categories converge today. A 13-year-old Apache ActiveMQ vulnerability just landed in CISA's Known Exploited Vulnerabilities catalog after attackers started targeting the 7,500 exposed instances still running online. A commercially available AI voice phishing platform is automating the entire attack chain from spoofed email to credential harvest with no technical skill required. And a disgruntled security researcher dropped a second Windows Defender zero-day in two weeks after a dispute with Microsoft, promising more to come.
Threat snapshot
3 new · 2 monitoring
New
KEV Listed
Apache ActiveMQ flaw hid for 13 years. Now exploited. 7,500 servers still exposed.
RCE via Jolokia management API. CISA deadline April 30. ActiveMQ has been a ransomware entry point repeatedly since 2021.
New
Threat Intel
ATHR platform puts AI voice phishing on autopilot for anyone with $4,000
Full TOAD attack chain automated. AI voice agents impersonate support staff. No technical skill needed to target Google, Microsoft, or financial accounts.
New
High
Researcher drops second Windows Defender zero-day. Threatens more if Microsoft does not respond.
Second public exploit in two weeks from the same researcher. Privilege escalation to SYSTEM. Public PoC code circulating since April 3.
Detailed intelligence
Full analysis
01 New KEV Listed
Apache ActiveMQ flaw hid for 13 years. Now exploited. 7,500 servers still exposed.
CVE-2026-34197
What happened
CISA added CVE-2026-34197 to the Known Exploited Vulnerabilities catalog today with a federal remediation deadline of April 30. The vulnerability is in Apache ActiveMQ Classic, the widely deployed open-source message broker used across financial services, healthcare, government, and e-commerce environments. The flaw, discovered by a Horizon3.ai researcher using AI-assisted analysis, sat undetected in the codebase for 13 years. It works by exploiting the Jolokia JMX management API, allowing an attacker to trick the broker into fetching a remote configuration file and executing arbitrary OS commands. On some ActiveMQ versions, this can be done without authentication by chaining with a separate known flaw. Apache patched it in late March in versions 5.19.4 and 6.2.3. Threat monitoring service ShadowServer is currently tracking over 7,500 exposed ActiveMQ instances online.
CyberSip™ Take
This one checks every box that should accelerate response. ActiveMQ has been a repeat ransomware entry point since 2021, so threat actors know it well and already have post-exploitation playbooks built around it. The Jolokia API that makes this exploitable is a management interface, which means a successful attacker is not just landing on one server — they are landing on the system that orchestrates messaging across an entire distributed application stack. Thirteen years of undetected presence is a sobering reminder that attack surface audits based on known CVEs consistently miss what has not yet been found. The more actionable signal here is the exposure count: 7,500 internet-facing instances is not a small population, and automated scanning against them is already underway. If your organization runs ActiveMQ, this is the week to verify which version is deployed and whether the management interface is reachable from outside your network perimeter.
Recommended actions
- Upgrade to ActiveMQ Classic version 5.19.4 or 6.2.3 immediately. Federal deadline is April 30.
- Verify the Jolokia API endpoint at /api/jolokia/ is not exposed to untrusted networks
- Review broker logs for suspicious network connector activity referencing vm:// URIs with brokerConfig=xbean:http and unexpected POST requests to /api/jolokia/ invoking addNetworkConnector
- Check for unusual outbound connections from the ActiveMQ broker process and unexpected child processes
Derived from the federal known-exploited vulnerability catalog, national vulnerability database, and vendor security advisories
02 New Threat Intel
ATHR platform puts AI voice phishing on autopilot for anyone with $4,000
What happened
Researchers at Abnormal Security identified and analyzed ATHR, a commercially available cybercrime platform advertised on underground forums for $4,000 plus a 10 percent commission on proceeds. ATHR automates the full telephone-oriented attack delivery chain from start to finish. It generates brand-specific spoofed lure emails, routes inbound callbacks to either an AI voice agent or a human operator through a browser-based telephony interface, and captures credentials in real time through pre-built phishing panels for Google, Microsoft, Coinbase, Binance, and other platforms. The AI voice agents use a custom text-to-speech engine designed to sound like support staff. Operators monitor live sessions through a dashboard showing each target, the page they are on, and what has been captured. No specialized infrastructure or technical knowledge is required to operate the platform.
CyberSip™ Take
ATHR is not a new attack technique. Voice phishing has existed for years. What this platform represents is the industrialization of an attack that previously required significant manual effort and technical skill to execute at scale. When a $4,000 subscription replaces a team of social engineers and a custom telephony stack, the number of actors who can run these campaigns grows dramatically. The Booking.com follow-on attacks we covered in Issue 5 are the practical version of what ATHR enables at a much higher volume. The defense does not change: no legitimate organization will call you and ask you to verify credentials, approve an MFA push, or provide a one-time code. The problem is that most employees have not internalized that rule as a hard reflex, and an AI voice that sounds natural and knows contextual details about your account is specifically designed to erode that skepticism before the request even lands. Security awareness training that does not include a simulated vishing scenario is not keeping up with the current threat.
Recommended actions
- Add a simulated vishing scenario to your security awareness program. Email phishing simulations alone no longer reflect the full threat.
- Reinforce a single standing rule with all staff: hang up on any inbound call requesting credentials, MFA codes, or security actions, then call back on a verified number
- Brief finance, IT help desk, and executive assistant teams specifically — these are the highest-value targets for TOAD attacks
- Review whether your MFA implementation uses push notifications, which are susceptible to real-time relay attacks, and evaluate phishing-resistant alternatives
Derived from threat intelligence research and vendor security analysis
03 New High
Researcher drops second Windows Defender zero-day. Threatens more if Microsoft does not respond.
CVE-2026-33825
What happened
A security researcher going by the alias Chaotic Eclipse has published a second Windows Defender privilege escalation exploit less than two weeks after Microsoft patched the first one, which was included in Tuesday's Patch Tuesday as CVE-2026-33825. The researcher states they were working with Microsoft under a responsible disclosure agreement and that the arrangement broke down. The new exploit, again targeting privilege escalation in Windows Defender, was dropped publicly with a statement threatening to release more severe remote code execution exploits if Microsoft does not engage. Security researchers have confirmed the second exploit functions on unpatched systems. Microsoft has not commented publicly at the time of this writing.
CyberSip™ Take
The vendor relationship dynamics here are not the security story. The operational reality is that public exploit code for Windows Defender privilege escalation is circulating with more potentially on the way, on a platform that is running on virtually every Windows endpoint in every enterprise environment. Defender is not just antivirus anymore — it is deeply integrated into the security posture of Windows and the Microsoft security stack. A privilege escalation flaw in Defender that can be combined with any lower-privilege initial access gives an attacker a reliable path to SYSTEM on the target machine. Tuesday's Patch Tuesday addressed CVE-2026-33825 specifically, and Defender updates automatically on most systems. The immediate action for any organization is to confirm that Defender's antimalware platform has updated to version 4.18.26050.3011 or later, which contains the fix. The threat of additional disclosures means this situation should be monitored closely over the coming days.
Recommended actions
- Confirm Microsoft Defender Antimalware Platform has updated to version 4.18.26050.3011 or later across your environment
- On systems where automatic updates are disabled, force an immediate Defender signature and platform update
- Monitor Microsoft Security Response Center and threat intelligence feeds for additional disclosures from this researcher over the next week
- Treat any system where Defender has not received this update as having an active privilege escalation exposure until remediated
Derived from vendor security advisories, April 2026 Patch Tuesday analysis, and security researcher disclosures
Still watching
Aging items · days 2–7
Items here remain operationally relevant but have produced no significant new developments. They drop off after 7 days.
nginx-ui CVE-2026-33032 (Issue 5). Active exploitation ongoing. Patch to version 2.3.4 if not already applied.
Day 2
Booking.com breach follow-on vishing (Issue 5). Social engineering campaigns using leaked booking data remain active.
Day 2
SharePoint CVE-2026-32201 (Issue 4). Patch applied in April Patch Tuesday. Federal deadline April 28. Apply if not yet deployed.
Day 3
Cross-source standouts
What connects this week
01
AI is collapsing the skill barrier on both sides of the threat landscape
This week alone: a researcher used AI to find a 13-year-old vulnerability that human reviewers missed. A criminal platform uses AI voice agents to run phishing operations that previously required teams of social engineers. And AI-assisted exploit development means the time between disclosure and weaponization continues to shrink. None of these are hypothetical future scenarios. They are in this issue, happening now. The organizations still treating AI as a future planning horizon rather than a present operational reality are already behind.
02
Old vulnerabilities keep showing up because no one is looking for them
CVE-2026-34197 lived in Apache ActiveMQ for 13 years. CVE-2012-1854 in Microsoft VBA was patched in 2012 and added to KEV this week. The pattern across this entire week of coverage is consistent: the most reliable entry points for attackers are not sophisticated zero-days. They are known or unknown flaws in infrastructure that organizations have been running for years without scrutiny. Exposure reduction and proactive assessment of management interfaces, broker services, and legacy components produces more security improvement per hour of effort than chasing the latest CVE numbers.
Past issues · 7-day archive