CVE-2026-24795: CWE-787 Out-of-bounds Write in CloverHackyColor CloverBootloader
Out-of-bounds Write vulnerability in CloverHackyColor CloverBootloader (MdeModulePkg/Universal/RegularExpressionDxe/Oniguruma modules). This vulnerability is associated with program files regcomp.C. This issue affects CloverBootloader: before 5162.
AI Analysis
Technical Summary
CVE-2026-24795 is a medium-severity vulnerability classified as CWE-787 (Out-of-bounds Write) found in the CloverHackyColor CloverBootloader, specifically within the Oniguruma regular expression modules implemented in the MdeModulePkg/Universal/RegularExpressionDxe component. The vulnerability arises from improper bounds checking in the regcomp.C source files, allowing an attacker with local access to cause an out-of-bounds write during the bootloader's execution phase. This memory corruption can lead to unpredictable behavior including potential data corruption or system instability. The affected versions include all builds prior to 5162. The CVSS 4.0 vector indicates the attack requires local access (AV:L), no privileges (PR:N), no user interaction (UI:N), and results in low impact on availability but impacts confidentiality and integrity to some extent. The vulnerability does not require authentication and does not affect system confidentiality or integrity at a high level but can compromise the boot process's reliability. No public exploits or active exploitation have been reported to date. The vulnerability is significant in environments where CloverBootloader is used to initialize hardware and load operating systems, particularly in custom or legacy UEFI implementations. Since the bootloader operates at a low level, exploitation could potentially undermine system trustworthiness or lead to denial of service during boot. The lack of patches at the time of reporting necessitates cautious monitoring and prompt application of updates once released.
Potential Impact
For European organizations, the impact of CVE-2026-24795 depends largely on the deployment of CloverBootloader in their infrastructure. Organizations using CloverBootloader in embedded systems, custom hardware, or legacy UEFI environments may face risks of system instability or data corruption during boot, potentially causing downtime or loss of system integrity. While the vulnerability does not appear to allow remote exploitation or privilege escalation, local attackers or insiders could exploit it to disrupt system operations. This could be particularly impactful in critical infrastructure sectors such as manufacturing, telecommunications, or government systems that rely on secure and stable boot processes. The medium severity rating reflects moderate risk; however, the bootloader's foundational role means any compromise could cascade into broader system trust issues. European entities with stringent compliance requirements for system integrity and availability may find this vulnerability a compliance risk if unmitigated. The absence of known exploits reduces immediate threat but does not eliminate future risk. Therefore, organizations should prioritize identifying affected systems and plan for timely remediation to maintain operational security.
Mitigation Recommendations
To mitigate CVE-2026-24795, European organizations should: 1) Inventory all systems and devices using CloverHackyColor CloverBootloader, focusing on versions prior to build 5162. 2) Monitor vendor communications for official patches or updates addressing this vulnerability and apply them promptly once available. 3) Where patching is not immediately possible, implement strict access controls to limit local access to trusted personnel only, reducing the risk of exploitation. 4) Conduct security audits of bootloader configurations and usage to identify unnecessary exposure or legacy systems that can be upgraded or replaced. 5) Employ runtime integrity verification mechanisms such as Secure Boot or measured boot to detect unauthorized modifications during the boot process. 6) Incorporate this vulnerability into incident response and vulnerability management workflows to ensure ongoing monitoring. 7) Educate system administrators about the risks associated with local exploitation of bootloader vulnerabilities and best practices for secure system maintenance. These targeted actions go beyond generic advice by focusing on bootloader-specific controls and operational security measures.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy
CVE-2026-24795: CWE-787 Out-of-bounds Write in CloverHackyColor CloverBootloader
Description
Out-of-bounds Write vulnerability in CloverHackyColor CloverBootloader (MdeModulePkg/Universal/RegularExpressionDxe/Oniguruma modules). This vulnerability is associated with program files regcomp.C. This issue affects CloverBootloader: before 5162.
AI-Powered Analysis
Technical Analysis
CVE-2026-24795 is a medium-severity vulnerability classified as CWE-787 (Out-of-bounds Write) found in the CloverHackyColor CloverBootloader, specifically within the Oniguruma regular expression modules implemented in the MdeModulePkg/Universal/RegularExpressionDxe component. The vulnerability arises from improper bounds checking in the regcomp.C source files, allowing an attacker with local access to cause an out-of-bounds write during the bootloader's execution phase. This memory corruption can lead to unpredictable behavior including potential data corruption or system instability. The affected versions include all builds prior to 5162. The CVSS 4.0 vector indicates the attack requires local access (AV:L), no privileges (PR:N), no user interaction (UI:N), and results in low impact on availability but impacts confidentiality and integrity to some extent. The vulnerability does not require authentication and does not affect system confidentiality or integrity at a high level but can compromise the boot process's reliability. No public exploits or active exploitation have been reported to date. The vulnerability is significant in environments where CloverBootloader is used to initialize hardware and load operating systems, particularly in custom or legacy UEFI implementations. Since the bootloader operates at a low level, exploitation could potentially undermine system trustworthiness or lead to denial of service during boot. The lack of patches at the time of reporting necessitates cautious monitoring and prompt application of updates once released.
Potential Impact
For European organizations, the impact of CVE-2026-24795 depends largely on the deployment of CloverBootloader in their infrastructure. Organizations using CloverBootloader in embedded systems, custom hardware, or legacy UEFI environments may face risks of system instability or data corruption during boot, potentially causing downtime or loss of system integrity. While the vulnerability does not appear to allow remote exploitation or privilege escalation, local attackers or insiders could exploit it to disrupt system operations. This could be particularly impactful in critical infrastructure sectors such as manufacturing, telecommunications, or government systems that rely on secure and stable boot processes. The medium severity rating reflects moderate risk; however, the bootloader's foundational role means any compromise could cascade into broader system trust issues. European entities with stringent compliance requirements for system integrity and availability may find this vulnerability a compliance risk if unmitigated. The absence of known exploits reduces immediate threat but does not eliminate future risk. Therefore, organizations should prioritize identifying affected systems and plan for timely remediation to maintain operational security.
Mitigation Recommendations
To mitigate CVE-2026-24795, European organizations should: 1) Inventory all systems and devices using CloverHackyColor CloverBootloader, focusing on versions prior to build 5162. 2) Monitor vendor communications for official patches or updates addressing this vulnerability and apply them promptly once available. 3) Where patching is not immediately possible, implement strict access controls to limit local access to trusted personnel only, reducing the risk of exploitation. 4) Conduct security audits of bootloader configurations and usage to identify unnecessary exposure or legacy systems that can be upgraded or replaced. 5) Employ runtime integrity verification mechanisms such as Secure Boot or measured boot to detect unauthorized modifications during the boot process. 6) Incorporate this vulnerability into incident response and vulnerability management workflows to ensure ongoing monitoring. 7) Educate system administrators about the risks associated with local exploitation of bootloader vulnerabilities and best practices for secure system maintenance. These targeted actions go beyond generic advice by focusing on bootloader-specific controls and operational security measures.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GovTech CSG
- Date Reserved
- 2026-01-27T08:18:43.267Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 697878ed4623b1157c0fa6a0
Added to database: 1/27/2026, 8:35:57 AM
Last enriched: 1/27/2026, 8:51:33 AM
Last updated: 2/7/2026, 2:30:26 AM
Views: 30
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2071: Buffer Overflow in UTT 进取 520W
HighCVE-2026-25762: CWE-400: Uncontrolled Resource Consumption in adonisjs core
HighCVE-2026-25754: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in adonisjs core
HighCVE-2026-25644: CWE-295: Improper Certificate Validation in datahub-project datahub
HighCVE-2026-25804: CWE-287: Improper Authentication in antrea-io antrea
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.