Atlassian updates: prove the change before closing it
Atlassian’s November bulletin calls for decisions by product and support branch. Learn how to define an acceptable update and establish the outcome in the service actually running.
Читати португальськоюBy Pentesty
Start with the applicable advisory
The November 17, 2026 bulletin lists 266 high-severity entries and 52 critical entries in third-party components. Atlassian assesses the risk of these components, as used in its products, as non-critical for customers. Identifiers can recur across products, so the count does not represent 318 distinct CVEs or mean that every installation is exposed to every entry.
That assessment belongs to the monthly bulletin. Separate critical advisories have their own conditions and priorities, which must inform the enterprise decision. For an actual installation, record the product, edition, release branch, running version and applicable advisories; the severity of an isolated library does not establish that relationship.
Choose the destination by product and branch
The fixed builds are a snapshot dated November 17. The Confluence 10.2.20 notes record a November 3 release, and the Jira Software 11.3.13 notes give November 5; publication of the bulletin came later.
The monthly Confluence 9.2.27 to 9.2.28 range needs to be checked against the separate CVE-2026-90436 advisory: Atlassian assesses this issue as critical, and the XML-RPC/SOAP Remote API must be enabled for an instance to be vulnerable. That advisory lists 9.2.28 as fixed; choosing 9.2.27 solely from the monthly bulletin does not meet this criterion. Confluence 10.x and later are unaffected by this specific issue.
- Jira Software: 10.3.27 LTS or 11.3.13 LTS, both recommended in the bulletin.
- Jira Service Management: 11.3.13 LTS or 10.3.27 LTS; only 11.3.13 carries the recommended label.
- Confluence: 11.0.1, recommended 10.2.20 LTS, or the 9.2.27 to 9.2.28 LTS range.
- Bitbucket: 10.5.2, recommended 10.2.9 LTS, or 9.4.27 LTS. All builds listed here are Data Center Only.
Plan downtime before the maintenance window
The Bitbucket 10.2 notes require a full cluster shutdown and restart when moving from 10.2.0, 10.2.1 or 10.2.2 to 10.2.3 or later. From 10.2.3 to another later build within 10.2, they allow a rolling restart. The starting state changes the procedure, even when the selected destination is 10.2.9.
For Confluence 10.2.20, the vendor recommends backing up the confluence-home directory and database before upgrading. Pentesty adds verifying recovery and assigning rollback ownership as operational acceptance criteria. Also test authentication and essential integrations, with expected results recorded before the change; a process starting does not by itself demonstrate that business functions remain available.
Close the change against the running service
The exposure window connects disclosure to effective remediation. Validating the live JVM for Java4Shell illustrates why installing files and establishing which process is running are different checks.
If a node still runs the previous version, record an incomplete update and identify which traffic it continues to serve. If an integration fails, retain the test evidence and apply the agreed rollback criterion; a successful login alone does not validate workflows that depend on automation, plugins or background processing across the deployment.
Pentesty proposes attaching reproducible evidence to acceptance. Record who validated the change, when and on which instance; keep outstanding work linked to owners and deadlines, without treating a completed update as a guarantee of security.
- Before: retain each node’s version, applicable advisory, approved build and rollback criteria, with restricted access to operational records.
- After: establish the running version on every node and the service’s functional test results, including authentication and priority integrations.
- For an exception: document remaining exposure, the official guidance considered, its owner and the next review.
Frequently asked questions
Are all 318 entries critical?
The bulletin counts 266 high-severity and 52 critical third-party entries, with effective risk assessed as non-critical by Atlassian. Separate advisories require their own assessment.
Does one version cover every product?
Choose by product, edition, branch and advisory. The targets cited here are Data Center builds; this analysis does not establish equivalent fixes for Cloud or unsupported Server.
Does Confluence 9.2.27 resolve the separate advisory?
For CVE-2026-90436, Atlassian lists 9.2.28. The monthly 9.2.27 to 9.2.28 range must be checked against that specific requirement.
When can the enterprise close the ticket?
When it establishes the approved build is running, completes the defined tests and addresses exceptions. This is Pentesty’s acceptance recommendation, adjustable to the environment.
Sources and references
- Atlassian: November 17 bulletin
- Confluence 10.2.20: release notes
- Jira Software 11.3.13: release notes
- Jira Software 10.3.27: release notes
- Jira Service Management 11.3.13: release notes
- Jira Service Management 10.3.27: release notes
- Bitbucket 10.2: notes and restart constraint
- Bitbucket 9.4: release notes
- Bitbucket 10.5: release notes
- Atlassian: separate CVE-2026-90436 advisory
- CISO Advisor: news report consulted
- Cyber Security News: news report consulted
Original Pentesty analysis, published November 18, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.