# CVE-2026-21575: Code injection in Sourcetree for Mac

> An authenticated attacker can execute arbitrary code on Sourcetree for Mac and Windows, requiring user interaction to trigger the vulnerability.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-rrh5-678c-6wj4

## What is CVE-2026-21575?

CVE-2026-21575 is a high-severity code injection vulnerability in Atlassian Sourcetree for Mac, published on 21 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

This High severity RCE (Remote Code Execution) vulnerability was introduced in version 3.4.11 of Sourcetree for Mac and Sourcetree for Windows. 
	
	This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 7.1, allows an authenticated attacker to execute arbitrary code which has high impact to confidentiality, high impact to integrity, high impact to availability, and requires user interaction. 
	
	Atlassian recommends that Sourcetree for Mac and Sourcetree for Windows customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:
		
		* Sourcetree for Mac and Sourcetree for Windows 3.4: Upgrade to a release greater than or equal to 3.4.13
		
		
	
	See the release notes (https://www.sourcetreeapp.com/download-archives). You can download the latest version of Sourcetree for Mac and Sourcetree for Windows from the download center (https://www.sourcetreeapp.com/download-archives). 
	
	This vulnerability was reported via our Bug Bounty program.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-21575?

It affects 1 product.


Products: Atlassian Sourcetree.

## How do I fix CVE-2026-21575?

No fix has been published for CVE-2026-21575 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-21575 being exploited?

There is no known exploitation of CVE-2026-21575 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Sourcetree for Mac

- [CVE-2018-13385](https://insights.sbomify.com/CVE-2018-13385/): Command injection in Sourcetree for macOS (critical 9.8)
- [CVE-2017-8768](https://insights.sbomify.com/CVE-2017-8768/): Command injection in n/a (critical 9.8)
- [CVE-2024-21697](https://insights.sbomify.com/CVE-2024-21697/): Code injection in Sourcetree for Mac (high 8.8)
- [CVE-2019-11582](https://insights.sbomify.com/CVE-2019-11582/): Command injection in Sourcetree for Windows (high 8.8)
- [CVE-2018-20234](https://insights.sbomify.com/CVE-2018-20234/): Command injection in Sourcetree for macOS (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-21575 and fix it if it is affected.

What it is: CVE-2026-21575 is a high-severity code injection vulnerability in Atlassian Sourcetree for Mac, published on 21 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-21575 in the wild and no public exploit code.

Affected product: Atlassian Sourcetree for Mac. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-21575/ (Markdown: https://insights.sbomify.com/CVE-2026-21575/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-21575
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21575
- OSV: https://osv.dev/vulnerability/CVE-2026-21575

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-21575/
Summaries are generated and may contain mistakes; the official description above is the record.