• Home
  • About
  • Locations
  • Contact Us
logologologologo
  • Plan
    • AI Governance & Risk Management
    • Acquisition & VC
    • vCISO
    • Policies & Procedures
    • Strategy & Security Program Creation
    • Risk Management
  • Attack
    • Penetration Testing
    • AI Penetration Testing
    • Mobile Application Penetration Testing
    • Red Teaming
    • Web Application Penetration Testing
    • PTaaS
    • IOT Penetration Testing
  • Defend
    • Office 365 Security
    • HIPAA Compliance
    • PCI Compliance
    • Code Reviews
    • Blockchain Security Analysis
    • Vulnerability Assessments
  • Recover
    • Ransomware Recovery
    • Expert Witness
    • Forensics
  • Learn
    • Resources
    • Penetration Testing Training
    • Blog
  • Tools
    • Wp2shell Checker
    • php2shell checker
  • Instant Quote
✕

How the Confluence Data Center Flaw Exposes Your Wiki

November 17, 2026
Written By: author avatar James Knight
author avatar James Knight
James Knight is a well-known cybersecurity expert, international keynote speaker, and Senior Principal at Digital Warfare, a global cybersecurity consulting firm headquartered in McLean, Virginia, USA. Digital Warfare provides penetration testing, red teaming, vCISO, and many other services to enterprise organizations and government entities globally and across the United States. With over 25 years of hands-on experience at the intersection of offensive security and real-world threat intelligence, James has conducted pen tests, security assessments, vulnerability research, and adversarial analysis for corporate enterprises and government clients spanning financial services, critical infrastructure, and defense-adjacent sectors. His work covers the full spectrum of modern enterprise threats including advanced persistent threat campaigns, ransomware group tradecraft, supply chain compromise, AI-augmented attack techniques, and zero-day vulnerability exploitation. James is a recognized and frequently cited voice on cybersecurity in both specialist and mainstream media. Many well-known news sites, including The Daily Mail, have quoted him on many occasions: on ransomware payment policy in the context of the Colonial Pipeline attack, on how agentic AI is expected to reshape cyber warfare over the next 25 years, and on the security implications of the latest OpenAI security incident. His analysis has also been cited on Medium, where independent cybersecurity researchers have quoted his insights on supply chain security and AI-driven attack techniques. On supply chain risk, James has described the threat in terms that practitioners recognize immediately: supply chain attacks exploit the trust organizations place in third parties, requiring defenders to map every dependency like a battlefield and probe for weaknesses that could cascade across entire networks. On AI-driven attacks, his assessment reflects the same operational directness: AI-powered attacks exploit the enterprise fascination with new technology, requiring penetration testers to treat every unverified component as a potential payload delivery mechanism. His firm has been featured as a cybersecurity resource in FinancialContent and referenced across multiple professional data platforms including ZoomInfo and Datanyze as a specialist cybersecurity consulting firm serving Fortune 500 and SME organizations. At Digital Warfare, James leads the team and authors the Digital Warfare Threat Intelligence blog, publishing daily analysis of confirmed cybersecurity incidents sourced exclusively from verified primary sources including CISA advisories, vendor security bulletins, and leading threat intelligence publications. His analysis is built for security practitioners and business leaders who need actionable intelligence rather than vendor marketing. His original research includes the Digital Warfare 2026 Mid-Year Threat Pattern Report, an analysis of 28 confirmed threat incidents tracked between January and August 2026 that introduced three named security frameworks now used by enterprise security teams. The Zero-Day Priority Framework establishes a tiered patching classification system grounded in confirmed 2026 exploitation data showing that 73 percent of zero-days are weaponized within 72 hours of public disclosure. The Supply Chain Attack Taxonomy defines three distinct classes of supply chain compromise, each requiring different defensive controls and monitoring approaches. The AI Augmentation Classification documents three confirmed maturity levels of AI-assisted attack capability observed in real-world 2026 incidents, from AI-generated custom malware at Level One through fully autonomous ransomware operations at Level Three. Digital Warfare was founded in 2012 and serves corporations and governmental entities seeking rigorous security assessment and strategic security leadership from practitioners with genuine operational experience. Every member of the firm’s elite team brings over 25 years of cybersecurity experience to every client engagement. Connect with James on LinkedIn or follow his threat intelligence updates at digitalwarfare.com/blog.
See Full Bio

The Confluence Data Center flaw CVE-2026-90436 lets an unauthenticated attacker run code on the server through the legacy Remote API. Atlassian rates it critical at 9.3 and traces it to Apache Axis, the component behind the XML-RPC and SOAP APIs. Upgrade to version 9.2.28, or disable the Remote API right away.

What Is the Confluence Data Center Flaw CVE-2026-90436?

CVE-2026-90436 is a critical remote code execution flaw. Specifically, it sits in Apache Axis, the library that Confluence Data Center uses for its XML-RPC and SOAP Remote API. Atlassian rates it 9.3 on CVSS 4.0, and the vector records no privileges and no user interaction, which means an unauthenticated attacker can reach it over the network. In short, a remote attacker can run code on an exposed server without a single credential.

