CWE-1329
AllowedReliance on Component That is Not Updateable
Abstraction: Base · Status: Incomplete
The product contains a component that cannot be updated or patched in order to remove vulnerabilities or significant bugs.
12 vulnerabilities reference this CWE, most recent first.
GHSA-MP9V-4XWC-G9HX
Vulnerability from github – Published: 2026-05-12 18:30 – Updated: 2026-05-12 18:30Reliance on a component that is not updateable in Windows Secure Boot allows an authorized attacker to bypass a security feature locally.
{
"affected": [],
"aliases": [
"CVE-2026-41097"
],
"database_specific": {
"cwe_ids": [
"CWE-1329"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-12T18:17:21Z",
"severity": "MODERATE"
},
"details": "Reliance on a component that is not updateable in Windows Secure Boot allows an authorized attacker to bypass a security feature locally.",
"id": "GHSA-mp9v-4xwc-g9hx",
"modified": "2026-05-12T18:30:46Z",
"published": "2026-05-12T18:30:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-41097"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-41097"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-XQXC-72VF-V8F5
Vulnerability from github – Published: 2026-01-13 18:31 – Updated: 2026-01-13 18:31Windows Secure Boot stores Microsoft certificates in the UEFI KEK and DB. These original certificates are approaching expiration, and devices containing affected certificate versions must update them to maintain Secure Boot functionality and avoid compromising security by losing security fixes related to Windows boot manager or Secure Boot. The operating system’s certificate update protection mechanism relies on firmware components that might contain defects, which can cause certificate trust updates to fail or behave unpredictably. This leads to potential disruption of the Secure Boot trust chain and requires careful validation and deployment to restore intended security guarantees.
Certificate Authority (CA) Location Purpose Expiration Date
Microsoft Corporation KEK CA 2011 KEK Signs updates to the DB and DBX 06/24/2026
Microsoft Corporation UEFI CA 2011 DB Signs 3rd party boot loaders, Option ROMs, etc. 06/27/2026
Microsoft Windows Production PCA 2011 DB Signs the Windows Boot Manager 10/19/2026
For more information see this CVE and Windows Secure Boot certificate expiration and CA updates.
{
"affected": [],
"aliases": [
"CVE-2026-21265"
],
"database_specific": {
"cwe_ids": [
"CWE-1329"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-13T18:16:25Z",
"severity": "MODERATE"
},
"details": "Windows Secure Boot stores Microsoft certificates in the UEFI KEK and DB. These original certificates are approaching expiration, and devices containing affected certificate versions must update them to maintain Secure Boot functionality and avoid compromising security by losing security fixes related to Windows boot manager or Secure Boot.\nThe operating system\u2019s certificate update protection mechanism relies on firmware components that might contain defects, which can cause certificate trust updates to fail or behave unpredictably. This leads to potential disruption of the Secure Boot trust chain and requires careful validation and deployment to restore intended security guarantees.\n\n\n\nCertificate Authority (CA)\nLocation\nPurpose\nExpiration Date\n\n\n\n\nMicrosoft Corporation KEK CA 2011\nKEK\nSigns updates to the DB and DBX\n06/24/2026\n\n\nMicrosoft Corporation UEFI CA 2011\nDB\nSigns 3rd party boot loaders, Option ROMs, etc.\n06/27/2026\n\n\nMicrosoft Windows Production PCA 2011\nDB\nSigns the Windows Boot Manager\n10/19/2026\n\n\n\nFor more information see this CVE and Windows Secure Boot certificate expiration and CA updates.",
"id": "GHSA-xqxc-72vf-v8f5",
"modified": "2026-01-13T18:31:11Z",
"published": "2026-01-13T18:31:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-21265"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21265"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation
Specify requirements that each component should be updateable, including ROM, firmware, etc.
Mitigation
Design the product to allow for updating of its components. Include the external infrastructure that might be necessary to support updates, such as distribution servers.
Mitigation
With hardware, support patches that can be programmed in-field or during manufacturing through hardware fuses. This feature can be used for limited patching of devices after shipping, or for the next batch of silicon devices manufactured, without changing the full device ROM.
Mitigation
Implement the necessary functionality to allow each component to be updated.
No CAPEC attack patterns related to this CWE.