[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fcvJcyzQ2C8q1GXpXgKB6KDq3_ydm1ESpzfnPqnIPgfE":3},{"success":4,"data":5},true,{"vendor":6,"topVulnerabilitiesByEpss":36,"kevVulnerabilities":89,"topProductsByCves":90,"seoMetadata":95,"meta":104},{"vendorId":7,"vendorName":8,"productCount":9,"cveCount":10,"kevCount":11,"versionCount":12,"lastCveUpdate":13,"firstLetter":14,"products":15,"description":35},3881,"bluetooth",4,16,0,17,"2023-11-28","b",[16,21,26,31],{"id":17,"product_name":18,"version_count":19,"cve_count":20,"kev_count":11,"last_cve_update":13},14693,"bluetooth_core_specification",13,10,{"id":22,"product_name":23,"version_count":24,"cve_count":9,"kev_count":11,"last_cve_update":25},14695,"mesh_profile",2,"2021-05-24",{"id":27,"product_name":28,"version_count":29,"cve_count":24,"kev_count":11,"last_cve_update":30},14692,"bluetooth_core",1,"2020-05-19",{"id":32,"product_name":33,"version_count":29,"cve_count":29,"kev_count":11,"last_cve_update":34},14694,"bluetooth_stack","2011-07-13","Bluetooth is a technology vendor with 4 tracked products and 16 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this vendor.",[37,46,52,57,62,67,71,76,81,85],{"cveId":38,"description":39,"publishedDate":40,"cvssScore":41,"cvssVersion":42,"severity":43,"isKev":44,"epssScore":45},"CVE-2020-15802","Devices supporting Bluetooth before 5.1 may allow man-in-the-middle attacks, aka BLURtooth. Cross Transport Key Derivation in Bluetooth Core Specification v4.2 and v5.0 may permit an unauthenticated user to establish a bonding with one transport, either LE or BR\u002FEDR, and replace a bonding already established on the opposing transport, BR\u002FEDR or LE, potentially overwriting an authenticated key with an unauthenticated key, or a key with greater entropy with one with less.","2020-09-11",5.9,"v3.1","Medium",false,0.07079,{"cveId":47,"description":48,"publishedDate":34,"cvssScore":49,"cvssVersion":42,"severity":50,"isKev":44,"epssScore":51},"CVE-2011-1265","The Bluetooth Stack 2.1 in Microsoft Windows Vista SP1 and SP2 and Windows 7 Gold and SP1 does not prevent access to objects in memory that (1) were not properly initialized or (2) have been deleted, which allows remote attackers to execute arbitrary code via crafted Bluetooth packets, aka \"Bluetooth Stack Vulnerability.\"",8.8,"High",0.05948,{"cveId":53,"description":54,"publishedDate":30,"cvssScore":55,"cvssVersion":42,"severity":43,"isKev":44,"epssScore":56},"CVE-2020-10135","Legacy pairing and secure-connections pairing authentication in Bluetooth BR\u002FEDR Core Specification v5.2 and earlier may allow an unauthenticated user to complete authentication without pairing credentials via adjacent access. An unauthenticated, adjacent attacker could impersonate a Bluetooth BR\u002FEDR master or slave to pair with a previously paired remote device to successfully complete the authentication procedure without knowing the link key.",5.4,0.02366,{"cveId":58,"description":59,"publishedDate":13,"cvssScore":60,"cvssVersion":42,"severity":43,"isKev":44,"epssScore":61},"CVE-2023-24023","Bluetooth BR\u002FEDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS.",6.8,0.01297,{"cveId":63,"description":64,"publishedDate":25,"cvssScore":65,"cvssVersion":42,"severity":50,"isKev":44,"epssScore":66},"CVE-2020-26556","Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, able to conduct a successful brute-force attack on an insufficiently random AuthValue before the provisioning procedure times out, to complete authentication by leveraging Malleable Commitment.",7.5,0.00907,{"cveId":68,"description":69,"publishedDate":25,"cvssScore":55,"cvssVersion":42,"severity":43,"isKev":44,"epssScore":70},"CVE-2020-26555","Bluetooth legacy BR\u002FEDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an unauthenticated nearby device to spoof the BD_ADDR of the peer device to complete pairing without knowledge of the PIN.",0.0088,{"cveId":72,"description":73,"publishedDate":25,"cvssScore":74,"cvssVersion":42,"severity":43,"isKev":44,"epssScore":75},"CVE-2020-26558","Bluetooth LE and BR\u002FEDR secure pairing in Bluetooth Core Specification 2.1 through 5.2 may permit a nearby man-in-the-middle attacker to identify the Passkey used during pairing (in the Passkey authentication procedure) by reflection of the public key and the authentication evidence of the initiating device, potentially permitting this attacker to complete authenticated pairing with the responding device using the correct Passkey for the pairing session. The attack methodology determines the Passkey value one bit at a time.",4.2,0.00872,{"cveId":77,"description":78,"publishedDate":25,"cvssScore":79,"cvssVersion":42,"severity":50,"isKev":44,"epssScore":80},"CVE-2020-26560","Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, reflecting the authentication evidence from a Provisioner, to complete authentication without possessing the AuthValue, and potentially acquire a NetKey and AppKey.",8.1,0.00855,{"cveId":82,"description":83,"publishedDate":25,"cvssScore":49,"cvssVersion":42,"severity":50,"isKev":44,"epssScore":84},"CVE-2020-26559","Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (participating in the provisioning protocol) to identify the AuthValue used given the Provisioner’s public key, and the confirmation number and nonce provided by the provisioning device. This could permit a device without the AuthValue to complete provisioning without brute-forcing the AuthValue.",0.00852,{"cveId":86,"description":87,"publishedDate":25,"cvssScore":65,"cvssVersion":42,"severity":50,"isKev":44,"epssScore":88},"CVE-2020-26557","Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (without possession of the AuthValue used in the provisioning protocol) to determine the AuthValue via a brute-force attack (unless the AuthValue is sufficiently random and changed each time).",0.00828,[],[91,92,93,94],{"id":17,"product_name":18,"version_count":19,"cve_count":20,"kev_count":11,"last_cve_update":13},{"id":22,"product_name":23,"version_count":24,"cve_count":9,"kev_count":11,"last_cve_update":25},{"id":27,"product_name":28,"version_count":29,"cve_count":24,"kev_count":11,"last_cve_update":30},{"id":32,"product_name":33,"version_count":29,"cve_count":29,"kev_count":11,"last_cve_update":34},{"title":96,"metaDescription":97,"keywords":98,"structuredData":99},"Bluetooth - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Bluetooth covering 4 products with 16 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Bluetooth vulnerabilities, Bluetooth security, Bluetooth CVE, Bluetooth threat intelligence, vendor security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":100,"@type":101,"name":102,"description":97,"url":103},"https:\u002F\u002Fschema.org","Organization","Bluetooth","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Fbluetooth",{"totalProducts":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":13,"generatedAt":105,"apiVersion":106},"2026-10-19T17:53:19.660Z","3.0"]