Back to Newsroom

Threat intel6 min read

Atlassian fixes 318 flaws in Jira, Confluence and Bitbucket; Confluence 9.2 needs 9.2.28

Atlassian's November bulletin lists 266 high and 52 critical entries across its Data Center products. Confluence 9.2 users should go to 9.2.28 to close the separate Apache Axis flaw CVE-2026-90436.

4Tify Team

Atlassian's monthly security bulletin for November 2026, published on 17 November, lists 318 vulnerability entries fixed across its self-managed products: Jira Software, Jira Service Management, Confluence, Bitbucket, Bamboo, Crowd, Fisheye and Crucible. Of these, 266 are rated high and 52 are rated critical. Every critical entry sits in a third-party component bundled with the products.

The number looks alarming, but it needs some reading. The same CVE often appears once per product, so the count of distinct flaws is much lower than 318. Atlassian also says it rated everything in the monthly bulletin as a non-critical risk to customers, based on how its products actually use the affected libraries. Issues it considers an immediate danger get a separate critical advisory, and one of those landed this month as well.

What happened

The bulletin collects fixes that shipped in product releases over the previous month. It is a big jump from October, when the bulletin listed 176 entries (162 high and 14 critical).

Most of the critical scores come from widely used third-party libraries:

  • CVE-2026-4800 (CVSS 9.8): code execution in the Lodash JavaScript library, fixed in Confluence Data Center.
  • CVE-2026-76183 (CVSS 9.8): a session-management flaw in Apache Tomcat, listed for Jira Software, Jira Service Management, Confluence, Bamboo and Crowd.
  • CVE-2026-47890 (CVSS 9.8): code execution in a Spring Framework dependency used by Bamboo and Crowd.
  • CVE-2026-91403 (CVSS 9.1): compromised eMudhra certificates shipped inside the official Docker images for most of the product line.
  • CVE-2026-110879 (CVSS 9.8): a denial-of-service bug in Jackson Databind in Crucible Server.

Some of the more interesting entries are bugs in Atlassian's own code. They carry lower scores, but they are not library issues that may or may not be reachable:

  • Path traversal flaws that allow unintended file reads or writes: CVE-2026-21605 in Confluence (8.7), and CVE-2026-21590, CVE-2026-21606 and CVE-2026-21607 in Jira Software (all 8.7).
  • Stored cross-site scripting in Jira Core and Jira Software Data Center, CVE-2026-21603 (8.4) and CVE-2026-21602 (7.4). A malicious script stored in a page runs in the browser of whoever opens it.
  • An OS command injection, CVE-2026-21593 (7.7), in Crucible and Fisheye Data Center.

Jira Service Management also gets fixes for two code-execution bugs in the sharp image library (CVE-2026-114111 and CVE-2026-114112, both 8.9).

The Confluence 9.2 detail

There is a separate critical advisory, released on 9 November, for CVE-2026-90436. The bug is in Apache Axis 1.x, an end-of-life library that older Confluence versions use for the XML-RPC and SOAP Remote API. An unauthenticated attacker who can reach the instance can trigger it, and Atlassian rates it 9.3 under CVSS 4.0.

Only Confluence Data Center 9.x and earlier is affected, and only when the "Remote API (XML-RPC & SOAP)" option is turned on. That option has been off by default for new installations since Confluence 3.0 and was removed in 10.0. Confluence 10.x and Atlassian Cloud are not affected.

The catch is the version number. The November bulletin lists both 9.2.27 and 9.2.28 as fixed builds on the 9.2 LTS branch, but the CVE-2026-90436 advisory names 9.2.28 as the fix. If you are staying on 9.2, 9.2.27 is not enough.

At the time of writing, CVE-2026-90436 is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's own assessment in the CVE record lists no known exploitation.

Who is affected

Organisations running Atlassian Data Center or Server products on their own infrastructure. Cloud customers have nothing to do. The fixed builds listed in the bulletin are Data Center releases, so teams still on Server editions should check their branch carefully.

What to do now

  1. Make a list of every Atlassian installation with its edition and exact version, including test and staging copies and anything running from the Docker images.
  2. Upgrade to the recommended builds from Atlassian's November bulletin:
    • Jira Software Data Center: 11.3.13 or 10.3.27 (both LTS)
    • Jira Service Management Data Center: 11.3.13 LTS (10.3.27 is also listed)
    • Confluence Data Center: 10.2.20 LTS, or 9.2.28 if you must stay on 9.2
    • Bitbucket Data Center: 10.2.9 LTS
    • Bamboo Data Center: 12.1.13 LTS
    • Crowd Data Center: 7.2.6
    • Fisheye and Crucible: 4.9.16
  3. On Confluence 9.x, check whether the Remote API is enabled. If you cannot patch yet, Atlassian's mitigation is to clear the "Remote API (XML-RPC & SOAP)" box under General Configuration > Further Configuration. Browsing to /plugins/servlet/soap-axis1/confluenceservice-v2 should then return HTTP 403. Some scripts and add-ons that rely on the API may stop working, so test first.
  4. If a branch you run has no fix listed, move to a supported release rather than assuming the old one is safe.
  5. Keep internet exposure of these servers to a minimum, and check logs on any 9.x Confluence that had the Remote API switched on.

Monthly bulletins of this size are hard to triage by hand, because the same library bug shows up under several products and versions. Regular vulnerability scanning that maps the versions you actually run to published CVEs, which is a service our team provides, makes it easier to see which of the 318 entries apply to you and which servers are still behind.

NEWSLETTER

The week’s news,
every Friday.

A short email with what we published that week. You can unsubscribe from any of them.

FRIDAY DIGEST · SAMPLE4TIFY NEWSROOM

This week in security

  • 01Attackers exploit critical Cisco Expressway flaw to gain root on clustered nodes
  • 02SonicWall ends Gen 6 firewall patches, even for critical flaws
  • 03WhatsApp fixes three flaws, one possibly used to back up scam messages

+ 6 MORE IN THIS ISSUE · UNSUBSCRIBE IN ONE CLICK

ONE OFFER

More than one product?
Get one offer.

Tell us what you need to protect and your budget, monthly or yearly. We combine the products into one offer and one contract, sized to that budget, and we stay with you after it is signed.

Ask for an offer Just tell us how many assets you have and what you want to spend.
Atlassian November 2026 bulletin: 318 flaws fixed | 4Tify