CVE-2026-21575

HIGHNVD 8.08.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.0 under NVD CVSS v3. EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-21) is not newer than that change (2026-08-10), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
8.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.0Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
36
EG Risk 36/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity80% × 45%
Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.

EG Severity
8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 21, 2026

Last Modified

August 10, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
Fix named in the CVE record.
Web page

Security Bulletin - July 21 2026 | Atlassian Support | Atlassian Documentation

https://confluence.atlassian.com/pages/viewpage.action?pageId=1821999345

Vendor Advisories for CVE-2026-21575(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 243 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 144 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-18 03:56 UTCEG score recompute
  3. 2026-10-17 17:23 UTCEG score recompute
  4. 2026-10-17 17:23 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  5. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  7. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-10-12 16:23 UTCEG score recompute
  12. 2026-10-11 20:04 UTCEG score recompute
  13. 2026-10-11 17:17 UTCEG score recompute
  14. 2026-10-11 14:49 UTCEG score recompute
  15. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  21. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-10-04 14:49 UTCEG score recompute
  24. 2026-10-04 14:49 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  25. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Show 74 more
  1. 2026-10-01 07:29 UTCEG score recompute
  2. 2026-10-01 07:29 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  6. 2026-09-28 06:09 UTCEG score recompute
  7. 2026-09-28 06:09 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  8. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  9. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  10. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-09-24 03:23 UTCEG score recompute
  13. 2026-09-24 03:23 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  14. 2026-09-23 01:25 UTCEG score recompute
  15. 2026-09-23 01:25 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  16. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-09-20 05:57 UTCEG score recompute
  18. 2026-09-20 05:57 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  19. 2026-09-19 00:21 UTCEG score recompute
  20. 2026-09-19 00:20 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  21. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-09-18 03:49 UTCEG score recompute
  23. 2026-09-18 03:49 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  24. 2026-09-17 05:06 UTCEG score recompute
  25. 2026-09-17 05:06 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  26. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  27. 2026-09-16 12:38 UTCEG score recompute
  28. 2026-09-16 12:38 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  29. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  30. 2026-09-14 04:00 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  31. 2026-09-13 17:01 UTCEG score recompute
  32. 2026-09-13 17:01 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  33. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  34. 2026-09-13 06:00 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  35. 2026-09-12 19:01 UTCEG score recompute
  36. 2026-09-12 19:01 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  37. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  38. 2026-09-12 07:30 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  39. 2026-09-11 20:31 UTCEG score recompute
  40. 2026-09-11 20:31 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  41. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  42. 2026-09-11 09:03 UTCEG score recompute
  43. 2026-09-11 09:03 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  44. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  45. 2026-09-09 11:29 UTCEG score recompute
  46. 2026-09-09 11:29 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  47. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  48. 2026-09-07 22:36 UTCEG score recompute
  49. 2026-09-07 22:36 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  50. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  51. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  52. 2026-09-06 10:57 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  53. 2026-09-05 19:54 UTCEG score recompute
  54. 2026-09-05 19:54 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  55. 2026-09-05 08:55 UTCEG score recompute
  56. 2026-09-05 08:55 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  57. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  59. 2026-09-02 00:57 UTCEG score recompute
  60. 2026-09-02 00:57 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  61. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  62. 2026-08-31 00:15 UTCEG score recompute
  63. 2026-08-31 00:15 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  64. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  65. 2026-08-30 13:15 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  66. 2026-08-30 02:15 UTCEG score recompute
  67. 2026-08-30 02:15 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  68. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  69. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  70. 2026-08-27 22:19 UTCEG score recompute
  71. 2026-08-27 22:19 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  72. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  73. 2026-08-27 11:20 UTCGHSA enrichmentGHSA-rrh5-678c-6wj4 · GitHub severity HIGH · GitHub CVSS 7.1
  74. 2026-08-26 22:08 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-21575?
CVE-2026-21575 is a high-severity vulnerability; its CVE record was published on July 21, 2026. 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…
When was the CVE record for CVE-2026-21575 published?
The CVE record for CVE-2026-21575 was published on July 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 10, 2026; the record at its source may have been updated since.
Is CVE-2026-21575 actively exploited?
CVE-2026-21575 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-21575?
CVE-2026-21575 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-21575?
The CVE record for CVE-2026-21575 names the fix: "…Upgrade to a release greater than or equal to 3.4.13". The vendor advisories EchelonGraph has for CVE-2026-21575 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-21575

Explore →

Is Your Infrastructure Affected by CVE-2026-21575?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.