Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article3 min readViews0

Rapid7 Detected Attacks on Confluence: What to Check on Your Server

Exploitation of CVE-2026-90436 was observed on November 13. We examine the condition of the legacy API being enabled, the 9.2.28 patch, temporary disabling, and the scope of verification.

Comments 0

A closed metal box with a latch and paper documents behind a side window on a turquoise background
In this article

On November 16, Rapid7 reported exploitation of CVE-2026-90436 in Confluence Data Center: its MDR team observed such an attack in a client environment on November 13. If your company hosts Confluence on a dedicated server or VPS, check the version and Remote API (XML-RPC & SOAP) configuration. A patch and a temporary mitigation are available for affected installations.

What Changed

The vulnerability was already known; the new fact is the published confirmation of its use against Confluence, not the appearance of another demonstration exploit. Rapid7 recommends mitigating the risk on externally accessible systems outside the regular update cycle. Internal instances should also be checked.

The report does not specify the total scale of attacks or the number of affected organizations. Observing an incident at one client does not mean every server running Confluence has been compromised.

Who Needs to Check

  • Confluence Data Center branches 1.x–9.x require verification if Remote API (XML-RPC & SOAP) is enabled. The fixed version is 9.2.28.
  • In new installations starting with Confluence 3.0, this setting is disabled by default. For old or modified configurations, verify its actual state.
  • In Confluence 10.x, the feature has been removed. Atlassian Cloud is not affected by this vulnerability.

The issue is related to the Apache Axis library in the legacy API. According to Atlassian, under specific conditions, an unauthenticated attacker can execute commands with the privileges of the operating system account running Confluence. This creates a risk to the data, files, and service availability accessible to that account.

What administrators should do

Update the affected installation to 9.2.28 or plan a compatible migration to the unaffected 10.x branch. Align the target branch choice with application and integration requirements.

If updating is delayed, Atlassian recommends temporarily disabling the legacy API: General Configuration → Further Configuration → Edit, uncheck Remote API (XML-RPC & SOAP), and save. The change takes effect without a restart. First, assess dependencies: scripts, automation, and add-ons using this API may stop working.

After saving, reopen the settings and ensure the checkbox is cleared. Then navigate to /plugins/servlet/soap-axis1/confluenceservice-v2 on your Confluence. According to Atlassian instructions, you should expect an HTTP 403 Forbidden response. If the check fails, reverify the setting and contact the vendor. This verifies API disabling, not the absence of a prior breach.

Updating and investigating are separate tasks

A disabled API or an installed patch does not prove that no prior intervention occurred. For a previously exposed vulnerable installation, preserve logs before cleanup and have a specialist check for signs of compromise. The absence of specific indicators from the Rapid7 report also does not confirm server security.

Information verified on November 17, 2026, at 00:08 MSK. The attack observation date was November 13, and the report publication date was November 16.

Discussion 0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.