A vulnerability classified as problematic was found in efivar . This affects an unknown function of the component libefiboot . Executing a manipulation can lead to uncontrolled recursion. This vulnerability is registered as CVE-2026-6862 . The attack needs to be launched locally. No exploit is available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358961 · CVE-2026-6862 · GCVE-0-2026-6862
EFIVAR LIBEFIBOOT RECURSION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.4 $0-$5k 0.25+
Summaryinfo
A vulnerability, which was classified as problematic, has been found in efivar. This impacts an unknown function of the component libefiboot. The manipulation leads to recursion. This vulnerability is documented as CVE-2026-6862. The attack needs to be performed locally. There is not any exploit available.
Detailsinfo
A vulnerability was found in efivar (affected version unknown) and classified as problematic. This issue affects an unknown functionality of the component libefiboot. The manipulation with an unknown input leads to a recursion vulnerability. Using CWE to declare the problem leads to CWE-674. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack. Impacted is availability. The summary by CVE is:
A flaw was found in libefiboot, a component of efivar. The device path node parser in libefiboot fails to validate that each node's Length field is at least 4 bytes, which is the minimum size for an EFI (Extensible Firmware Interface) device path node header. A local user could exploit this vulnerability by providing a specially crafted device path node. This can lead to infinite recursion, causing stack exhaustion and a process crash, resulting in a denial of service (DoS).
The advisory is shared at access.redhat.com. The identification of this vulnerability is CVE-2026-6862 since 04/22/2026. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Name
efivar
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.5
CNA Vector (redhat): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Recursion
CWE: CWE-674 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/22/2026 Advisory disclosed
04/22/2026 +0 days CVE reserved
04/22/2026 +0 days VulDB entry created
04/22/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: access.redhat.com
Status: Not defined
CVE: CVE-2026-6862 (🔒)
GCVE (CVE): GCVE-0-2026-6862
GCVE (VulDB): GCVE-100-358961
Entryinfo
Created: 04/22/2026 17:29
Changes: 04/22/2026 17:29 (59)
Complete: 🔍
Cache ID: 99:B05:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