EVE Has Partially Predetermined Vault Key

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.7 · CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2023-43637: 0.14% estimated exploitation activity in the next 30 days; percentile 3.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The deriveVaultKey function calls retrieveCloudKey which always returns "foobarfoobarfoobarfoobarfoobarfo". When merged with the randomly generated 32-byte key using mergeKeys (16 bytes from each), the last 16 bytes are always "arfoobarfoobarfo". This enables an attacker with physical access to the EVE-OS device to attempt to brute force the remaining 128 bits of key. Patches Fixed in 7.10 and 8.12.1-lts Workarounds None

Published by the source

4 Feb 2026, 23:21 UTC

Last modified by the source

4 Feb 2026, 23:21 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g7vp-j25f-h34p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-43637

Advisory: EVE Has Partially Predetermined Vault Key
IDs: CVE-2023-43637, GHSA-g7vp-j25f-h34p
Record: https://patchnext.com/advisories/cve-2023-43637 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/lf-edge/eve 0.0.0-20220310190112-c0c966dc31e2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lf-edge/eve: affected < 0.0.0-20220310190112-c0c966dc31e2; fixed in 0.0.0-20220310190112-c0c966dc31e2

## Suggested inspection (read-only)
- Go github.com/lf-edge/eve: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lf-edge/eve.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g7vp-j25f-h34p (GitHub-reviewed advisory GHSA-g7vp-j25f-h34p lists affected ranges: Go github.com/lf-edge/eve >=0 <0.0.0-20220310190112-c0c966dc31e2)

Commands are suggestions: review each one before running it.