Two critical security vulnerabilities impacting Apache software components are currently being actively exploited in the wild by malicious actors. The threats have triggered urgent warnings across the cybersecurity community, software vendor updates, and swift defensive measures from federal regulators. The Cybersecurity and Infrastructure Security Agency (CISA) responded to the escalating crisis by adding one of the flaws to its heavily monitored Known Exploited Vulnerabilities (KEV) catalog, placing federal civilian executive branch agencies on a tight deadline to remediate the risk.
The active exploitation campaign highlights the persistent dangers posed by legacy components and deep-seated architectural flaws in enterprise environments. Security researchers and incident responders have observed sophisticated threat actors leveraging these high-severity vulnerabilities to infiltrate corporate networks, compromise critical databases, extract sensitive credentials, and pivot into cloud-based infrastructure and external integration services within hours of initial access.
Apache Axis vulnerability exploited in attacks
The first and more widely documented of the two issues is tracked as CVE-2026-90436. Disclosed publicly on November 6, this vulnerability involves an unsafe reflection flaw residing in Apache Axis 1.x, which is an end-of-life, Java-based SOAP implementation. Because the software package itself has reached its end-of-life status, the Apache Software Foundation does not plan to release a natively fixed version of Axis 1.x, leaving organizations dependent on alternative mitigations or migrations.
Carrying a maximum severity rating of 9.8 on the Common Vulnerability Scoring System (CVSS), CVE-2026-90436 allows unauthenticated, remote attackers to execute arbitrary code on vulnerable systems. Threat actors have waste no time turning this capability into practical intrusions. Cybersecurity firm Rapid7 revealed that it detected active exploitation of the vulnerability on November 13 within a customer environment running Atlassian Confluence Data Center.
According to Rapid7’s telemetry and analysis, the attack sequence demonstrated an alarming level of speed and tactical precision. Once the unauthenticated attacker gained entry through the vulnerable Axis component, they proceeded to execute hundreds of commands in rapid succession. They successfully accessed Confluence’s underlying database using the application’s own legitimate credentials and systematically searched the environment for sensitive corporate information.
The escalation of privileges and movement across the compromised network happened at a breakneck pace. Within a mere four hours of the initial exploitation event, the attacker had managed to obtain a service account credential. Armed with this new access, they began querying a production cloud data warehouse. Approximately twelve hours after the first exploit request was logged, the threat actor utilized an integration service account to sign in to a Microsoft 365 environment, demonstrating how a single software component vulnerability can rapidly cascade into a widespread multi-platform cloud breach.
Rapid7’s findings were further compounded by related intelligence from software provider N-able, which reported attacks against its N-central platform involving a vulnerability strongly correlated with CVE-2026-90436. Security analysts noted that both Atlassian Confluence and N-able N-central require non-default configurations to expose the underlying Apache Axis component to this form of attack.
Independent visibility into the broader threat landscape came from Previdian, a security monitoring firm that reported detecting 50 separate exploitation attempts originating from 14 distinct IP addresses between November 12 and November 19. While Previdian’s sensor data could not definitively establish whether those specific scanning and exploitation attempts achieved successful system compromise, the sheer volume of attempts underscores the automated and opportunistic nature of the threat.
Because the Apache Software Foundation will not patch the legacy Axis 1.x branch, administrators are formally advised to migrate entirely away from the legacy SOAP engine or apply specific published patches provided by downstream vendors. For Atlassian Confluence Data Center users, the recommended remediation path involves upgrading to version 9.2.28 or transitioning to an unaffected 10.x release. Meanwhile, N-able released N-central 2026.4 HF3, which completely disables the Legacy API functionality responsible for exposing the vulnerable Apache Axis component.
Recognizing the severity of the threat and the active exploitation documented in enterprise environments, CISA formally added CVE-2026-90436 to its KEV catalog. Federal civilian agencies were instructed to secure their systems against the flaw by November 21, mirroring the regulatory urgency typically reserved for the most dangerous internet-facing enterprise bugs.
Apache Roller vulnerability also exploited
Compounding the crisis for organizations utilizing Apache software ecosystems, the Apache Software Foundation has confirmed active exploitation of a second high-severity flaw. Tracked as CVE-2026-129448, this vulnerability also carries a CVSS score of 9.8 and impacts versions 4.0.0 through 6.1.4 of Apache Roller, a popular Java-based blogging platform.
Like the Axis flaw, CVE-2026-129448 allows unauthenticated remote code execution. In an advisory published on November 17, Apache acknowledged the threat candidly, stating that the issue is actively being exploited, though the organization did not provide granular details regarding the specific threat actors or campaigns leveraging the bug.
The core vulnerability stems from unsafe deserialization within Roller’s XML-RPC interface. This interface processes incoming malicious data before the application has even authenticated the user, providing a direct pathway for remote code execution without requiring valid credentials. Security researchers noted that attempting to mitigate the issue by disabling the XML-RPC feature through the application’s administrative interface is ineffective and does not prevent successful exploitation.
The disclosure of CVE-2026-129448 follows an earlier, related advisory issued by Apache in September under the identifier CVE-2026-82384. Clarifying the relationship between the two identifiers, Apache explained that the newly acknowledged flaw represents the underlying vulnerability associated with a broader range of versions than initially understood. While the original September advisory listed only Apache Roller 6.1.5 as affected, the broader scope of vulnerable legacy versions became apparent as analysis continued.
The Apache Roller vulnerability was ultimately addressed in version 6.1.6, and maintainers strongly advise all users running affected iterations to upgrade immediately to that version or later releases. The urgency of maintaining up-to-date installations was further emphasized by the release of version 6.1.7 on November 11, which remediated an additional 15 security vulnerabilities within the blogging platform, highlighting the continuous stream of maintenance and security challenges facing complex Java-based enterprise applications.






