The Apache Axis bug only bites where the Remote API (XML-RPC and SOAP) is switched on; 9.2.28 fixes it, Confluence 10 and Cloud are not affected, and turning the API off works without a restart.
Jira Service Management Data Center fixes high-severity access flaw
EditorialBy TrustList Editorial
CVE-2026-21609 (CVSS 7.1) lets a logged-in user reach resources they should not, and possibly run code; fixed in 10.3.27 and 11.3.13 of the self-managed edition.
- Australia
- Sydney, Australia
- Help Desk
- Cybersecurity
About Jira Service Management Data Center fixes high-severity access flaw
Jira Service Management Data Center fixes high-severity access flaw
17 November 2026: Atlassian has fixed CVE-2026-21609, a high-severity improper authorization flaw (CVSS 7.1) in Jira Service Management Data Center that lets an authenticated attacker reach resources or functions they should not, and could expose sensitive information or allow code to be run. The fixes are in 10.3.27 and 11.3.13. Atlassian does not report any exploitation, and the flaw came in through its bug bounty programme.
Not yet independently verified. Atlassian's public ticket gives the fixed versions but no publication date, and Atlassian has not said whether Jira Service Management Server 5.12 has a fix. Canada's Cyber Centre lists Server 5.12.16 to 5.12.42 as affected. We will update this when it can be confirmed, and remove this note.
Versions to move to
The flaw was introduced in 5.12.0, 10.3.0 and 11.3.0, and Atlassian's ticket lists every feature release from 5.12 through 11.3 as affected. Its advice is to upgrade to the latest release, or at least to:
- 10.3.27 or later on the 10.3 long-term support line;
- 11.3.13 or later on the 11.3 line.
Canada's Cyber Centre, in advisory AV26-1166 of 17 November, also lists Jira Service Management Server 5.12.16 to 5.12.42 as affected. Atlassian's ticket names no fix for the Server line.
The ticket describes the impact only in broad terms: unintended access that can expose resources or functionality, possibly giving an attacker sensitive information or even letting them execute arbitrary code. It does not say which endpoint or permission check is at fault, and it names no workaround, so upgrading is the only remedy it offers. Atlassian puts moving to the latest release first, with the two fixed builds as the minimum for customers who cannot go that far.
A flaw that needs a login, on a system full of logins
Because the attacker must be signed in, the realistic risk is from accounts that already exist: agents, portal customers on instances that allow self sign-up, and integration users. Service desks open to external customers are the ones where an unknown person can most easily get an account. Atlassian Cloud is not named in the ticket.
The ticket was created on 13 November and marked fixed on 17 November. It lists the affected feature releases as 5.12, 5.15, 5.16 and 5.17, every release from 10.0 to 10.7, and 11.0 to 11.3, and points to the release notes and the download archive for the fixed builds.
The rest of this week's Atlassian picture
The same week brought Java4Shell, a critical OpenJDK flaw that its finders showed reaching remote code execution in Jira and Confluence before login on some x86-64 servers. Self-managed Atlassian sites running on an affected JDK need both the application update and a Java update.
Atlassian is in our catalogue, and our service desk software category lists 17 products.
Sources
Categories & features
- Australia
- Sydney, Australia
- Help Desk
- Cybersecurity
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
The quantum software company, founded in 2017 with offices from Sydney to Oxford, says the round, A$415 million, was expanded twice and brings in AMD Ventures, EDGE Group and Australia's National Reconstruction Fund for its GPS-free navigation push.
Three employees of an India-based subcontractor accessed some Australian court hearing recordings outside agreed arrangements. Agencies were not told before VIQ entered administration, and the OAIC will take no further action.
Atlassian has deprecated the Forge modules jira:dashboardGadget and jira:dashboardBackgroundScript, to be removed on 17 May 2027. Apps must move to the new dashboards:widget and dashboards:backgroundScript modules.
After the Regulatory Reform Omnibus Bill 2026 passed, WGEA said Commonwealth public-sector employers with 100+ staff move to the 1 April–31 March reporting period from 2027, and employers with 500+ staff get a 12-month gap between target cycles.
From 1 October 2026 Australian merchants may no longer surcharge debit, prepaid or credit card payments, and interchange caps fall to 0.3% on consumer credit cards. Card networks and large acquirers must publish their fees from 30 October.
Torii, founded in 2017, tracks AI consumption down to the token; Freshworks expects the deal to close in its fourth fiscal quarter of 2026 and has not given a price.
Two people and two companies that place North Korean IT workers in remote contracts abroad are now on Australia's sanctions list. Paying them, even through a recruiter, can be a criminal offence.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More AustraliaThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.