Vulnerabilities
Summary — last 7 days
New vulnerabilities2,739▲ 36 vs. last week
Critical / high1,474▲ 366 vs. last week
New active exploitation (KEV)7▼ 3 vs. last week
Unscored (no CVSS)62▼ 464 vs. last week
12 results, sorted by published date (most recent first)
| CVE | Status | Severity | EPSS | Active exploitation | Affected technologies | Published ▼ | Modified | Description |
|---|---|---|---|---|---|---|---|---|
| Modified | High (8.6) | 0.22% | — | Pengutronix Barebox | 5/11/2026 | 7/18/2026 | 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… | |
| Modified | Medium (6.9) | 0.18% | — | Pengutronix Barebox | 5/11/2026 | 7/18/2026 | barebox version prior to 2026.04.0 contains a denial-of-service vulnerability in ext4 directory parsing in fs/ext4/ext4_common.c where the ext4fs_iterate_dir() function fails to validate that directory entry length values are non-zero. Attackers can supply a malicious ext4 filesystem image with a crafted directory… | |
| Modified | Medium (6.9) | 0.22% | — | Pengutronix Barebox | 5/11/2026 | 7/18/2026 | barebox prior to version 2026.04.0 contains out-of-bounds read vulnerabilities in ext4 extent parsing due to missing validation of the eh_entries field against buffer capacity in fs/ext4/ext4_common.c. Attackers can supply a malicious ext4 filesystem image via USB, SD card, or network boot to trigger heap… | |
| Modified | High (7.1) | 0.38% | — | Pengutronix Barebox | 5/11/2026 | 7/18/2026 | barebox prior to version 2026.04.0 contains an out-of-bounds read vulnerability in DHCP option parsing within the dhcp_message_type() function that fails to verify the options pointer remains within received packet bounds. An attacker on the same broadcast domain can send a crafted DHCP Offer or ACK packet without a… | |
| Analyzed | High (8.2) | 0.12% | — | Pengutronix Barebox | 3/20/2026 | 9/11/2026 | barebox is a bootloader. In barebox from version 2016.03.0 to before version 2026.03.1 (and the corresponding backport to 2025.09.3), an attacker could exploit a FIT signature verification vulnerability to trick the bootloader into booting different images than those that were verified as part of a signed… | |
| Deferred | High (7.1) | 0.29% | — | Pengutronix BareboxAI | 2/19/2025 | 6/17/2026 | In barebox before 2025.01.0, ext4fs_read_symlink has an integer overflow for zalloc (adding one to an le32 variable) via a crafted ext4 filesystem with an inode size of 0xffffffff, resulting in a malloc of zero and resultant memory overwrite, a related issue to CVE-2024-57256. | |
| Deferred | High (7.1) | 0.29% | — | Pengutronix BareboxAI | 2/19/2025 | 6/17/2026 | In barebox before 2025.01.0, request2size in common/dlmalloc.c has an integer overflow, a related issue to CVE-2024-57258. | |
| Modified | High (7.5) | 1.5% | — | Pengutronix Barebox | 8/2/2021 | 6/17/2026 | common/password.c in Pengutronix barebox through 2021.07.0 leaks timing information because strncmp is used during hash comparison. | |
| Modified | High (7.5) | 1.5% | — | Pengutronix Barebox | 8/2/2021 | 6/17/2026 | crypto/digest.c in Pengutronix barebox through 2021.07.0 leaks timing information because memcmp is used during digest verification. | |
| Modified | Critical (9.1) | 1.2% | — | Pengutronix Barebox | 6/7/2020 | 6/17/2026 | Pengutronix Barebox through v2020.05.0 has an out-of-bounds read in nfs_read_reply in net/nfs.c because a field of an incoming network packet is directly used as a length field without any bounds check. | |
| Modified | Critical (9.8) | 2.1% | — | Pengutronix Barebox | 9/5/2019 | 6/17/2026 | Pengutronix barebox through 2019.08.1 has a remote buffer overflow in nfs_readlink_req in fs/nfs.c because a length field is directly used for a memcpy. | |
| Modified | Critical (9.8) | 2.1% | — | Pengutronix Barebox | 9/5/2019 | 6/17/2026 | Pengutronix barebox through 2019.08.1 has a remote buffer overflow in nfs_readlink_reply in net/nfs.c because a length field is directly used for a memcpy. |