How Does the Confluence Data Center Flaw Let Attackers Run Code?

The path is direct. First, the server must have the Remote API using XML-RPC and SOAP switched on. Then an attacker sends a crafted, unauthenticated request to the Axis service endpoint. Because Apache Axis mishandles that request, the flaw triggers and the attacker’s code runs on the server. As a result, one exposed endpoint turns a documentation platform into attacker controlled infrastructure.

How the Confluence Data Center RCE flaw runs code through the Remote API
How the Confluence Data Center RCE works.

Which Confluence Data Center Versions Are at Risk?

Exposure depends on three conditions together. The instance must run an affected build, the Remote API must be on, and the fix must not yet be in place. Atlassian notes that the Remote API has been off by default for new installations since Confluence 3.0, and that Atlassian removed the feature entirely in Confluence 10.0. Therefore, long running, upgraded instances are the ones most likely to still have it enabled.

The three conditions that expose a Confluence Data Center to CVE-2026-90436
The three conditions for exposure.
ItemDetail
CVECVE-2026-90436
TypeUnauthenticated remote code execution through Apache Axis
CVSS9.3 Critical on CVSS 4.0 (Atlassian assessment)
VectorAV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
ConditionRemote API using XML-RPC and SOAP must be enabled
AffectedConfluence Data Center 1.x through 9.x
Not affectedConfluence 10.x and later, where the Remote API was removed
Fixed versionConfluence Data Center 9.2.28
ExploitationNo confirmed exploitation; Atlassian cannot confirm whether instances are affected

You can confirm the fixed build and the mitigation in the official Atlassian security advisory, and the tracking details in the Atlassian CONFSERVER-104610 record.

Is Anyone Exploiting the Confluence Data Center Flaw?

Atlassian has not reported known exploitation of the Confluence Data Center flaw, and it states plainly that it cannot confirm whether the flaw reached any instance. However, that is not a reason to wait. Because the flaw needs no login and scores 9.3, a public exploit would put every exposed server at immediate risk. Treat an internet facing, unpatched instance as a priority, not a maybe.

How Strong Is the Evidence Behind the Confluence Data Center Flaw?

We separate confirmed facts from open questions, so you can judge the risk yourself.

  • Confirmed by Atlassian: the flaw, the 9.3 CVSS 4.0 score and vector, the affected 1.x through 9.x range, the 9.2.28 fix, the Remote API condition, and the November 9, 2026 advisory
  • Attributed by Atlassian: the root cause in Apache Axis, which published the underlying flaw as CVE-2026-90436
  • Still open: whether any Confluence Data Center was exploited, which Atlassian says it cannot confirm, and whether CISA will add the flaw to its Known Exploited Vulnerabilities catalog

How Do You Fix or Mitigate the Confluence Data Center Flaw?

Patching is the real fix, and a setting change is the fast stopgap. Work through these steps on every Confluence Data Center you run.

  1. Patch first: upgrade to Confluence Data Center 9.2.28 or a later fixed release. Atlassian backports critical fixes as maintenance releases, so a supported LTS line has a patched build
  2. Mitigate if you cannot patch yet: disable the Remote API using XML-RPC and SOAP under General Configuration, then Further Configuration. No restart is required
  3. Expect some breakage: scripts, automations and third-party add-ons that call the Remote API may stop working, so plan for it
  4. Hunt for compromise: have your security team review exposed instances for signs of intrusion, because the flaw leaves no login trail

To confirm the mitigation, open the Axis service path below under your own base URL. An HTTP Status 403 Forbidden response means the Remote API is off and the flaw is no longer reachable.

/plugins/servlet/soap-axis1/confluenceservice-v2

Why Do Legacy Features Like the Remote API Keep Causing This?

The deeper lesson is that old features age into liabilities. The Remote API was useful years ago, yet Atlassian turned it off by default back in Confluence 3.0 and removed it in 10.0 for good reason. Meanwhile, the instances still carrying it are the long lived ones that nobody wants to touch. For that reason, a Confluence Data Center that teams have upgraded for a decade is exactly where this flaw hides. Our 2026 Mid Year Threat Pattern Report keeps finding the same story, where a forgotten setting, not a brand new bug, opens the door.

What Should Your Team Do About the Confluence Data Center Flaw Now?

Internet facing collaboration tools hold credentials, internal docs and single sign on sessions, so attackers prize them. Above all, prove the fix rather than assume it. Our team runs penetration testing and vulnerability assessments that show whether an attacker can still reach your Confluence Data Center and what lies behind it, and our PTaaS platform keeps that testing continuous between audits.

Key Takeaways

  • CVE-2026-90436 is an unauthenticated remote code execution flaw in the Apache Axis Remote API of Confluence Data Center, rated 9.3 critical
  • The flaw affects Data Center 1.x through 9.x when the Remote API is on, and Confluence 10.x and later escape it
  • Upgrade to Data Center 9.2.28, or disable the Remote API using XML-RPC and SOAP as a stopgap
  • Confirm the mitigation with an HTTP 403 response on the Axis service path, and expect some add-ons to break
  • Atlassian cannot confirm whether instances were hit, so treat every exposed server as a priority to patch

