Security readout for executives and security teams
Plain-English summary
This flaw affects EVerest EV charging software. An unauthenticated party near the charging communication path may cause the charger software to accept out-of-order ISO 15118-2 messages and prepare charging state incorrectly. Sources say it does not appear to enable actual current flow without additional state changes.
Executive priority
Treat this as a medium-priority operational safety and trust issue for EV charging deployments. It does not currently appear to allow actual charging current without further conditions, but affected production chargers should be inventoried and monitored while waiting for vendor remediation guidance.
Technical view
CVE-2026-24003 is a sequence state validation bypass in EVerest everest-core EvseV2G through 2025.12.1. ISO 15118-2 messages published to MQTT can bypass expected state verification, including authentication-related sequencing, and update context with illegitimate data. The advisory maps this to CWE-287 and CWE-863. CVSS is 4.3, AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
Likely exposure
Exposure is most likely for organizations using EVerest everest-core up to and including 2025.12.1 in EV charging systems where ISO 15118-2 and related MQTT message paths are reachable. The CVE has no CPEs listed, so confirm by software inventory rather than product matching alone.
Exploitation context
The published CVSS requires adjacent access, low complexity, no privileges, and no user interaction. The source bundle does not show CISA KEV listing or active exploitation. Impact is described as integrity-only and limited by the charger remaining in WaitingForAuthentication for contactor closure.
Researcher notes
The key nuance is impact boundary. The advisory says authorization is separate, EVSEManager cannot leave WaitingForAuthentication through ISO 15118-2 communication, and contactor closure does not appear possible through the described path. No fixed versions were available at publication.
Mitigation direction
- Check the GitHub advisory and EVerest project guidance for updates or patches.
- Identify and prioritize affected everest-core deployments through version inventory.
- Avoid production exposure of affected builds where practical until vendor guidance is available.
- Review compensating controls around ISO 15118-2 and MQTT access paths.
Validation and detection
- Confirm everest-core version is 2025.12.1 or earlier.
- Determine whether EvseV2G and ISO 15118-2 functionality are enabled.
- Review architecture for MQTT paths handling ISO 15118-2 messages.
- Check logs for abnormal out-of-sequence charging state transitions.
- Track the vendor advisory for fixed-version availability.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-24003 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/EVerest/everest-core/security/advisories/GHSA-9vv5-67cv-9crqCVE reference · x_refsource_CONFIRM
- https://github.com/EVerest/everest-core/blob/main/modules/EVSE/EvseV2G/iso_server.cpp#L44CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.