Security readout for executives and security teams
Plain-English summary
SourceTree for Windows could let a malicious Mercurial repository tag name cause code execution when that tag is deleted. The attacker needs permission to create a tag in a Mercurial repository already linked in SourceTree. This is most relevant to developer workstations using older SourceTree versions with shared Mercurial repositories.
Executive priority
Prioritize remediation for developer workstations because successful exploitation can execute code on endpoints that may hold source code and credentials. Scope is narrower than an internet-facing server issue, but impact is serious where Mercurial collaboration is still active.
Technical view
CVE-2018-5226 is an argument injection issue in SourceTree for Windows before 2.5.5.0. The injection path is a Mercurial repository tag name involved in tag deletion. Atlassian’s CVE description states that an attacker able to create such a tag can gain code execution on the affected system.
Likely exposure
Exposure is likely limited to Windows systems running SourceTree before 2.5.5.0 and using linked Mercurial repositories where another user can create tags. Git-only use is not described as affected in the provided sources.
Exploitation context
The provided sources do not state active exploitation, and the CVE is not listed as KEV. Exploitation requires repository-level tag creation rights and a vulnerable SourceTree for Windows workflow involving deletion of that Mercurial tag.
Researcher notes
The source bundle provides no CVSS vector, CWE, exploit details, or in-the-wild evidence. Analysis should stay focused on the documented argument injection in Mercurial tag deletion and the stated affected boundary: SourceTree for Windows versions before 2.5.5.0.
Mitigation direction
- Upgrade SourceTree for Windows to 2.5.5.0 or later.
- Restrict Mercurial tag creation to trusted maintainers.
- Review shared Mercurial repositories linked in SourceTree.
- Check Atlassian guidance for any additional vendor recommendations.
Validation and detection
- Inventory SourceTree for Windows versions on developer endpoints.
- Identify endpoints using SourceTree with linked Mercurial repositories.
- Review repository permissions for users allowed to create tags.
- Check security telemetry for unusual SourceTree or Mercurial child processes.
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.
Execution 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-2018-5226 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/SRCTREEWIN-8509CVE reference · x_refsource_CONFIRM
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.