EVE: SSH as Root Unlockable Without Triggering Measured Boot

Exploitation

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

CVSS

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

EPSS

• CVE-2023-43631: 0.17% estimated exploitation activity in the next 30 days; percentile 6.40 (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 On boot, the Pillar container checks for /config/authorizedkeys. If present with a valid public key, it enables SSH on port 22 with root login. The /config partition is not protected by measured boot, is mutable and unencrypted. This enables an attacker with physical access to the device to take out the disk, modify the /config partition using a separate server, then insert it, without the inserted key being flagged as an integrity voilation my measured boot and remote attestation. Patches Patched in 9.4.3-lts Workarounds None (apart from preventing physical access to the device)

Published by the source

4 Feb 2026, 20:46 UTC

Last modified by the source

4 Feb 2026, 20:46 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3mq9-xhgq-r7gj

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

# Patch Next advisory brief: CVE-2023-43631

Advisory: EVE: SSH as Root Unlockable Without Triggering Measured Boot
IDs: CVE-2023-43631, GHSA-3mq9-xhgq-r7gj
Record: https://patchnext.com/advisories/cve-2023-43631 (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 5.9)
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-20220708121648-5fef4d92e758. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lf-edge/eve: affected < 0.0.0-20220708121648-5fef4d92e758; fixed in 0.0.0-20220708121648-5fef4d92e758

## 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-3mq9-xhgq-r7gj (GitHub-reviewed advisory GHSA-3mq9-xhgq-r7gj lists affected ranges: Go github.com/lf-edge/eve >=0 <0.0.0-20220708121648-5fef4d92e758)

Commands are suggestions: review each one before running it.