
Galaxy Watch user reports burn overnight; this isn’t the first time
One Galaxy Watch 5 Pro user reported burns and blisters on their skin after sleeping with their watch under what can only be considered normal operation.
via 9to5GoogleReported by 4 outlets
The story so far
AI summary of the reporting below · Updated · How we work
A Samsung Galaxy Watch 5 Pro user reported suffering severe skin burns and blisters after wearing the smartwatch to sleep on October 22, 2026. According to a post shared on Reddit by user u/ksima_03, the three-year-old wearable went to bed fully charged but was completely drained and unresponsive by morning. [2][3][4]
The rapid overnight discharge of the watch's 590mAh lithium-ion battery likely generated substantial heat, preventing the device from powering back on. While common wearable skin reactions typically stem from contact dermatitis, photos shared by the user showed fluid-filled blisters and marks that resemble burns. Outlets noted similar isolated overheating reports across other Samsung devices, including the Galaxy Watch 7, Watch 8, and Ultra models. [2][3]
The incident has revived lingering consumer anxieties regarding battery safety and overnight sleep tracking. Samsung has not commented on the matter, though analysts note such hardware failures remain rare across millions of active devices. [3][4]

One Galaxy Watch 5 Pro user reported burns and blisters on their skin after sleeping with their watch under what can only be considered normal operation.
via 9to5Google
A Galaxy Watch user reported a painful blister and skin burn after the device overheated while they were resting.
via Android CentralSome Samsung Galaxy Watch users have reported finding rather severe-looking burns on their wrists after wearing their Galaxy Watches overnight.
via Android Police
A user on r/samsunggalaxy has alleged that their Samsung Galaxy Watch 5 Pro left severe burn marks on their wrist. The attached pictures definitely show marks that resemble second-degree burns. Samsung has yet to comment on the issue.
via Notebookcheck