GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GCVE-1988-2026-0282

Vulnerability from gna-1988 – Published: 2026-09-08 11:24 – Updated: 2026-09-08 11:24
VLAI
Title
Skullcandy Dime 3 unauthorized Bluetooth pairing behavior
Summary
Hello, I am submitting the following security disclosure for publication on the Full Disclosure mailing list. Title: Pairing Without Consent: CVE-2025-20701 Behavior on Skullcandy Dime 3 Affected product: Skullcandy Dime 3 wireless earbuds Vulnerability: Unauthorized Bluetooth Classic pairing and persistent bond creation Description: Testing demonstrated that a previously unknown Linux computer could pair with a Skullcandy Dime 3 earbud set and store a persistent Bluetooth bond without the earbuds being intentionally placed into pairing mode. No confirmation or physical interaction with the earbuds was required during the pairing process. The observed behavior is consistent with CVE-2025-20701. Security impact: A nearby attacker within Bluetooth range may be able to establish an unauthorized trusted relationship with the earbuds. The stored bond could allow subsequent connections from the unauthorized device and potentially interfere with the legitimate user’s Bluetooth connection. Evidence: The public research repository includes: - A detailed technical report - Reproduction information - Screenshots - A sanitized BTSnoop capture - A packet-level description of the pairing sequence Repository: https://github.com/x0jac0b0x/skullcandy-dime3-cve-2025-20701 The published BTSnoop capture preserves the pairing and connection sequence. The 16-byte BR/EDR link key was replaced with zero bytes before publication. The original, unmodified capture has been retained privately. This research was conducted on hardware I own and is being published for defensive research, independent verification, and vendor awareness. Regards, Jacob Nowak Independent Security Researcher GitHub: https://github.com/x0jac0b0x _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Impacted products
Vendor Product Version CPE status
unknown Skullcandy Dime 3 Affected: unknown
guessed Create a notification for this product.
Relationships
reference GCVE-1988-2026-0282 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "Skullcandy Dime 3",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Jacob Nowak"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Hello,\n\nI am submitting the following security disclosure for publication on the\nFull Disclosure mailing list.\n\nTitle: Pairing Without Consent: CVE-2025-20701 Behavior on Skullcandy Dime 3\n\nAffected product:\nSkullcandy Dime 3 wireless earbuds\n\nVulnerability:\nUnauthorized Bluetooth Classic pairing and persistent bond creation\n\nDescription:\n\nTesting demonstrated that a previously unknown Linux computer could pair\nwith a Skullcandy Dime 3 earbud set and store a persistent Bluetooth bond\nwithout the earbuds being intentionally placed into pairing mode.\n\nNo confirmation or physical interaction with the earbuds was required\nduring the pairing process.\n\nThe observed behavior is consistent with CVE-2025-20701.\n\nSecurity impact:\n\nA nearby attacker within Bluetooth range may be able to establish an\nunauthorized trusted relationship with the earbuds. The stored bond could\nallow subsequent connections from the unauthorized device and potentially\ninterfere with the legitimate user\u2019s Bluetooth connection.\n\nEvidence:\n\nThe public research repository includes:\n\n   - A detailed technical report\n   - Reproduction information\n   - Screenshots\n   - A sanitized BTSnoop capture\n   - A packet-level description of the pairing sequence\n\nRepository:\n\nhttps://github.com/x0jac0b0x/skullcandy-dime3-cve-2025-20701\n\nThe published BTSnoop capture preserves the pairing and connection\nsequence. The 16-byte BR/EDR link key was replaced with zero bytes before\npublication. The original, unmodified capture has been retained privately.\n\nThis research was conducted on hardware I own and is being published for\ndefensive research, independent verification, and vendor awareness.\n\nRegards,\n\nJacob Nowak\nIndependent Security Researcher\nGitHub: https://github.com/x0jac0b0x\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T11:24:56Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Aug/7"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Aug/7"
        },
        {
          "url": "https://github.com/x0jac0b0x"
        },
        {
          "url": "https://github.com/x0jac0b0x/skullcandy-dime3-cve-2025-20701"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Aug/7"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "Skullcandy Dime 3 unauthorized Bluetooth pairing behavior",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2025-20701",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0282",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Aug/7",
            "automated": true,
            "contentSha256": "76718710d96bdc9795176214e35243cb3e582c997a565fae63c5f0d93fde612b",
            "evidenceScore": 6,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Aug/7",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-07-28T20:00:34Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0282"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-08T11:24:56Z",
    "dateUpdated": "2026-09-08T11:24:56Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0282"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…