AMI Security Advisories
Committed to providing the highest level of security in our products, with our AMI Security Team standing by for a rapid response.
AMI’s Product Security Incident Response Team (PSIRT) is equipped to respond quickly and efficiently to any identified vulnerabilities and provide remediations to our OEM/ODM customers, as well as the industry at large, through releases, AMI security advisories and other communication channels. We are committed to ensuring the security of our products from vulnerability sighting to public disclosure.
Read the statement from AMI’s Chief Information Security Officer.
Security advisories from AMI provide fixes or workarounds for potential vulnerabilities associated with AMI products. AMI continuously works with customers and partners to provide timely updates to help mitigate security vulnerabilities.
For customers who have questions related to security advisories, please contact your AMI Sales Representative.
AMI Security Advisories:
Document and CVE numbers to be provided when available
AMI-SA-2025009
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2025-58770 | 7.2 | AMI-SA-2025009 | 12/12/25 | 12/12/25 |
AMI-SA-2025008
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2025-22831 | 5.9 | AMI-SA-2025008 | 10/14/25 | 10/15/25 |
| CVE-2025-22832 | 5.9 | AMI-SA-2025008 | 10/14/25 | 10/15/25 |
| CVE-2025-22833 | 4.6 | AMI-SA-2025008 | 10/14/25 | 10/15/25 |
| CVE-2025-33044 | 5.9 | AMI-SA-2025008 | 10/14/25 | 10/15/25 |
AMI-SA-2025007
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2025-33045 | 8.2 | AMI-SA-2025007 | 09/09/25 | 09/09/25 |
AMI-SA-2025006
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2025-22834 | 4.2 | AMI-SA-2025006 | 08/12/25 | 08/12/25 |
| CVE-2025-22830 | 7.3 | AMI-SA-2025006 | 08/12/25 | 08/12/25 |
AMI-SA-2025005
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2025-33043 | 5.8 | AMI-SA-2025005 | 05/29/25 | 05/29/25 |
AMI-SA-2025004
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2024-42446 | 7.5 | AMI-SA-2025004 | 05/13/25 | 05/13/25 |
AMI-SA-2025003
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2024-54084 | 7.5 | AMI-SA-2025003 | 03/11/25 | 03/13/25 |
| CVE-2024-54085 | 10.0 | AMI-SA-2025003 | 03/11/25 | 03/13/25 |
AMI-SA-2025002
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2024-33659 |
5.7 | AMI-SA-2025002Â | 02/11/25 | 02/11/25 |
AMI-SA-2025001
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2024-42444 | 7.5 | AMI-SA-2025001Â | 01/14/25 | 01/14/25 |
AMI-SA-2024004
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2024-2315 | 6.8 | AMI-SA-2024004Â | 11/12/24 | 11/12/24 |
| CVE-2024-33658 | 4.4 | AMI-SA-2024004Â | 11/12/24 | 11/12/24 |
| CVE-2024-33660 | 5.2 | AMI-SA-2024004Â | 11/12/24 | 11/12/24 |
| CVE-2024-42442 | 7.2 | AMI-SA-2024004Â Â | 11/12/24 | 11/12/24 |
AMI-SA-2024003
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2024-33657 | 7.8 | AMI-SA-2024003Â | 8/19/24 | 8/19/24 |
| CVE-2024-33656 | 7.8 | AMI-SA-2024003Â | 8/19/24 | 8/19/24 |
AMI-SA-2024002
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2018-25103 | 2.3 | AMI-SA-2024002Â | 4/15/24 | 7/09/24 |
AMI-SA-2024001
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-45229 | 6.5 | AMI-SA-2024001 | 1/16/24 | 1/16/24 |
| CVE-2023-45230Â | 8.3 | AMI-SA-2024001 | 1/16/24 | 1/16/24 |
| CVE-2023-45231Â | 6.5 | AMI-SA-2024001 | 1/16/24 | 1/16/24 |
| CVE-2023-45232Â | 7.5 | AMI-SA-2024001 | 1/16/24 | 1/16/24 |
| CVE-2023-45233Â | 7.5 | AMI-SA-2024001 | 1/16/24 | 1/16/24 |
| CVE-2023-45234Â | 8.3 | AMI-SA-2024001 | 1/16/24 | 1/16/24 |
| CVE-2023-45235 | 8.3 | AMI-SA-2024001 | 1/16/24 | 1/16/24 |
AMI-SA-2023010
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-37293 | 9.6 | AMI-SA-2023010 | 1/09/24 | 1/09/24 |
| CVE-2023-37296 | 8.3 | AMI-SA-2023010 | 1/09/24 | 1/09/24 |
| CVE-2023-37297 | 8.3 | AMI-SA-2023010 | 1/09/24 | 1/09/24 |
| CVE-2023-37295 | 8.3 | AMI-SA-2023010 | 1/09/24 | 1/09/24 |
| CVE-2023-37294 | 8.3 | AMI-SA-2023010 | 1/09/24 | 1/09/24 |
| CVE-2023-3043 | 9.6 | AMI-SA-2023010 | 1/09/24 | 1/09/24 |
| CVE-2023-34333 | 7.8 | AMI-SA-2023010 | 1/09/24 | 1/09/24 |
| CVE-2023-34332 | 7.8 | AMI-SA-2023010 | 1/09/24 | 1/09/24 |
AMI-SA-2023009
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-39538 | 7.5 | AMI-SA-2023009 | 12/06/23 | 12/06/23 |
| CVE-2023-39539 | 7.5 | AMI-SA-2023009 | 12/06/23 | 12/06/23 |
AMI-SA-2023008
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-39535 | 7.5 | AMI-SA-2023008 | 11/14/23 | 11/14/23 |
| CVE-2023-39536 | 7.5 | AMI-SA-2023008 | 11/14/23 | 11/14/23 |
| CVE-2023-39537 | 7.5 | AMI-SA-2023008 | 11/14/23 | 11/14/23 |
AMI-SA-2023007
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-34469 | 4.9 | AMI-SA-2023007 | 09/12/23 | 09/25/23 |
| CVE-2023-34470 | 6.8 | AMI-SA-2023007 | 09/12/23 | 09/25/23 |
AMI-SA-2023006
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-34472 | 5.7 | AMI-SA-2023006 | 7/05/23 | 7/05/23 |
| CVE-2023-34473 | 6.6 | AMI-SA-2023006 | 7/05/23 | 7/05/23 |
| CVE-2023-34471 | 6.3 | AMI-SA-2023006 | 7/05/23 | 7/05/23 |
| CVE-2023-34337 | 7.6 | AMI-SA-2023006 | 7/05/23 | 7/05/23 |
| CVE-2023-34338 | 7.1 | AMI-SA-2023006 | 7/05/23 | 7/05/23 |
| CVE-2023-34329 | 9.1 | AMI-SA-2023006 | 7/18/23 | 7/18/23 |
| CVE-2023-34330 | 8.2 | AMI-SA-2023006 | 7/18/23 | 7/18/23 |
AMI-SA-2023005
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-34344 | 5.3 | AMI-SA-2023005 | 6/12/23 | 6/12/23 |
| CVE-2023-25191 | 7.5 | AMI-SA-2023005 | 6/12/23 | 6/12/23 |
| CVE-2023-34345 | 6.5 | AMI-SA-2023005 | 6/12/23 | 6/12/23 |
| CVE-2023-34341 | 7.2 | AMI-SA-2023005 | 6/12/23 | 6/12/23 |
| CVE-2023-34342 | 6.0 | AMI-SA-2023005 | 6/12/23 | 6/12/23 |
| CVE-2023-34343 | 7.2 | AMI-SA-2023005 | 6/12/23 | 6/12/23 |
| CVE-2023-34334 | 7.2 | AMI-SA-2023005 | 6/12/23 | 6/12/23 |
| CVE-2023-34335 | 7.7 | AMI-SA-2023005 | 6/12/23 | 6/12/23 |
| CVE-2023-34336 | 8.1 | AMI-SA-2023005 | 6/12/23 | 6/12/23 |
AMI-SA-2023004
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-29552 | 6.5 | AMI-SA-2023004 | 5/01/23 | 5/01/23 |
AMI-SA-2023003
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-28863 | 5.9 | AMI-SA-2023003Â | 4/04/23 | 4/04/23 |
AMI-SA-2023002
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2023-25191 | 9.1 | AMI-SA-2023002Â | 2/14/23 | 2/14/23 |
| CVE-2023-25192 | 5.3 | AMI-SA-2023002Â | 2/14/23 | 2/14/23 |
AMI-SA-2023001
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2022-40258 | 5.3 | AMI-SA-2023001 | 1/30/23 | 2/01/23 |
| CVE-2022-26872 | 8.3 | AMI-SA-2023001 | 1/30/23 | 2/01/23 |
| CVE-2022-40259 | 9.9 | AMI-SA-2023001 | 1/30/23 | 2/01/23 |
| CVE-2022-2827 | 7.5 | AMI-SA-2023001 | 1/30/23 | 2/01/23 |
| CVE-2022-40242 | 9.7 | AMI-SA-2023001 | 1/30/23 | 2/01/23 |
AMI-SA-2022001
| Vulnerabilities | CVSS Score | AMI Security Advisory | Published Date | Last Revised |
| CVE-2021-44769 | 4.9 | AMI-SA-2022001 | 12/20/22 | 12/20/22 |
| CVE-2021-46279 | 5.8 | AMI-SA-2022001 | 12/20/22 | 12/20/22 |
| CVE-2021-45925 | 5.3 | AMI-SA-2022001 | 12/20/22 | 12/20/22 |
| CVE-2021-4228 | 5.8 | AMI-SA-2022001 | 12/20/22 | 12/20/22 |
Report a Security Issue to AMI
Please provide as much information as possible, including:
- The products and versions affected.
- A detailed description of the vulnerability.
- Information on known exploits.
Aptio UEFI BIOS Firmware
If you have information about a security issue or vulnerability with a BIOS Product from AMI, please send an email to the AMI BIOS Security Team at [email protected]. For added security, we recommend using AMI’s provided Encryption Key to encrypt sensitive information before sending. A member of the BIOS Security Team will review your email and contact you to collaborate on resolving the issue.
MegaRAC BMC Firmware
If you have information about a security issue or vulnerability with a MegaRAC Product from AMI, please send an email to the AMI MegaRAC Security Team at [email protected]. For added security, we recommend using AMI’s provided Encryption Key to encrypt sensitive information before sending. A member of the MegaRAC Security Team will review your email and contact you to collaborate on resolving the issue.
Tektagon Firmware
If you have information about a security issue or vulnerability with a Tektagon Product from AMI, please send an email to the AMI Tektagon Security Team at [email protected]. For added security, we recommend using AMI’s provided Encryption Key to encrypt sensitive information before sending. A member of the Tektagon Security Team will review your email and contact you to collaborate on resolving the issue.
Encryption Key for Secure Data Transmission
It is good security practice that you only trust validated encryption keys. Do not trust encryption keys that have not been validated. It is important to also validate your copy of the AMI public encryption key to ensure it is legitimate.
Validate your AMI public encryption key to ensure it is legitimate. It is a good security practice only to trust validated encryption keys.
AMI Security Team Key Information
- User-ID: AMI Product Security Incident Response Team [email protected]
- Created: Apr 15 18:49:27 UTC 2025
- Expires: Apr 15 18:49:26 UTC 2027
- Type: 2048-bit RSA (secret key available)
- Usage:Â Signing, Encryption, Certifying User-IDs
- Fingerprint: 6e88bbdff4440f8e8eaf3750a4addcf1bf83c633
Please note that this encryption key is for both the MegaRAC and BIOS security. However, please use the AMI Security Team Key Information as provided above.