https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 05:39:59 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-06825 bdu:2026-06825 https://cve.radiocsirt.org/vuln/bdu:2026-06825 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0622 certfr-2026-avi-0622 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0622 https://cve.radiocsirt.org/vuln/euvd-2026-350566 EUVD-2026-350566 https://cve.radiocsirt.org/vuln/euvd-2026-350566 https://cve.radiocsirt.org/vuln/fkie_cve-2026-45585 <p>Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as &amp;quot;YellowKey&amp;quot;. The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices. We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available. Mitigation FAQs Should I leverage the temporary mitigation? Microsoft recommends that you consider implementing these mitigations if you are concerned your devices and data are at risk of being compromised or stolen. For example, if your organization’s employees take their work devices home or on business travel. What impact to service availability/management could be caused by implementing the mitigations? Implementing these mitigations will not impact service availability or management operations. Do customers need to revert the changes made to mitigate the vulnerability once the security update to protect against this vulnerability is available? No. The security update will maintain the mitigation&#39;s behavior once the security update is installed. I am using TPM+PIN, am I at risk of this vulnerability being exploited No, if you are using TPM+PIN the vulnerability is not exploitable.</p> <p>Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as &amp;quot;YellowKey&amp;quot;. The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices. We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available. Mitigation FAQs Should I leverage the temporary mitigation? Microsoft recommends that you consider implementing these mitigations if you are concerned your devices and data are at risk of being compromised or stolen. For example, if your organization’s employees take their work devices home or on business travel. What impact to service availability/management could be caused by implementing the mitigations? Implementing these mitigations will not impact service availability or management operations. Do customers need to revert the changes made to mitigate the vulnerability once the security update to protect against this vulnerability is available? No. The security update will maintain the mitigation&#39;s behavior once the security update is installed. I am using TPM+PIN, am I at risk of this vulnerability being exploited No, if you are using TPM+PIN the vulnerability is not exploitable.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-45585 https://cve.radiocsirt.org/vuln/ghsa-2h24-8rjh-qgjv <p>Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as &amp;quot;YellowKey&amp;quot;. The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices. We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available.</p> <p>Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as &amp;quot;YellowKey&amp;quot;. The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices. We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available.</p> https://cve.radiocsirt.org/vuln/ghsa-2h24-8rjh-qgjv https://cve.radiocsirt.org/vuln/msrc_cve-2026-45585 msrc_CVE-2026-45585 https://cve.radiocsirt.org/vuln/msrc_cve-2026-45585 https://cve.radiocsirt.org/vuln/ncsc-2026-0165 NCSC-2026-0165 https://cve.radiocsirt.org/vuln/ncsc-2026-0165 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1609 <p>Ein Angreifer mit physischem Zugriff kann eine Schwachstelle in Microsoft Windows 11 und Microsoft Windows Server 2025 ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein Angreifer mit physischem Zugriff kann eine Schwachstelle in Microsoft Windows 11 und Microsoft Windows Server 2025 ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1609