Atlassian November Bulletin Fixes 318 Flaws, Six Rated Critical

Atlassian's November security bulletin fixes 318 flaws across Bamboo, Bitbucket, Confluence, Crowd, Fisheye/Crucible and Jira; no exploitation is confirmed.
Table of Contents
    Add a header to begin generating the table of contents

    Atlassian’s monthly security bulletin, published November 17, fixes 318 flaws across its Data Center and Server products. Six of the notable vulnerabilities are rated critical, and no exploitation has been confirmed for any of them.

    What Atlassian’s 318-Flaw Bulletin Covers

    Atlassian’s “Security Bulletin – November 17 2026” reports “266 high-severity vulnerabilities and 52 critical-severity third-party vulnerabilities,” and Canada’s Cyber Centre tracked it as advisory AV26-1166. Per the vendor bulletin, the fixes break down into 266 high-risk bugs and 52 critical third-party flaws. They span Bamboo, Bitbucket, Confluence, Crowd, Fisheye/Crucible and Jira.

    An analysis of the bulletin tallies 11 notable CVEs, six critical and five high severity. Jira and Confluence are also among the products that researchers named as remote code execution targets for the Java4Shell flaw, CVE-2026-114938, which made the same week’s Java patches relevant to Atlassian administrators.

    Six Critical CVEs With CVSS Scores of 9.1 and 9.8

    Five of the critical flaws score 9.8:

    • CVE-2026-47890 (CWE-93)
    • CVE-2026-47884 (CWE-22)
    • CVE-2026-59313 (CWE-93)
    • CVE-2026-86248 (CWE-287)
    • CVE-2026-76183 (CWE-289)

    CVE-2026-91403 scores 9.1. The weakness types cover a range of problems, from path traversal (CWE-22) and improper authentication (CWE-287) to neutralization failures (CWE-93).

    Which Atlassian Products Hold the Critical CVEs

    The critical examples break down by product. Bamboo’s CVE-2026-47884 and CVE-2026-47890 are Spring framework issues scored 9.8. Confluence has CVE-2026-4800, a lodash flaw scored 9.8, and CVE-2026-91403, scored 9.1, which relates to an eMudhra certificate failure. Jira’s CVE-2026-76183 and CVE-2026-86248 are Tomcat authentication failures scored 9.8. A separate CVE-2026-90436 affects Apache Axis 1.x, which Confluence’s XML-RPC and SOAP APIs use.

    One analysis headlined CVE-2026-4800 as the remote code execution flaw, which is consistent with the vendor table.

    Atlassian Says Many Third-Party Ratings Overstate Its Risk

    For most critical third-party findings, Atlassian states that “Atlassian’s application of this dependency presents a lower, non-critical assessed risk.” The raw CVSS ratings therefore overstate the risk in many cases. The third-party components named are Apache Tomcat (authentication and denial of service), Spring Framework (expression injection and misconfigurations), Bouncy Castle (cryptographic failures), Netty (denial of service and authorization), Jackson (deserialization and denial of service) and lodash.

    Additional High-Severity Fixes in the Atlassian Bulletin

    Two further vulnerabilities fall just below the critical band. CVE-2026-21600 scores 8.9 and CVE-2026-21598 scores 8.7. Both are fixed in versions 13.0.1, 12.1.13 and 10.2.26.

    Fixed Versions for Each Atlassian Data Center Product

    The fixed versions are Bamboo Data Center 13.0.1 (LTS 12.1.13 and 10.2.26), Bitbucket Data Center 10.5.2 (10.2.9 and 9.4.27), Confluence Data Center 11.0.1 (10.2.20 and 9.2.27 to 9.2.28), and Jira Software and Jira Service Management Data Center at the latest or LTS releases 11.3.13 and 10.3.27. Crowd Data Center is fixed in 7.2.6 and Fisheye/Crucible in 4.9.16. Atlassian recommends patching to the latest version or one of the fixed versions for each product.

    Where Atlassian Servers Hold Sensitive Material

    Atlassian Data Center and Server hosts store source code, build jobs and wikis. Stolen cloud keys are a risk on unpatched systems, which is why flaws in these products draw attention even without confirmed attacks.

    What Administrators Need to Do

    The response is to update Data Center and Server hosts to the fixed builds named in the bulletin. No exploitation has been confirmed for any of the flaws, but the number of critical entries and their authentication and path-traversal weakness types make the update a priority for teams running self-hosted Atlassian software.

    The overlap with Java4Shell creates a second reason to check these systems. Jira and Confluence are on Calif’s list of products where it demonstrated pre-authentication code execution in default configurations, so administrators of those two products have both Atlassian’s bulletin and the Java runtime fixes to apply.

    Related Posts