Frequently Asked Questions About the Confluence Data Center Flaw

What is the Confluence Data Center flaw CVE-2026-90436?

It is a critical remote code execution flaw in the Apache Axis component that Confluence uses for its XML-RPC and SOAP APIs. An unauthenticated attacker can run code on the server when the Remote API is on.

Which Confluence Data Center versions does the flaw affect?

The flaw affects Confluence Data Center 1.x through 9.x when the Remote API is on. Atlassian fixed it in version 9.2.28, and Confluence 10.x and later escape it because Atlassian removed the Remote API.

Does CVE-2026-90436 need a login?

No. The CVSS vector records no privileges and no user interaction, so an unauthenticated attacker can reach the flaw. That is why Atlassian rates the Confluence Data Center flaw critical at 9.3.

How do I mitigate the flaw without patching?

Disable the Remote API using XML-RPC and SOAP on the Confluence Data Center under General Configuration, then Further Configuration. It needs no restart, though scripts and third-party add-ons that use the Remote API may stop working.

How do I confirm the mitigation worked?

Browse to the Axis service path under your base URL. An HTTP Status 403 Forbidden response confirms that the Remote API is off and the Confluence Data Center flaw is no longer reachable.

Has anyone exploited CVE-2026-90436?

Atlassian has not reported known exploitation and says it cannot confirm whether the flaw reached any instance. Because the flaw needs no login and scores critical, treat every exposed Confluence Data Center as a priority to patch.

author avatar
James Knight Senior Principal, and lead threat intelligence analyst
James Knight is a well-known cybersecurity expert, international keynote speaker, and Senior Principal at Digital Warfare, a global cybersecurity consulting firm headquartered in McLean, Virginia, USA. Digital Warfare provides penetration testing, red teaming, vCISO, and many other services to enterprise organizations and government entities globally and across the United States. With over 25 years of hands-on experience at the intersection of offensive security and real-world threat intelligence, James has conducted pen tests, security assessments, vulnerability research, and adversarial analysis for corporate enterprises and government clients spanning financial services, critical infrastructure, and defense-adjacent sectors. His work covers the full spectrum of modern enterprise threats including advanced persistent threat campaigns, ransomware group tradecraft, supply chain compromise, AI-augmented attack techniques, and zero-day vulnerability exploitation. James is a recognized and frequently cited voice on cybersecurity in both specialist and mainstream media. Many well-known news sites, including The Daily Mail, have quoted him on many occasions: on ransomware payment policy in the context of the Colonial Pipeline attack, on how agentic AI is expected to reshape cyber warfare over the next 25 years, and on the security implications of the latest OpenAI security incident. His analysis has also been cited on Medium, where independent cybersecurity researchers have quoted his insights on supply chain security and AI-driven attack techniques. On supply chain risk, James has described the threat in terms that practitioners recognize immediately: supply chain attacks exploit the trust organizations place in third parties, requiring defenders to map every dependency like a battlefield and probe for weaknesses that could cascade across entire networks. On AI-driven attacks, his assessment reflects the same operational directness: AI-powered attacks exploit the enterprise fascination with new technology, requiring penetration testers to treat every unverified component as a potential payload delivery mechanism. His firm has been featured as a cybersecurity resource in FinancialContent and referenced across multiple professional data platforms including ZoomInfo and Datanyze as a specialist cybersecurity consulting firm serving Fortune 500 and SME organizations. At Digital Warfare, James leads the team and authors the Digital Warfare Threat Intelligence blog, publishing daily analysis of confirmed cybersecurity incidents sourced exclusively from verified primary sources including CISA advisories, vendor security bulletins, and leading threat intelligence publications. His analysis is built for security practitioners and business leaders who need actionable intelligence rather than vendor marketing. His original research includes the Digital Warfare 2026 Mid-Year Threat Pattern Report, an analysis of 28 confirmed threat incidents tracked between January and August 2026 that introduced three named security frameworks now used by enterprise security teams. The Zero-Day Priority Framework establishes a tiered patching classification system grounded in confirmed 2026 exploitation data showing that 73 percent of zero-days are weaponized within 72 hours of public disclosure. The Supply Chain Attack Taxonomy defines three distinct classes of supply chain compromise, each requiring different defensive controls and monitoring approaches. The AI Augmentation Classification documents three confirmed maturity levels of AI-assisted attack capability observed in real-world 2026 incidents, from AI-generated custom malware at Level One through fully autonomous ransomware operations at Level Three. Digital Warfare was founded in 2012 and serves corporations and governmental entities seeking rigorous security assessment and strategic security leadership from practitioners with genuine operational experience. Every member of the firm's elite team brings over 25 years of cybersecurity experience to every client engagement. Connect with James on LinkedIn or follow his threat intelligence updates at digitalwarfare.com/blog.
See Full Bio
Penetration Testing Ransomware Incident Response Threat Intelligence Zero-Day Vulnerability Research
social network icon social network icon
Share
Copyright © Digital Warfare. All rights reserved.
  • Home
  • About
  • Locations
  • Contact Us