Approved changes feed: RSS · Atom
cpe:2.3:o:linuxfoundation:everest:*:*:*:*:*:*:*:*
part: o version: * update: *
| Vendor | Linuxfoundation (4b459c90-8cdb-5268-beb4-b69b5fe74234) |
|---|---|
| Product | Everest (7ca736b5-dc8b-59b1-9040-3a3b783f043f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-33015 |
vulnerable | 2026-06-08 07:57:18.463540 |
EVerest has RemoteStop Bypass via BCB Toggle Session Restart
MEDIUM (5.2)
EVerest is an EV charging software stack. Prior to version 2026.02.0, even immediately after CSMS performs a RemoteStop (StopTransaction), the EVSE can return to `PrepareCharging` via the EV's BCB toggle, allowing session restart. This breaks the irreversibility of remote stop and can bypass operational/billing/safety controls. Version 2026.02.0 contains a patch.
Published: 2026-03-26T16:42:50.695Z
Updated: 2026-03-26T17:35:07.268Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33014 |
vulnerable | 2026-06-08 07:57:18.463142 |
EVerest has Delayed Authorization Response Bypasses Termination After RemoteStop
MEDIUM (5.2)
EVerest is an EV charging software stack. Prior to version 2026.02.0, during RemoteStop processing, a delayed authorization response restores `authorized` back to true, defeating the `stop_transaction()` call condition on PowerOff events. As a result, the transaction can remain open even after a remote stop. Version 2026.02.0 contains a patch.
Published: 2026-03-26T16:40:40.062Z
Updated: 2026-03-26T18:24:11.044Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33009 |
vulnerable | 2026-06-08 07:57:18.456113 |
EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio
HIGH (8.2)
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to C++ UB (potential memory corruption). This is triggered by an MQTT `everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging` message and results in `Charger::shared_context` / `internal_context` accessed concurrently without lock. Version 2026.02.0 contains a patch.
Published: 2026-03-26T16:39:30.268Z
Updated: 2026-03-28T02:26:05.370Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-29044 |
vulnerable | 2026-06-08 07:55:16.024723 |
EVerest: Charging Continues When WithdrawAuthorization Is Processed Before TransactionStarted
MEDIUM (5)
EVerest is an EV charging software stack. Prior to version 2026.02.0, when WithdrawAuthorization is processed before the TransactionStarted event, AuthHandler determines `transaction_active=false` and only calls `withdraw_authorization_callback`. This path ultimately calls `Charger::deauthorize()`, but no actual stop (StopTransaction) occurs in the Charging state. As a result, authorization withdrawal can be defeated by timing, allowing charging to continue. Version 2026.02.0 contains a patch.
Published: 2026-03-26T16:37:33.230Z
Updated: 2026-03-26T18:50:00.493Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27828 |
vulnerable | 2026-06-08 07:55:14.024815 |
EVerest: ISO15118 session_setup use-after-free can crash EVSE process
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 access who issues a session_setup command while v2g_ctx has been released. Version 2026.02.0 contains a patch.
Published: 2026-03-26T16:34:23.623Z
Updated: 2026-03-27T14:43:59.252Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27816 |
vulnerable | 2026-06-08 07:55:13.933670 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27815 |
vulnerable | 2026-06-08 07:55:13.933127 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27814 |
vulnerable | 2026-06-08 07:55:13.932576 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27813 |
vulnerable | 2026-06-08 07:55:13.932070 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-26074 |
vulnerable | 2026-06-08 07:53:20.771880 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-26073 |
vulnerable | 2026-06-08 07:53:20.771519 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-26072 |
vulnerable | 2026-06-08 07:53:20.771147 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-26071 |
vulnerable | 2026-06-08 07:53:20.770867 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-26070 |
vulnerable | 2026-06-08 07:53:20.770542 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-26008 |
vulnerable | 2026-06-08 07:53:20.702706 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-24003 |
vulnerable | 2026-06-08 07:51:16.514135 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-23995 |
vulnerable | 2026-06-08 07:51:16.503767 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-23955 |
vulnerable | 2026-06-08 07:51:16.457348 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22790 |
vulnerable | 2026-06-08 07:51:13.924074 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22593 |
vulnerable | 2026-06-08 07:51:13.264839 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68141 |
vulnerable | 2026-06-08 07:41:20.865209 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68140 |
vulnerable | 2026-06-08 07:41:20.864847 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68139 |
vulnerable | 2026-06-08 07:41:20.864455 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68137 |
vulnerable | 2026-06-08 07:41:20.861116 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68136 |
vulnerable | 2026-06-08 07:41:20.860864 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68135 |
vulnerable | 2026-06-08 07:41:20.860403 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68134 |
vulnerable | 2026-06-08 07:41:20.860036 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68133 |
vulnerable | 2026-06-08 07:41:20.859650 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68132 |
vulnerable | 2026-06-08 07:41:20.859179 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.