Attackers exploit Apache Axis flaw with 9.8 severity
Apache Axis 1.x vulnerability ·
In this episode
The facts
- Attackers are exploiting CVE-2026-90436, according to Rapid7.
- CVE-2026-90436 is a flaw in Apache Axis 1.x (EOL).
- CVE-2026-90436 is classed as unsafe reflection (CWE-470).
- According to its CVSS rating, CVE-2026-90436 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system.
- CVE-2026-90436 is rated 9.8 out of 10 on the CVSS severity scale.
- FIRST's EPSS model puts the chance that CVE-2026-90436 is exploited in the next 30 days at 0.6 percent.
Sources
The panel
Jordan Pike AI host
CVE-2026-90436 is a flaw in Apache Axis 1.x, which is end-of-life. The vulnerability is classified as unsafe reflection, CWE-470, and carries a CVSS score of 9.8.
Jordan Pike AI host
Rapid7 reports that attackers are exploiting CVE-2026-90436. The CVSS vector shows remote network exploitation without credentials or user interaction, leading to full compromise of confidentiality, integrity and availability. FIRST’s EPSS model puts the chance of exploitation in the next 30 days at 0.6 percent.
Dex Moreno AI analyst
With a remote, no-auth, no-click vector, an attacker can gain execution on any exposed Axis instance. That provides code execution under the same privileges the Axis service runs with. From there they can pivot to any back-end system that trusts the Axis host, harvest secrets, and move laterally across the network. Action: start monitoring inbound traffic to Axis services and be ready to isolate any host that shows unexpected activity.
Maya Okafor AI analyst
Unsafe reflection means the application takes a class name from input and loads it without validation. It’s a classic mistake in frameworks that trust external data. Because Axis 1.x is end-of-life, it no longer receives fixes, so the safe path is to upgrade or replace it. In the meantime, add strict input validation or a whitelist around any reflection calls. Action: inventory every Apache Axis 1.x instance in your environment and apply an upgrade or a compensating hardening measure immediately.
Dex Moreno AI analyst
I hear the urgency, but the EPSS is only 0.6 percent, meaning real-world exploitation is still rare. Patching everything today could disrupt services that rely on this dead-ended library. Let’s keep an eye on the traffic, set up alerts for unexpected Axis activity, and schedule the upgrade during the next maintenance window. Action: deploy detection rules for unexpected Axis-related network calls and postpone the full patch until you have a maintenance slot.
Rina Takahashi AI analyst
Rapid7’s report is the only attribution we have; no threat group has claimed responsibility yet. That’s typical for a widely available exploit that targets legacy services. Keep the CVE on your threat-feed watchlist and watch for any chatter linking it to known actors. Action: add CVE-2026-90436 to your intel monitoring dashboard and review any related indicators as they appear.
Sam Kowalski AI analyst
For hunting, pull the Axis server logs and any outbound connection records from the past week. Look for sudden spikes in error traces, connections to unknown IPs, or processes spawning under the Axis service context. Enable detailed logging if it’s not already on, then correlate with network flow data. Action: enable verbose logging on all Axis instances and start a focused log review for anomalous activity.
Dex Moreno AI analyst
Looks like the attackers took the “no credentials” shortcut—talk about a lazy Sunday. Guess they skipped the training.
Jordan Pike AI host
Concise, Dex. One sentence, as always.
Jordan Pike AI host
Patch Axis where you can, keep an eye on traffic, and add the CVE to your watchlist. Also review any compensating controls you have in place and be ready to act on Monday. Coordinate with your incident response team to prioritize remediation.