Elements Connect

2026 11 04 - P2 Security issue (Unauthorized data residency migration)

A security vulnerability was recently identified and fixed in Elements Connect. Here are the details about the issue, its impact and the analysis and actions taken.

Nature of the issue

Some operations of the Elements Connect backend are meant to be called only by Atlassian or by the app itself, for example during the installation of the app or during a data residency migration of the app's data to another region. These operations checked that a request genuinely came from Elements Connect on the Jira site, but not whether it had been made on behalf of a user. As a result, any user logged in to the Jira site, including a Jira Service Management portal customer, could call them and, in particular, trigger a data residency migration of the Elements Connect data of that site.

This vulnerability has been rated High according to the scale published by the Common Vulnerability Scoring System (CVSS). It was identified by our own team during an internal security review on , and was also reported by a security researcher through our Bug Bounty Program on . The fix was deployed on .

Impact

Exploiting this vulnerability required being logged in to the Jira site: a regular Jira user or a Jira Service Management customer was enough.

  • Availability: by triggering a data residency migration, a user could make Elements Connect unusable for every user of the Jira site, and cause the Elements Connect data of the site to be moved to another region, then removed from its original region.

  • No data was exposed. The issue did not allow reading Elements Connect configuration, field values, Jira data, or the data of the external datasources connected to Elements Connect.

  • No Jira data could be modified. Only the Elements Connect data of the site and the app's usage statistics for that site could be affected.

We have not identified any exploitation of this vulnerability: the only calls were made by the security researcher, on their own test site. No customer was affected.

Analysis and actions taken

The operations reserved to Atlassian and to the app now reject any request made on behalf of a user, whoever that user is. This check was applied to all of these operations, not only to the data residency migration.

In addition, an internal mechanism that could relay requests from the app's user interface to these operations was removed.

Automated tests were added to cover these checks, and we conducted non-regression tests to confirm the resolution of the issue. The fixed version was released on .

Conclusion

This fix is now live and ensures that Elements Connect Cloud remains secure.

No action is required from customers, but we encourage all users to keep their applications up to date and report any suspicious behavior.

We want you to know that we take this issue very seriously. We are conducting a thorough review of our internal processes to ensure this does not occur again for our customers.

If you have any questions, please feel free to raise a support request at support.elements-apps.com referencing "ECC-5203".