CVE-2023-43635: EVE Seals Vault Key With SHA1 PCRs
Impact The vault key is sealed using SHA1 PCRs instead of SHA256 PCRs Thus an attacker with physical access to an EVE-OS device can try to brute force creating a kernel or rootfs image which produces the same SHA1 PCR but with malicious content. Patches Fixed in 9.4.3-lts and 10.1.0 Workarounds None
Published Feb 4, 2026
Affected packages
github.com/lf-edge/eve
- Ecosystem
- Go
- Affected
- < 0.0.0-20230519072751-977f42b07fa9
- Fixed in
- 0.0.0-20230519072751-977f42b07fa9
- Check
go list -m github.com/lf-edge/eve
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The vault key is sealed using SHA1 PCRs instead of SHA256 PCRs
Thus an attacker with physical access to an EVE-OS device can try to brute force creating a kernel or rootfs image which produces the same SHA1 PCR but with malicious content.
Patches
Fixed in 9.4.3-lts and 10.1.0
Workarounds
None
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2023-43630
EVE Doesn't Measure Config Partition From 2 Fronts
medium5.2Feb 4, 2026CVE-2023-43631
EVE: SSH as Root Unlockable Without Triggering Measured Boot
medium5.9Feb 4, 2026CVE-2023-43632
EVE Freely Allocates Buffer on The Stack With Data From Socket
medium6.5Feb 4, 2026CVE-2023-43633
EVE's Debug Functions Unlockable Without Triggering Measured Boot
medium5.9Feb 4, 2026CVE-2023-43634
EVE Doesn't Protect Config Partition with Measured Boot
medium5.9Feb 4, 2026CVE-2023-43637
EVE Has Partially Predetermined Vault Key
medium6.7Feb 4, 2026
