Cyber Resilience

CVE-2026-27828

Memory Safety in Linuxfoundation Everest ≤ 2026.02.0

Memory Safety
Published
26 March 2026
Modified
31 March 2026
Patch / advisory
View advisory
CVSS Score v4 5.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0029 21th percentile
Risk Priority 31 floored blend · peak EPSS

Summary

CVE-2026-27828 is a medium-severity Use After Free (CWE-416) vulnerability in Linuxfoundation Everest. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-27828 is a use-after-free vulnerability (CWE-416) in the EVerest EV charging software stack, affecting versions prior to 2026.02.0. The flaw resides in the ISO15118_chargerImpl::handle_session_setup function, which attempts to use the v2g_ctx object after it has been freed, such as during ISO15118 initialization failures (e.g., absence of an IPv6 link-local address). This impacts the EVSE process within the stack.

An attacker with MQTT access can remotely exploit the vulnerability by issuing a session_setup command while v2g_ctx has been released, causing a crash of the EVSE process and resulting in a denial of service. The CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects network accessibility, low attack complexity, no required privileges or user interaction, and high availability impact with no confidentiality or integrity effects.

The GitHub security advisory at https://github.com/EVerest/EVerest/security/advisories/GHSA-5g3v-qc79-qqwr documents the issue, noting that version 2026.02.0 contains a patch to resolve the use-after-free condition.

EU & UK References

Vulnerability Data

EVerest is an EV charging software stack. Prior to version 2026.02.0, ISO15118_chargerImpl::handle_session_setup uses v2g_ctx after it has been freed when ISO15118 initialization fails (e.g., no IPv6 link-local address). The EVSE process can be crashed remotely by an attacker with MQTT…

more

access who issues a session_setup command while v2g_ctx has been released. Version 2026.02.0 contains a patch.

CWE(s)
CWE-416

Related Threats

MITRE ATT&CK Enterprise Techniques

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-27813Same product: Linuxfoundation Everest
CVE-2026-26071Same product: Linuxfoundation Everest
CVE-2024-31583Same vendor: Linuxfoundation
CVE-2025-26681Shared CWE-416
CVE-2025-48543Shared CWE-416
CVE-2026-54127Shared CWE-416
CVE-2026-50323Shared CWE-416
CVE-2024-38078Shared CWE-416
CVE-2025-21929Shared CWE-416
CVE-2026-53025Shared CWE-416

Affected Assets

linuxfoundation
everest
≤ 2026.02.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.4.3

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover use-after-free bugs through dynamic analysis or fuzzing.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require memory-safe constructs or languages that structurally avoid introducing use-after-free.

SC-39 Process Isolation partial match

Process isolation confines the blast radius of use-after-free memory corruption to a single execution domain.

SI-16 Memory Protection partial match

Memory protection controls limit exploitation impact by blocking unauthorized code execution from dangling pointers.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly incorporate memory-safety tooling and reviews that prevent most use-after-free defects.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.

PR.PS-02 partial match
prevents

Routine patching removes known use-after-free instances after they have been introduced in released software.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect use-after-free bugs before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates memory-safety practices that reduce use-after-free defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-management rules that mitigate use-after-free.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include memory-safety design choices that limit use-after-free exposure.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe avoidance of use-after-free patterns.

A.8.32 Change management partial match
prevents

Change-management processes help ensure memory-safety fixes are deployed consistently.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248592 OL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416
RHEL 8 (1 rule)
  • V-230279 RHEL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416
RHEL 9 (1 rule)
  • V-257794 RHEL 9 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-416

References