Samsung’s August 2026 security update became widely available only during the final week of the month, with additional releases landing on August 31. That made the patch notably late for a monthly security release, while Samsung’s model-by-model and region-by-region distribution made it difficult for users to know when their device would be covered.
2
3
The update itself is significant: Samsung’s security bulletin addresses 56 vulnerabilities across eligible Galaxy phones and tablets. The package combines 38 Android fixes supplied through Google’s bulletin with 18 Samsung-specific fixes for Galaxy and One UI software. Eight of the Android issues are rated critical and 30 high priority.
4
6
8
Which Galaxy devices received the August patch?
The rollout was staged rather than simultaneous. Reports available by August 31 identified the following groups and locations:
Galaxy S26, S25 and S24
- Galaxy S26, S26+ and S26 Ultra: the rollout began in South Korea before expanding to additional countries.
1
11
- Galaxy S25, S25+ and S25 Ultra: updates were reported first in South Korea, with availability also reported in Europe.
11
13
- Galaxy S24, S24+ and S24 Ultra: the update was reported in Europe and other expanding markets.
1
11
- Galaxy S25 FE and S24 FE: early availability was reported in South Korea, with broader rollout expected to follow.
11
13
Firmware versions and update sizes varied by model and market, reinforcing that a Galaxy owner’s availability could differ from that of another owner using the same phone in a different country.
34
36
Galaxy S23 and S22
The Galaxy S23, S23+ and S23 Ultra began receiving the patch in South Korea on August 31. The Galaxy S22 series was also reported as part of that Korean rollout on the final day of the month.
2
3
33
Those releases were important because they showed the update reaching older flagship generations only as August was ending, rather than at the start of the monthly cycle.
Galaxy Z Fold and Z Flip devices
Samsung’s newest foldables were among the earliest devices associated with the August rollout. Reports identified the Galaxy Z Fold8 and Z Fold8 Ultra from mid-August, with the Galaxy Z Flip8 also listed as receiving the patch.
5
13
Additional reporting identified updates for earlier foldables, including the Galaxy Z Fold7, Z Flip7, Z Fold6 and Z Flip6, while other reports also listed the Z Fold5, Z Flip5 and older foldable generations in staged distributions.
38
41
43
Galaxy A-series phones
The A-series rollout was selective. Reports identified devices such as the Galaxy A56 and other A-series models, but the available evidence does not establish a single complete list showing that every eligible A-series variant had received the patch by August 31.
36
41
42
For A-series owners, the practical conclusion is that eligibility and timing could vary substantially by model, carrier and country.
Galaxy Tab S10 tablets
Reporting listed Galaxy Tab S10 models among the devices receiving the August update, while a separate update tracker specifically identified the Galaxy Tab S10 FE and Tab S10 FE+ in South Korea.
42
44
Because the reports do not provide a consistent, complete model-and-region matrix for every Tab S10 variant, it is safer to treat the tablet rollout as staged rather than assume that the entire range was updated worldwide by August 31.
What the 56 fixes include
The patch has two parts:
- 38 Google Android fixes: eight were classified as critical and 30 as high priority.
4
6
- 18 Samsung-specific fixes: these address vulnerabilities in Samsung’s own software and One UI components.
6
8
The number is therefore 56 total vulnerabilities, rather than an imprecise “nearly 60.” Some reporting notes that a Google fix had already appeared in an earlier update or did not affect Galaxy devices, so the detailed applicability of individual Android fixes can vary by device and software version.
8
12
The presence of eight critical Android issues explains why users were encouraged to install the update when it became available. However, the sources reviewed do not establish that these particular eight vulnerabilities were actively exploited zero-days. The critical rating should not be presented as proof of an ongoing attack campaign.
4
6
Why Samsung was criticized for the delay
Samsung published details of the August Security Maintenance Release early in the month, but broader device deployment did not begin until late August. One contemporaneous tracker described the wait as almost 25 days, while additional models were still being added on August 31.
2
3
6
The criticism was less about a single missing release date than about uncertainty. Samsung’s update process can differ according to:
- device model and generation;
- country or sales region;
- carrier firmware;
- chipset and software version; and
- staged release channels.
Samsung’s own security documentation says that release timing can vary by device, model and service version.
20
That structure makes it difficult for users to infer anything from another owner’s update notification: a Galaxy S24 owner in Europe, for example, could receive the patch before a Galaxy S23 owner in another market, even though both devices are eligible for monthly security support.
Could One UI 9 beta testing have contributed?
One UI 9.0 development was happening at the same time as the delayed security rollout. One UI 9 is Samsung’s Android 17-based software, and the Galaxy S26 beta program received multiple builds during August, including beta releases containing the August security patch.
49
53
56
Samsung also confirmed that Google Play System updates were temporarily paused for devices running beta versions of One UI, in coordination with Google. Samsung said critical Google security fixes had already been included in the beta build, according to reporting on the pause.
46
47
48
That overlap makes concurrent beta testing a plausible factor in the release-management picture, but it is not a confirmed explanation for the late August security rollout. Samsung did not publicly attribute the delay to One UI 9 or Android 17 work in the evidence reviewed.
What Galaxy owners should do
Check the phone or tablet directly rather than relying on rollout reports from another market:
- Open Settings.
- Select Software update.
- Tap Download and install.
- If the August 2026 patch is not yet available, check again later as Samsung continues the staged release.
1
2
10
Samsung’s normal installation guidance is to begin with at least 50% battery or keep the device connected to a charger. Using Wi‑Fi and backing up important data before a substantial software update are also sensible precautions.
The main takeaway is straightforward: the August patch was important and broad, but its late, fragmented arrival meant that “Samsung released the update” did not mean every eligible Galaxy device received it at the same time.