The cybersecurity landscape has been rattled this week by the confirmation of active, malicious exploitation targeting two high-severity vulnerabilities within the Apache Software Foundation’s ecosystem. The urgency of the situation was underscored on Wednesday when the U.S. Cybersecurity and Infrastructure Security Agency (CISA) officially added one of these flaws to its prestigious but ominous Known Exploited Vulnerabilities (KEV) catalog. These developments highlight the persistent risk posed by legacy software components and the rapid pace at which threat actors are weaponizing newly disclosed security gaps.
Apache Axis Vulnerability Exploited in Targeted Attacks
The primary focus of current security concern is CVE-2026-90436, a critical vulnerability disclosed on November 6 that has sent shockwaves through enterprise IT environments. The flaw, which carries a maximum CVSS score of 9.8, represents an unsafe reflection vulnerability within Apache Axis 1.x—a Java-based SOAP implementation that has long since reached its end-of-life status. Because it is no longer actively maintained by the Apache Foundation, the software lacks modern security safeguards, leaving systems that rely on it profoundly exposed to unauthenticated remote code execution (RCE).
The real-world implications of this vulnerability were laid bare by a detailed report from the security firm Rapid7, which detected active exploitation attempts as early as November 13. The researchers observed a sophisticated attack lifecycle unfolding against a customer environment running Atlassian Confluence Data Center. In this instance, the attackers demonstrated a high level of operational maturity. After gaining an initial foothold through the Axis vulnerability, they executed hundreds of commands, successfully dumping credentials and navigating the internal database to scout for sensitive proprietary information.
The speed and precision of these actors were particularly alarming. Within just four hours of the initial breach, the threat actors had managed to exfiltrate a service account credential, which they immediately utilized to query a production cloud data warehouse. The escalation did not stop there; within twelve hours, the attackers had pivoted further, successfully signing into the victim’s Microsoft 365 environment using an integrated service account. This rapid lateral movement illustrates the extreme danger posed by vulnerabilities that allow for RCE, as they effectively serve as a master key for attackers to traverse an organization’s digital infrastructure.
The threat is not limited to isolated incidents. Rapid7 also pointed to reports from N-able regarding suspicious activity against their N-central platform, which involved a vulnerability strongly correlated with the mechanics of CVE-2026-90436. In both the Confluence and N-central scenarios, security analysts noted that the systems were only vulnerable if they were running specific, non-default configurations. This serves as a vital reminder to administrators that "default" security settings are often the first line of defense, and modifying them without a full understanding of the underlying software dependencies can create catastrophic security holes.
The scope of the threat is further confirmed by data from Previdian, a firm specializing in threat detection, which reported detecting 50 distinct exploitation attempts originating from 14 different IP addresses between November 12 and November 19. While current sensor data cannot definitively confirm the success rate of every individual attempt, the volume of activity suggests a concerted effort by multiple threat actors to identify and compromise vulnerable targets on the public-facing internet.
The resolution path for CVE-2026-90436 is complicated by the nature of the software. Because Apache Axis 1.x is officially end-of-life, the Apache Foundation has explicitly stated that it does not intend to release a patch. Instead, the foundation urges organizations to migrate to a modern, supported SOAP engine. For those currently trapped in environments that rely on this legacy code, the only recourse is to apply the specific workarounds or third-party patches published by the vendors of the affected applications.
For Confluence Data Center users, the recommendation is to upgrade immediately to version 9.2.28 or move to an unaffected 10.x release. Meanwhile, N-able has addressed the issue in N-central 2026.4 HF3 by disabling the Legacy API functionality that inadvertently exposed the vulnerable Axis component. Given the severity of the threat, CISA has mandated that all federal agencies must remediate CVE-2026-90436 by November 21, a deadline that serves as a benchmark for the private sector as well.
Apache Roller Vulnerability Also Under Active Exploitation
While the Axis vulnerability has dominated headlines due to its inclusion in the CISA KEV catalog, the Apache ecosystem is simultaneously grappling with another critical issue. The Apache Foundation has confirmed active exploitation of CVE-2026-129448, a vulnerability with a matching CVSS score of 9.8 that affects versions 4.0.0 through 6.1.4 of its popular Java-based blogging platform, Apache Roller.
In a brief but pointed advisory issued on November 17, the Apache Foundation confirmed that this flaw allows for unauthenticated remote code execution. Unlike some vulnerabilities that require complex interactions, this flaw stems from unsafe deserialization within the platform’s XML-RPC interface. This interface processes data from external sources before the system has an opportunity to perform authentication checks, providing a direct pathway for attackers to inject and execute malicious code.
One of the most troubling aspects of this vulnerability is the failure of common defensive workarounds. Apache noted that attempting to disable the XML-RPC interface via the application’s administrative interface is insufficient to block the exploit, as the underlying mechanism remains active at a level that bypasses standard configuration controls.
The history of this vulnerability is also instructive regarding the complexity of software maintenance. Apache initially identified the underlying flaw in September and assigned it the identifier CVE-2026-82384. At that time, the disclosure was limited to Apache Roller version 6.1.5. However, further investigation revealed that the scope was much wider than initially understood, leading to the current, more urgent advisory. The foundation has clarified that the flaw was ultimately addressed in version 6.1.6, and they strongly recommend that all users upgrade to that version or newer. Notably, the release of version 6.1.7 on November 11 provides additional hardening, as it addresses a staggering 15 other vulnerabilities, underscoring the importance of maintaining an up-to-date patch cycle for all web-based platforms.
The concurrent nature of these two major Apache vulnerabilities serves as a stark reminder of the "patch fatigue" that plagues modern IT departments. With threat actors actively scanning for and exploiting these flaws within hours of technical details becoming public, the window for effective remediation has narrowed significantly. Organizations relying on Apache software must prioritize inventory management to identify where these components reside within their stacks.
The security industry has seen a rise in the exploitation of Java-based vulnerabilities, as demonstrated by the long-tail effects of incidents like the original Log4j disclosure. The current situation with Axis and Roller reinforces the necessity of a proactive security posture—one that includes continuous monitoring, the rapid implementation of vendor-supplied patches, and, perhaps most importantly, the decommissioning of legacy software that can no longer be secured. As federal and private sector entities alike scramble to meet the CISA-imposed deadlines and secure their infrastructures, the message from the cybersecurity community remains clear: the cost of inaction is increasingly measured in compromised data and lost operational integrity.

