GCVE-1988-2026-0569
Vulnerability from gna-1988 – Published: 2026-11-13 02:29 – Updated: 2026-11-13 02:29- related CVE-2026-113964
- related CVE-2026-113965
- related CVE-2026-113968
- related CVE-2026-113969
- related CVE-2026-113970
{
"containers": {
"cna": {
"affected": [
{
"product": "Watchos",
"vendor": "Apple",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Apple Product Security via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nAPPLE-SA-11-09-2026-8 watchOS 26.6.1\n\nwatchOS 26.6.1 addresses the following issues.\nInformation about the security content is also available at\nhttps://support.apple.com/149723.\n\nApple maintains a Security Releases page at\nhttps://support.apple.com/100100 which lists recent\nsoftware updates with security advisories.\n\nAirPlay\nAvailable for: Apple Watch Series 6, Apple Watch Series 7, Apple Watch\nSeries 8, Apple Watch SE (2nd generation), and Apple Watch Ultra\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113968: Apple\n\nBluetooth\nAvailable for: Apple Watch Series 6, Apple Watch Series 7, Apple Watch\nSeries 8, Apple Watch SE (2nd generation), and Apple Watch Ultra\nImpact: An attacker in Bluetooth range may be able to corrupt process\nmemory\nDescription: A use-after-free issue was addressed with improved memory\nmanagement.\nCVE-2026-113970: Apple\n\nCoreUtils\nAvailable for: Apple Watch Series 6, Apple Watch Series 7, Apple Watch\nSeries 8, Apple Watch SE (2nd generation), and Apple Watch Ultra\nImpact: A malicious Bluetooth device may be able to establish a pairing\nwithout user interaction\nDescription: This issue was addressed with improved checks.\nCVE-2026-113965: Apple\n\nCoreUtils\nAvailable for: Apple Watch Series 6, Apple Watch Series 7, Apple Watch\nSeries 8, Apple Watch SE (2nd generation), and Apple Watch Ultra\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts and pair with a device without user\ninteraction\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113964: an anonymous researcher\n\nrapportd\nAvailable for: Apple Watch Series 6, Apple Watch Series 7, Apple Watch\nSeries 8, Apple Watch SE (2nd generation), and Apple Watch Ultra\nImpact: An attacker on the same network may be able to bypass the rate\nlimit on AirPlay pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113969: Apple\n\nInstructions on how to update your Apple Watch software are\navailable at https://support.apple.com/kb/HT204641\n\nTo check the version on your Apple Watch, open the Apple Watch app\non your iPhone and select \"My Watch \u003e General \u003e About\".\n\nAlternatively, on your watch, select \"My Watch \u003e General \u003e About\".\n\nAll information is also posted on the Apple Security Releases\nweb site: https://support.apple.com/100100.\n\nThis message is signed with Apple\u0027s Product Security PGP key,\nand details are available at:\nhttps://www.apple.com/support/security/pgp/\n\n-----BEGIN PGP SIGNATURE-----\n\niQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryYmsACgkQ4Ifiq8DH\n7PUIZg//d2qdsd9FczlHYGX+r0EcVh7ODCRFN7k53cyBhMnY8MQRf0jZD7cXms/n\ny5cSB3ihdcq6F+lrnASQtA3wtrtuqNdlbtoMuim9y25n4ipLpIdqGgWFQvTrTo1u\nZCRG/Sc6BnK65B47CwpkPSSt92TyV5LQhM9scyW4dsOCAdZMUuaj8Zcw6hLVxefd\nKSClkNwRoglVg578VKxWHDU4HD2SZcLj9jKlN4m7FBG9+2dc59CSOFZ3+7xo19Q1\nRn3ZF1PXDc2AUQS+eiA5P0nOlB1sjKofIVwuXchSQ/Ulmo6m4IGij++qK+8tU1N7\nN6Z6SQhjEy+MMa/7V/QvpZTSyP4Jnjoj2+bkRNt6Tf7TMIHqcybfg1OHyqUhSdyB\n8PsUrT8cOJEneiKXOgbdDRwf8PMHiIszm+w8XYriYIEDWBtCkJsZQTUgVGp2B15W\nqhZdVniwkz11avlMYyWVZUOofag6gI8LfWHBkWEVmiGURiQAyT7eLp1Wf5yaeGXj\nE2bU3KcO5b8HQeVNtDw2JeRMZ91SxLEav3q7Ac7HzHBtZZfM6z6yqcJdzLdft+4C\nimCemy7syDVZOpze6v+3v+9300EqdKSRSBXhlsDDAusNDg9vy7CHLWTN+JDqguMW\nSvFsoP1K2Zfx9s1PGoS77aAqbPXAgUa4E00OEpjbKZbu0AwZEyI=\n=FTiO\n-----END PGP SIGNATURE-----\n\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-11-13T02:29:21Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/31"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Nov/31"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://support.apple.com/100100"
},
{
"url": "https://support.apple.com/149723"
},
{
"url": "https://support.apple.com/kb/HT204641"
},
{
"url": "https://www.apple.com/support/security/pgp/"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Nov/31"
],
"discovery": "EXTERNAL"
},
"title": "APPLE-SA-11-09-2026-8 watchOS 26.6.1",
"x_gcve": [
{
"recordType": "reference",
"relationships": [
{
"destId": "CVE-2026-113964",
"type": "related"
},
{
"destId": "CVE-2026-113965",
"type": "related"
},
{
"destId": "CVE-2026-113968",
"type": "related"
},
{
"destId": "CVE-2026-113969",
"type": "related"
},
{
"destId": "CVE-2026-113970",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0569",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/31",
"automated": true,
"contentSha256": "a681c7e4ab56588c1878e767da9df8e70995e77540d6e2ed420699823fd1cbd6",
"evidenceScore": 7,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/31",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-11-10T00:21:36Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0569"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-11-13T02:29:21Z",
"dateUpdated": "2026-11-13T02:29:21Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0569"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.