Security readout for executives and security teams
Plain-English summary
A flaw in Atlassian Sourcetree can let a logged-in attacker run code after a user interacts with malicious content or workflow. Successful exploitation could compromise source code, credentials, and the developer workstation. The supplied advisory rates it High at CVSS 7.1.
Executive priority
Treat as a high-priority developer-workstation update. Schedule prompt remediation, especially where Sourcetree users hold valuable repository or deployment credentials. Emergency incident response is not justified solely by the supplied evidence because active exploitation is unconfirmed.
Technical view
CVE-2026-21575 is a CWE-94 code-injection vulnerability affecting Sourcetree for Mac and Windows according to the advisory narrative. It requires network access, low privileges, high attack complexity, and user interaction. Successful exploitation can severely affect confidentiality, integrity, and availability.
Likely exposure
Prioritize developer endpoints running Sourcetree 3.4.11 or 3.4.12. The narrative identifies both Mac and Windows, but the structured affected-version data is inconsistent about 3.4.13. Confirm installed versions and supported fixed releases against Atlassian guidance.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as being in KEV. Exploitation requires an authenticated attacker and user interaction, reducing immediacy but not the potential workstation and source-code impact.
Researcher notes
The CVSS 3.0 vector is AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H. Atlassian says the issue was introduced in 3.4.11 and fixed in 3.4.13 or later. However, the bundle’s structured affected entry also includes versions from 3.4.13, creating an unresolved boundary conflict.
Mitigation direction
- Upgrade Sourcetree for Mac and Windows to the latest available release.
- If latest is unsuitable, use an Atlassian-supported fixed version at or above 3.4.13.
- Prioritize systems handling sensitive repositories, signing credentials, tokens, or production access.
- Review Atlassian guidance before treating 3.4.13 as fixed because supplied version data conflicts.
Validation and detection
- Inventory Sourcetree installations across managed Mac and Windows developer endpoints.
- Identify installations running versions 3.4.11 or 3.4.12.
- Confirm the installed version after upgrading and compare it with current Atlassian guidance.
- Review endpoint telemetry for unexpected processes or repository-access anomalies involving affected systems.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-21575 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H1.25.9atlassianVulnerability scoring details
Base CVSS 3.0 score
7.1HighVector: CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://confluence.atlassian.com/pages/viewpage.action?pageId=1821999345CVE reference, atlassian
- https://jira.atlassian.com/browse/SRCTREE-8275CVE reference, atlassian
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.