Report potential product security vulnerabilities


At TI, we set a high priority on the security of our products. However, as we all know, no matter how much effort is put into product security, no product or customer system can be 100% secure. TI wants to learn about any potential security issues impacting our products so that we can take the necessary steps to promptly address them. TI’s Product Security Incident Response Team (PSIRT) oversees the process of accepting and responding to reports of potential security vulnerabilities involving TI semiconductor products, including hardware, software and documentation.

How to report a potential security vulnerability

You can contact the TI PSIRT to report a potential security vulnerability at Your report should be in English. TI will respond in a timely manner to confirm receipt of your email. 

Vulnerability information is extremely sensitive. The TI PSIRT strongly recommends that all submitted security vulnerability reports be sent encrypted, using the TI PSIRT PGP/GPG Key:

  • Fingerprint: 898C ECC3 451F 9438 D972  06B6 4C13 1A0F 9AF0 04D8
  • Public Key File (ZIP, 3 KB)


Free software to read and author PGP/GPG encrypted messages may be obtained from:

Recommended information to include in your report

To help the TI PSIRT perform triage of the potential security vulnerability, it is recommended that you provide the following information:

  • TI hardware or software products potentially affected (including version or revision)
  • How and when the potential vulnerability was discovered, and by whom
  • Technical description of the potential vulnerability, including any related (1) known exploits and (2) existing CVE ID(s)
  • Your contact information, so that TI is able to ask any necessary follow-up questions

Report handling process

Once submitted, TI follows the following process to evaluate and respond to the potential security vulnerability:

  1. Notification: TI becomes aware of a potential security vulnerability.
  2. Initial triage: TI reviews the submission to determine whether a TI product may be affected and whether sufficient information has been provided.
  3. Technical analysis: TI investigates the reported potential vulnerability in greater technical    depth.[1]
  4. Remediation: TI takes appropriate action for verified product security vulnerability.
  5. Disclosure: Where appropriate, TI discloses information about the verified vulnerability and may make available the remediation e.g. in a security advisory or a bulletin. 


[1] TI will score the vulnerability using CVSS (Common Vulnerability Scoring System) v3.0, so that the vulnerability is properly prioritized for analysis and remediation. A CVE (Common Vulnerabilities and Exposures) ID for the vulnerability may be created, as needed. 

Responsible handling policy

Like most in the technology industry, TI PSIRT follows a responsible handling policy.  Our policy describes what you can expect from TI and our expectation from you. It is based on the CERT® Guide to Coordinated Vulnerability Disclosure. Before you submit a report, please review our policy as it describes the basis of our relationship with you.

Security advisories

Below you will find public information about security vulnerabilities and our available mediations.

Incident ID
Publication date
TI-PSIRT-2018-060007 BLE-STACK Heap Overflow Issue Nov. 1, 2018
TI-PSIRT-2019-010018 BT (BR/EDR) SIG Errata 11838 - LMP Encryption Key Minimum Size Change Aug. 20, 2019
TI-PSIRT-2019-050023 CC256x and WL18xx Bluetooth Low Energy - LE scan vulnerability (CVE-2019-15948) Nov. 12, 2019
TI-PSIRT-2019-060025 CC254x OAD: AES CTR crypto implementation vulnerability Nov. 12, 2019
TI-PSIRT-2019-060032 CC254x OAD: AES-CBC MAC verification vulnerability Nov. 12, 2019
TI-PSIRT-2019-100034 Bluetooth Low Energy – unexpected public key crash (SweynTooth, CVE-2019-17520) Feb. 19, 2020
TI-PSIRT-2019-100036 Bluetooth Low Energy – Invalid Connection Request (SweynTooth, CVE-2019-19193)
Feb. 19, 2020
TI-PSIRT-2019-080030 Variable Time Tag Comparison on SimpleLink™ Devices Feb. 28, 2020
TI-PSIRT-2020-020038 Bluetooth Low Energy, Basic Rate/Enhanced DataRate – Method Confusion Pairing Vulnerability (CVE-2020-10134) May 18, 2020
TI-PSIRT-2020-040043 Bluetooth Basic Rate/Enhanced Data Rate –Bluetooth Impersonation Attacks (BIAS, CVE-2020-10135) May 18, 2020
TI-PSIRT-2020-060056 Bluetooth® Low Energy – Missing Length Check for
UNPI Packets Over SPI on CC1350 and CC26x0
October 7, 2020
TI-PSIRT-2020-100078 Amnesia Open-Source TCP/IP Stack Vulnerabilities (AMNESIA:33) December 21, 2020
TI-PSIRT-2020-070058 Potential Heap Overflow Vulnerabilities in TI Z-Stack Zigbee Cluster Library (ZCL) Parsing Functions January 22, 2021
TI-PSIRT-2020-080063 Bluetooth® Low Energy – Updating Connection MTU Size During an Ongoing OAD Operation May Cause Buffer Overflow March 1, 2021
TI-PSIRT-2020-100073 SimpleLink™ Wi-Fi® CC32xx/CC31xx SDK and SimpleLink MSP432E4 SDK Integer and Buffer OverflowIssues April 29, 2021
TI-PSIRT-2020-100074 SimpleLink™ CC13XX, CC26XX, CC32XX and MSP432E4 Integer Overflow Issues April 29, 2021
TI-PSIRT-2020-100076 Integer and Buffer Overflow Issues – TI-NDK April 29, 2021
TI-PSIRT-2020-090066 FragAttacks - FRagmentation and AGgregation Attacks May 11, 2021
TI-PSIRT-2020-100068 Bluetooth® SIG Erratum – Impersonation in the Passkey Entry Protocol May 23, 2021
TI-PSIRT-2020-100069 Bluetooth® SIG Erratum – Authentication of the LE Legacy Pairing Protocol May 23, 2021
TI-PSIRT-2020-090070 Bluetooth® Low Energy, Basic Rate/Enhanced Data Rate – PIN-Code Pairing Key Derivation May 23, 2021
TI-PSIRT-2020-080064 Boot Image Manager (BIM) Potential Security Vulnerabilities in CC13x2, CC26x2, CC2640R2 Devices May 24, 2021
TI-PSIRT-2021-040098 InjectaBLE: Injecting Malicious Traffic Into Established Bluetooth® Low Energy Connections (CVE-2021-31615) June 22, 2021

TI PSIRT discloses information publicly where appropriate; this should not be considered a comprehensive list of incidents that we have handled. Inquiries regarding specific incidents can be addressed to

Media inquiries

Media inquiries regarding the security of TI products may be directed to