How severe is GHSA-3mq9-xhgq-r7gj?

GHSA-3mq9-xhgq-r7gj has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-3mq9-xhgq-r7gj?

GHSA-3mq9-xhgq-r7gj affects the following packages: github.com/lf-edge/eve (Go). Ecosystems affected: Go.

How do I fix GHSA-3mq9-xhgq-r7gj?

Update github.com/lf-edge/eve to 0.0.0-20220708121648-5fef4d92e758 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3mq9-xhgq-r7gj is resolved across your whole dependency graph.

How do I detect GHSA-3mq9-xhgq-r7gj in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lf-edge/eve, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3mq9-xhgq-r7gj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-3mq9-xhgq-r7gj actively exploited in the wild?

No public exploit code has been indexed for GHSA-3mq9-xhgq-r7gj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3mq9-xhgq-r7gj?

GHSA-3mq9-xhgq-r7gj has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 6th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3mq9-xhgq-r7gj?

GHSA-3mq9-xhgq-r7gj is classified as CWE-522 (CWE-522), CWE-922 (CWE-922). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3mq9-xhgq-r7gj published, and has it been updated?

GHSA-3mq9-xhgq-r7gj was published on February 4, 2026 and was last updated on February 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

EVE: SSH as Root Unlockable Without Triggering Measured BootGHSA-3mq9-xhgq-r7gj

MEDIUMFix: lf-edge/eve@5fef4d9

GHSA-3mq9-xhgq-r7gj is a medium-severity (CVSS 5.9) CWE-522 vulnerability in github.com/lf-edge/eve. A fix is available for github.com/lf-edge/eve — see the affected versions and patch details below.

Also known asCVE-2023-43631GO-2026-4418

Published

Feb 4, 2026

Updated

Feb 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3mq9-xhgq-r7gj.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs6th percentile — riskier than 6% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/lf-edge/eve

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

On boot, the Pillar eve container checks for the existence and content of “/config/authorized_keys”.

If the file is present, and contains a supported public key, the container will go on to open port 22 and enable sshd with the given keys as the authorized keys for root login.

An attacker could easily add their own keys and gain full control over the system without triggering the “measured boot” mechanism implemented by EVE OS, and without marking the device as “UUD” (“Unknown Update Detected”).

This is because the “/config” partition is not protected by “measured boot”, it is mutable, and it is not encrypted in any way.

An attacker can gain full control over the device without changing the PCR values, thus not triggering the “measured boot” mechanism, and having full access to the vault.

Note:

This issue was partially fixed in these commits (after disclosure to Zededa), where the config partition measurement was added to PCR13:

• aa3501d6c57206ced222c33aea15a9169d629141

• 5fef4d92e75838cc78010edaed5247dfbdae1889.

This issue was made viable in version 9.0.0 when the calculation was moved to PCR14 but it was not included in the measured boot.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/lf-edge/eve`	all versions	0.0.0-20220708121648-5fef4d92e758`go get github.com/lf-edge/eve@v0.0.0-20220708121648-5fef4d92e758`

Affected Products

1 product · 2 configurations

edge virtualization enginelinuxfoundation

≥ 9.0.0 && < 9.5.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lf-edge/eve, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/lf-edge/eve to 0.0.0-20220708121648-5fef4d92e758 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3mq9-xhgq-r7gj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact On boot, the Pillar container checks for /config/authorized_keys. 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