SourcetreeApplication · Atlassian
CVE-2018-5226
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere was an argument injection vulnerability in Sourcetree for Windows via Mercurial repository tag name that is going to be deleted. An attacker with permission to create a tag on a Mercurial repository linked in Sourcetree for Windows is able to exploit this issue to gain code execution on the system. All versions of Sourcetree for Windows before 2.5.5.0 are affected by this vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSourcetree for Windows versions before 2.5.5.0 contain an argument injection vulnerability when processing Mercurial repository tag names during deletion operations. An attacker with permission to create tags in a linked Mercurial repository can inject malicious arguments through the tag name, resulting in arbitrary code execution on the victim's system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SourcetreeApplication
< 2.5.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Sourcetree for Windows is installedCheck for Sourcetree installation on the Windows system, typically in Program Files or the user's AppData directory. Look for SourceTree.exe or check Add/Remove Programs.Affected if Sourcetree for Windows is found on the system
-
Determine the installed Sourcetree versionRight-click on SourceTree.exe, select Properties, then look at the Details tab for the Product Version, or use the application's About dialog.Affected if The version number is lower than 2.5.5.0
-
Check if Mercurial repositories are configuredOpen Sourcetree and look at the sidebar or repository list to see if any Mercurial (Hg) repositories are linked or have been cloned.Affected if One or more Mercurial repositories are present in Sourcetree
-
Confirm tag deletion functionality is accessibleIn Sourcetree, right-click on a linked Mercurial repository, navigate to the Tags view, and verify the ability to delete tags is available.Affected if User can access and delete tags in a Mercurial repository through Sourcetree
A user is affected only if Sourcetree for Windows version is below 2.5.5.0 AND Mercurial repositories are linked with tag deletion capability accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.5.5.0
Upgrade Sourcetree for Windows to version 2.5.5.0 or later. Until patched, restrict repository write permissions to trusted users only.
Fix this in Sourcetree
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-5226 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data