Apache Roller and Axis attacks: fixes and mitigation limits | Magica
Apache Roller and Axis flaws exploited as fixes hinge on product configuration
Editorial Team
••📖7 min read
Apache confirms exploitation of a Roller code-execution flaw that survives disabling XML-RPC in its administration panel. Attacks on the retired Axis 1.x library also expose enterprise applications, making product-specific mitigation and compromise checks urgent.
Roller needs an upgrade or a configuration change below its administration interface to block the exploited flaw.
Axis 1.x is retired; Apache does not plan a fixed release, leaving remediation to migration, patched builds and product vendors.
An observed Confluence intrusion reached other systems through stored credentials, making investigation part of the response.
The Apache Software Foundation has confirmed active exploitation of a critical flaw in Roller, its open-source Java server for multi-user and group blogs. Turning off its XML-RPC remote-call interface in the administration panel does not protect vulnerable installations. Separately, exploitation of Apache’s retired Axis 1.x web-services library has reached enterprise applications.
The response depends on the product carrying the vulnerable code. Roller requires an upgrade or a server configuration change; affected installations of Atlassian’s Confluence Data Center, self-managed enterprise software holding pages and attachments, can block the Axis attack by disabling their remote API. And an observed Confluence intrusion shows why closing the entry point must be followed by checks for stolen credentials and access to other systems.
Disclosure and response milestones, sourced to Apache, Rapid7 and CISA. Rapid7’s company-reported observation concerns one Confluence environment; November 21 is the federal remediation deadline for the Axis flaw. Source: Apache Axis security advisory.
Roller’s switch is checked too late
Apache’s November 17 advisory identifies CVE-2026-129448 in Roller versions 4.0.0 through 6.1.4, with a CVSS 3.1 severity score of 9.8. Its XML-RPC endpoint accepts extension types and deserializes untrusted data before authenticating the requester, allowing unauthenticated remote code execution.
The same underlying vulnerability was previously recorded as CVE-2026-82384, which listed only Roller 6.1.5 as affected. The newer notice therefore expands the affected-version record; it does not describe an unrelated flaw. Apache recommends upgrading to 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the feature is disabled.
The project’s 6.1.6 release announcement encourages users of 6.1.5 and earlier to upgrade, but flags compatibility changes: WSSE AtomPub authentication is retired, and installations still configured for fail at startup. Administrators must change that setting before upgrading. Initial setup and database-schema migrations also require a one-time token printed to the server log; Trackback support has been removed.
The management company supporting Japan's Shonan Beauty Clinic network disclosed stolen customer passwords stored without encryption and a separate booking-service incident. Treatment-related submissions were also exposed, while the affected population and financial impact remain under investigation.
Editorial Team
wsse
A report on the fixes says Roller 6.1.7, released November 11, addresses another 15 vulnerabilities. The available upgrade path therefore extends beyond the minimum release fixing this exploited flaw.
For users unable to upgrade immediately, Apache specifies two alternatives: set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping. Restart Roller after making the change. The administration-panel toggle alone fails because older versions deserialize the request before checking whether XML-RPC is enabled.
Apache has not disclosed who is behind the Roller attacks or how many servers have been compromised, according to the November 18 report. Confirmed exploitation establishes urgency without establishing the size of the campaign.
Axis moves the problem into products that embed it
Axis implements SOAP, the Simple Object Access Protocol, for creating Java web services. Apache’s November 6 advisory says CVE-2026-90436 affects all Axis 1.x versions through 1.4. A crafted SOAP fault can cause it to load an attacker-specified class and, when the request includes a string data element, invoke its string constructor before checking that it is an AxisFault. Loading the class alone runs its static initializer. Remote code execution depends on a suitable class being available to the application.
The fault is parsed before the service’s handler chain runs, so authentication handlers configured for that service do not protect it. Axis 1.x has reached end of life, and Apache does not expect to issue a fixed 1.x release. It recommends moving to another SOAP engine, such as Axis 2/Java, or using a build with its published patch applied.
That shifts the practical response toward the applications carrying the library. Confluence Data Center is Atlassian’s self-managed enterprise edition of Confluence. N-able N-central is a remote monitoring and management platform used by managed service providers to monitor, manage and automate IT infrastructure, as the Indian Computer Emergency Response Team describes in its vulnerability note.
Affected releases in the 1.x through 9.x families with “Remote API (XML-RPC & SOAP)” enabled
Upgrade to 9.2.28 or an unaffected 10.x release; disabling the remote API is a temporary mitigation
N-able N-central
Legacy API enabled
Upgrade urgently to 2026.4 HF3, build 2026.4.1.39, which disables the Legacy API; verify it is disabled on older deployments
Confluence’s remote API has been off by default for new installations since version 3.0 and was removed in 10.0. Atlassian Cloud is unaffected, the company says in its security advisory.
Unlike Roller’s admin toggle, Confluence’s approved API mitigation takes effect when saved, without a restart. Atlassian says administrators can validate it by checking that the SOAP service endpoint returns HTTP 403 Forbidden. Disabling the API may stop scripts, automations and third-party add-ons from working—a concrete operational cost of removing the exposed interface.
Rapid7 relays N-able’s statement that Legacy API is off by default, but says on-premises administrators should verify it is disabled even on 2026.4 HF2. It also relays N-able’s guidance that hosted environments received temporary protections, while both hosted and on-premises customers still need to follow Agent and Probe upgrade instructions. The analysis also says N-able temporarily disabled its Intune integration as a precaution. Hosted protection does not remove the customer-side upgrade responsibilities.
Atlassian’s mitigation screenshot shows the Remote API checkbox cleared. Atlassian says saving the change takes effect without restarting Confluence. Source: Atlassian security advisory.
One intrusion shows what an exposed knowledge system can unlock
Rapid7’s managed detection and response team observed exploitation against a customer’s Confluence Data Center environment on November 13. Requests returned HTTP 500 errors, yet endpoint telemetry showed the Java process launching Bash and curl within seconds. Those HTTP errors did not mean the attack had failed.
In the company’s account, attackers used Confluence’s own database credentials to access MySQL just over three minutes after the first observed execution. They searched pages and attachments for credentials, tokens, VPN configurations and private keys, and hunted for payment-card numbers.
Some attempted expansion failed, including an AS-REP roasting attempt against a domain controller. But roughly four hours after the initial exploit request, the attacker had acquired a service-account credential and was querying a production cloud data warehouse. Approximately twelve hours after that first request, the attacker signed in to Microsoft 365 using an integration account and legacy authentication.
This is evidence from one observed environment, not a measure of the wider campaign. It nevertheless demonstrates why an application compromise can outlast removal of its vulnerable entry point: credentials available inside it can provide access elsewhere.
For N-central, the attribution to this specific flaw is less direct. Rapid7 cites N-able’s November 13 report of exploitation involving a vulnerability that strongly correlates with CVE-2026-90436, separately from its own direct observation in Confluence. Rapid7 also says a public Metasploit module targeting vulnerable Confluence instances was released on November 17.
The next step is mitigation plus investigation
The US Cybersecurity and Infrastructure Security Agency added the Axis flaw to its Known Exploited Vulnerabilities catalog on November 18, with a November 21 remediation due date. A report on the addition says federal agencies were instructed to address it by that date. The catalog entry marks forensic triage as required under Binding Operational Directive 26-04 and lists use in ransomware campaigns as unknown.
Rapid7 recommends emergency remediation outside normal patching cycles, prioritizing internet-accessible instances with the relevant APIs enabled and checking internal deployments too. Its published indicators can help guide investigation, but it cautions that the absence of those indicators does not establish that an environment escaped compromise. Atlassian separately tells customers to investigate affected installations for evidence of compromise.
The outstanding question for an exposed organization is whether an attacker already used the application’s access. Closing the endpoint addresses future entry through that flaw. The observed Confluence intrusion makes the remaining investigation specific: examine application execution and the use of credentials that the application could reach, including activity in downstream systems.
N-able says an intruder reached a server supporting Mail Assure and SpamExperts Hosted Cloud. Mail delivery and filtering continued, but customers lost management access as the company revoked tokens and worked to restore services securely.
Microsoft is testing an optional Edge mode that blocks WebGL and WebGPU to reduce opportunities for browser exploitation. An early hands-on test found that restoring graphics for a trusted site also removed its broader Enhanced Security protections.
A critical authentication bypass gave a suspected China-linked espionage group access to VMware's virtualization control plane. Mandiant says the campaign stole signing keys and virtual-machine data, making compromise checks essential alongside patching.
PHP’s November 19 security releases address seven critical flaws, including unauthenticated code execution through reused backend connections. Patching takes priority, but applications that retain session upload progress must also check shared storage and serialization settings.
TfL has shut its Oyster photocard website after a breach that may have exposed around 265,000 customers’ account details, including security answers. Existing cards still work, while the attack method and restoration timetable remain undisclosed.
Around 40 Irish credit unions are implicated in a saved-payee data breach at software supplier Wellington IT. Missing logs leave the victim count unresolved, while a minister is seeking answers about the disclosure delay.
JPMorganChase says it believes attackers accessed marketing data at outside service providers, potentially exposing customer names and email addresses. The bank says services are unaffected, but has not identified the vendors or disclosed the attack date.
StepSecurity’s Elephant-led Series A will fund broader protection for developer machines, package downloads and build pipelines, alongside planned defenses for AI-agent sandboxes. Its challenge is turning open-source adoption into a larger commercial platform while proving the extra controls earn their place.
Nvidia says it has found no indication its own systems were affected after The Gentlemen ransomware group listed it on a leak site. The investigation concerns a possible incident at a partner, while the gang has supplied no public proof.
Senators from both parties plan to delay the CISA nomination of Palantir security chief Michael LoSapio after his Jan. 6 denial, adding a confirmation obstacle as the agency faces staffing losses and funding decisions.
Sean Cairncross is leaving as national cyber director, with Pentagon CIO Kirsten A. Davies reportedly selected to succeed him. The transition puts Senate confirmation at the center of a cybersecurity leadership reshuffle.
Windows baseline protection combines existing PC safeguards into a verifiable pass-or-fail result. Microsoft defines the standard; developers choose whether failure means a warning, fewer features or blocked access.
F5 lists fixed releases for a critical nginx HTTP/2 flaw, while the wider NGINX2Root disclosure covers five independent nginx attack paths and a separate Linux kernel bug. Remediation depends on configuration, supplier patch levels and replacing vulnerable running processes.
Tyler Robert Buchanan received six years in U.S. prison for a phishing and SIM-swapping conspiracy that stole at least $11.6 million from individuals. He is the last of five defendants sentenced; restitution remains pending.
The new Threat Disruption Center makes TRM Labs its main technology partner following a reported $94.66 million sole-source award for Homeland Security Task Force investigations. A rival lost its court challenge, but the launch leaves the center’s share of that spending and its performance benchmarks undisclosed.
Fandango says payment details from certain October 8–11 transactions may have been exposed. State disclosures provide only a partial affected count, while the company has not explained how the checkout page was compromised.
Norway’s state-controlled oil and gas group is working to neutralise an attack on some IT systems. Employee services may be disrupted, but Equinor says operations and production remain unaffected and it has found no indications of data theft.
Tor urges relay operators to install 0.4.9.17 as a continuing DDoS attack strains its privacy network. A post-upgrade operator account describes further disruption, while Bitcoin connectivity measurements show partial recovery with important limits.
Malicious code in Optimizely website-testing projects could swap cryptocurrency addresses and skim payment cards. Optimizely says it has fixed the vulnerability and removed the code, but visitor exposure and losses remain unquantified.