Security1 publisher2 min readPublished
Skullcandy's Dime 3 earbuds pair silently with any Bluetooth device in range
CERT/CC says the Airoha SDK flaw CVE-2025-20701 was fixed upstream on August 4, 2025 and in Skullcandy firmware 1.0.0.30, but units already sold on 1.0.0.28 have no update path, so the fix only reaches new stock.
The Watch · Security desk

What happened
- CERT/CC says Skullcandy Dime 3 earbuds accept Bluetooth pairing from an unpaired device in close range with no PIN, no access to the charging case and no approval from the owner.
- Once bonded, the attacker's device is trusted and reconnects automatically, letting it cut the owner's connection, hijack playback, use the headset profile and capture live microphone audio.
- The flaw is CVE-2025-20701 in the Airoha Bluetooth Audio SDK, which the Dime 3 (model S2DCW) uses for wireless connectivity, and firmware 1.0.0.28 is the affected build.
- Skullcandy's fix landed in firmware 1.0.0.30, but CERT/CC found no consumer-accessible method to move an existing unit off 1.0.0.28, whether by hand or through the app.
Compiled by The WatchSomething wrong?How this is made
Why it matters
- exposure The reachable asset is a live microphone, so the people exposed include anyone talking near the wearer, not only the person who bought the earbuds.
- decision An owner on 1.0.0.28 is choosing between buying replacement hardware and accepting an open pairing surface, because the advisory offers no software route out.
- constraint The advisory is written for consumers and offers no fleet or workplace guidance, so anyone responsible for room privacy has nothing to enumerate a building against.
- precedent This case shows the split runs on whether a vendor built a firmware channel to the product before it needed one, not on how the flaw was diagnosed.
Pairing is the entire attack. A radio in range asks, and a Dime 3 on firmware 1.0.0.28 answers yes without a PIN, without access to the charging case, and without a prompt on the owner's phone [2]. The bond then sticks. The attacker's device is trusted from that point and reconnects on its own whenever it comes back into range, which is what turns a proximity trick into standing access to the headset profile and live microphone audio [5].
Skullcandy's fix exists. It is firmware 1.0.0.30 [6], and it reaches units that ship with it. CERT/CC's advisory is explicit about the rest: "As of this writing, there are no known consumer-accessible methods to update an existing unit from the affected firmware version 1.0.0.28 to version 1.0.0.30" [7]. For a pair already in someone's pocket, that leaves replacement or leaving them powered off as the only controls [1].
Airoha published SDK updates on August 4, 2025, and earbud manufacturers took them up afterwards [8]. The underlying defect is a missing-authentication problem that affects earbud and headphone products from multiple vendors, not just this model [4]; ERNW researchers found it and presented it at the TROOPER conference last year [9]. Apple shipped a firmware update for its Beats Studio Buds in June [10]. The defect traces to the same SDK across vendors; what separates a closed case from an open one is firmware delivery, not diagnosis [2].
The wearer's only cue is a "new device paired" notification after the rogue bond is already made, which CERT/CC expects to be missed or read as a brief dropout and reconnection [12]. CERT/CC picked up the Skullcandy case from a tip by researcher Jacob Nowak [11]. Neither the advisory nor the coverage puts a number on how many Dime 3 units are in circulation on 1.0.0.28; the product sits at the cheap end of the market and, per BleepingComputer, is popular with young buyers [14]. Skullcandy has not accounted publicly for the gap, and BleepingComputer reported it could not reach the company because its chatbot does not handle press requests [13].
That is the whole evidence base. It is a consumer advisory. It carries no serial-number or date-code mapping, so an owner holding a Dime 3 cannot tell from the box which firmware is inside. Until a service or app path for 1.0.0.28 appears, the controls available are physical: distance and the power state of the earbuds.
What to watch
- Whether Skullcandy publishes a service or app path that moves an existing unit from 1.0.0.28 to 1.0.0.30.
- Whether CERT/CC names further vendors still shipping unpatched Airoha Bluetooth Audio SDK firmware.
- Whether a public proof-of-concept for CVE-2025-20701 appears, which would move this from close-range research to opportunistic use.