What Atlassian released
Atlassian published its November 2026 security bulletin on 17 November. It lists 266 high-severity and 52 critical-severity vulnerabilities, and nearly all of them come from third-party components bundled inside the products. The bulletin covers Jira, Jira Service Management, Confluence, Bitbucket, Bamboo, Crowd, Fisheye and Crucible. UC Today put the total at 318 fixes. GBHackers points out that some CVEs appear under more than one product, so 318 is a count of entries and overstates the number of distinct flaws.
For service desk owners, the Jira Service Management (JSM) section is the part to read. Every self-hosted release from 10.2.0 up to 11.3.12 is listed as affected, and the fixed versions are 11.3.13 LTS (Atlassian's recommendation) and 10.3.27 LTS. Atlassian labels both builds as Data Center only. The critical JSM entries include two Apache Tomcat authentication and session flaws scored 9.8, an HTTP request smuggling issue in Tomcat scored 9.1, and CVE-2026-91403, a 9.1-rated issue involving compromised eMudhra certificates in the Docker images. GBHackers reports that CVE-2026-91403 reaches all eight product families. The JSM table also lists two remote code execution entries in the sharp image library and two path traversal flaws that allow arbitrary reads and writes.
How to read the severity scores
Atlassian's position is that none of these CVEs is critical inside its own products. The bulletin says: "CVEs reported in monthly Security Bulletins have been assessed as presenting a non-critical risk to Atlassian customers." A 9.8 score belongs to the Tomcat or Spring component on its own. Atlassian has judged that the way JSM uses the component lowers the real exposure.
We'd accept Atlassian's assessment as a reasonable starting point for scheduling. We wouldn't treat it as a reason to wait. A vendor's risk rating assumes a standard deployment, and many NZ instances aren't standard. Some sit behind a reverse proxy that was configured years ago. Some run Marketplace apps that call the same libraries in different ways, and some expose the customer portal to the internet so clients can log tickets. Request smuggling and session handling flaws matter most in exactly those setups. The gap between "non-critical in the default configuration" and "non-critical in your configuration" is the part your team has to close for itself.
Why the service desk platform deserves faster patching
A service management platform holds more than tickets. JSM instances usually store asset records, change approvals, integration tokens for monitoring and identity tools, and attachments that customers upload, including screenshots, logs and sometimes credentials pasted in by mistake. Anyone who gets into the platform also gets a map of your environment and a trusted channel for talking to your staff. Earlier this month we covered fake IT support calls on Teams, and an attacker holding a working JSM account could make that kind of social engineering far more convincing.
Organisations also tend to put the service desk platform behind the systems it manages in the patching queue. The platform gets treated as an internal tool, and upgrades wait for a quiet period that never arrives. An ITIL 4 change practice should push the other way, because the service desk is the record you rely on during an incident. If you're reviewing how changes like this one get classified and approved, our ITIL 4 framework page explains how we approach standard and normal changes.
The Data Center deadline sits behind this patch
This bulletin also lands partway through Atlassian's Data Center end-of-life schedule. New customers lost the ability to buy Data Center subscriptions on 30 March 2026. Existing customers can't buy new subscriptions, expansions or upgrades after 30 March 2028. Jira Software, JSM, Confluence and Crowd Data Center reach end of life on 28 March 2029, when the products switch to read-only. Atlassian says it'll keep shipping security fixes for critical vulnerabilities until that date, and it advises against leaving a read-only instance connected to the internet. Bitbucket and Bamboo Data Center are excluded from the end-of-life plan.
NZ firms that self-host JSM therefore have about 28 months of patch cycles left. Each cycle like this one costs testing time, a maintenance window and checks on Marketplace app compatibility. Teams on older non-LTS builds such as 10.5 or 11.1 will find the jump to 11.3.13 bigger than a routine patch. Atlassian says unsupported versions don't receive these fixes. Those teams have to make the upgrade effort anyway, so it's a sensible time to cost the Cloud migration and the upgrade side by side. The bulletin doesn't cover Atlassian Cloud and says nothing about whether Cloud tenants were exposed, so Cloud customers have nothing to install from this release.
Some organisations will have good reasons to stay self-hosted until 2029, or to ask Atlassian for the extended maintenance it offers by exception. Data residency obligations, heavily customised workflows and integrations with on-premises systems are common examples in NZ. Those reasons should be written down and tested against what Cloud offers now. They shouldn't be assumed from a decision made when Server licences were still on sale.
Next steps for NZ IT and operations leaders
- Confirm the exact JSM, Jira and Confluence versions running in production and test, and check whether each instance runs from Atlassian's Docker images. CVE-2026-91403 affects those images directly.
- Schedule the upgrade to JSM 11.3.13 LTS or 10.3.27 LTS as a normal change with a short test cycle. Don't let it wait for the next quarterly window. If the customer portal or any login page is reachable from the internet, move it to the front of the queue.
- Check every Marketplace app against the target version before the maintenance window. App incompatibility is the most common reason we see Atlassian upgrades get rolled back.
- Review the reverse proxy and load balancer configuration in front of the instance. The Tomcat request smuggling entry is most relevant where a proxy and Tomcat parse requests differently.
- If an MSP hosts or patches your Atlassian stack, ask for the version they'll deploy, the date, and confirmation that the Docker base images were rebuilt.
- Use this upgrade to get a written comparison of staying on Data Center to March 2029 against moving to Cloud. Include licence cost, data residency, app replacements and staff time per patch cycle. Our digital transformation team can help structure that comparison if you don't have the internal capacity.
Sources
Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.
Get my free assessment How we help