Barebox up to 2026.04.0 EFI PE Loader efi/loader/pe.c VirtualAddress/size integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Barebox up to 2026.04.0. This affects an unknown part of the file efi/loader/pe.c of the component EFI PE Loader. Performing a manipulation of the argument VirtualAddress/size results in integer overflow. This vulnerability was named CVE-2026-34963. The attack needs to be approached locally. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Barebox up to 2026.04.0. This affects an unknown code of the file efi/loader/pe.c of the component EFI PE Loader. The manipulation of the argument VirtualAddress/size with an unknown input leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
barebox version prior to 2026.04.0 contains multiple memory-safety vulnerabilities in the EFI PE loader in efi/loader/pe.c where integer overflow in virtual image size computation using 32-bit arithmetic on section VirtualAddress and size values allows undersized heap allocation, and PE section loading logic fails to validate that PointerToRawData plus copied size remains within the PE file buffer. An attacker can supply a malicious EFI PE binary via TFTP, USB, SD card, or network boot to trigger heap buffer overflow or out-of-bounds read from heap memory, potentially achieving code execution in bootloader context.
The weakness was presented by Kazuma Matsumoto. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-34963 since 03/31/2026. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version 2026.04.0 eliminates this vulnerability. The upgrade is hosted for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-29347). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔒
CNA Base Score: 8.4
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Barebox 2026.04.0
Timeline
03/31/2026 CVE reserved05/12/2026 Advisory disclosed
05/12/2026 VulDB entry created
07/18/2026 VulDB entry last update
Sources
Advisory: github.comResearcher: Kazuma Matsumoto
Status: Confirmed
CVE: CVE-2026-34963 (🔒)
GCVE (CVE): GCVE-0-2026-34963
GCVE (VulDB): GCVE-100-362793
EUVD: 🔒
Entry
Created: 05/12/2026 04:00Updated: 07/18/2026 05:41
Changes: 05/12/2026 04:00 (78), 05/12/2026 04:49 (1), 07/18/2026 05:41 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.