Vulnerability database
Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.
31 results
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-33015 · Other software · EVerest · reported by GitHubMedium 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.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-33014 · Other software · EVerest · reported by GitHubMedium 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.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-33009 · Other software · EVerest · reported by GitHubHigh 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.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-29044 · Other software · EVerest · reported by GitHubMedium 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.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-27828 · Other software · EVerest · reported by GitHubMedium 5.5
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.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-27816 · Other software · EVerest · reported by GitHubMedium 5.5
EVerest is an EV charging software stack. Prior to versions to 2026.02.0, ISO15118_chargerImpl::handle_update_energy_transfer_modes copies a variable-length list into a fixed-size array of length 6 without bounds checking. With schema validation disabled by default, oversized MQTT Cmd payloads can trigger out-of-bounds writes and corrupt adjacent EVSE state or crash the process. Version 2026.02.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-27815 · Other software · EVerest · reported by GitHubMedium 5.5
EVerest is an EV charging software stack. Prior to versions to 2026.02.0, ISO15118_chargerImpl::handle_session_setup copies a variable-length payment_options list into a fixed-size array of length 2 without bounds checking. With schema validation disabled by default, oversized MQTT Cmd payloads can trigger out-of-bounds writes and corrupt adjacent EVSE state or crash the process. Version 2026.02.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-27814 · Other software · EVerest · reported by GitHubMedium 4.2
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race (C++ UB) triggered by an A 1-phase ↔ 3-phase switch request (`ac_switch_three_phases_while_charging`) during charging/waiting executes concurrently with the state machine loop. Version 2026.02.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-27813 · Other software · EVerest · reported by GitHubMedium 5.3
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to use-after-free. This is triggered by EV plug-in/unplug and RFID/RemoteStart/OCPP authorization events (or delayed authorization response). Version 2026.2.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-26074 · Other software · EVerest · reported by GitHubHigh 7
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::map<std::queue>` corruption. The trigger is CSMS GetLog/UpdateFirmware request (network) with an EVSE fault event (physical). This results in TSAN reports concurrent access (data race) to `event_queue`. Version 2026.2.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-26073 · Other software · EVerest · reported by GitHubMedium 5.9
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::queue`/`std::deque` corruption. The trigger is powermeter public key update and EV session/error events (while OCPP not started). This results in a TSAN data race report and an ASAN/UBSAN misaligned address runtime error being observed. Version 2026.02.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-26072 · Other software · EVerest · reported by GitHubMedium 4.2
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to `std::map<std::optional>` concurrent access (container/optional corruption possible). The trigger is EV SoC update with powermeter periodic update and unplugging/SessionFinished status. Version 2026.02.0 patches the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-26071 · Other software · EVerest · reported by GitHubMedium 4.2
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to `std::string` concurrent access. with heap-use-after-free possible. This is triggered by EVCCID update (EV/ISO15118) and OCPP session/authorization events. Version 2026.02.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-26070 · Other software · EVerest · reported by GitHubMedium 4.6
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to `std::map<std::optional>` concurrent access (container/optional corruption possible). The trigger is an EV SoC update with powermeter periodic update and unplugging/SessionFinished state. Version 2026.2.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-26008 · Other software · EVerest · reported by GitHubHigh 7.5
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have an out-of-bounds access (std::vector) that leads to possible remote crash/memory corruption. This is because the CSMS sends UpdateAllowedEnergyTransferModes over the network. Version 2026.2.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-23995 · Other software · EVerest · reported by GitHubHigh 8.4
EVerest is an EV charging software stack. Prior to version 2026.02.0, stack-based buffer overflow in CAN interface initialization: passing an interface name longer than IFNAMSIZ (16) to CAN open routines overflows `ifreq.ifr_name`, corrupting adjacent stack data and enabling potential code execution. A malicious or misconfigured interface name can trigger this before any privilege checks. Version 2026.02.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-22790 · Other software · EVerest · reported by GitHubHigh 8.8
EVerest is an EV charging software stack. Prior to version 2026.02.0, `HomeplugMessage::setup_payload` trusts `len` after an `assert`; in release builds the check is removed, so oversized SLAC payloads are `memcpy`'d into a ~1497-byte stack buffer, corrupting the stack and enabling remote code execution from network-provided frames. Version 2026.02.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 26, 2026EVerest is an EV charging software stack.CVE-2026-22593 · Other software · EVerest · reported by GitHubHigh 8.4
EVerest is an EV charging software stack. Prior to version 2026.02.0, an off-by-one check in IsoMux certificate filename handling causes a stack-based buffer overflow when a filename length equals `MAX_FILE_NAME_LENGTH` (100). A crafted filename in the certificate directory can overflow `file_names[idx]`, corrupting stack state and enabling potential code execution. Version 2026.02.0 contains a patch.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 26, 2026EVerest is an EV charging software stack.CVE-2026-24003 · Other software · EVerest · reported by GitHubMedium 4.3
EVerest is an EV charging software stack. In versions up to and including 2025.12.1, it is possible to bypass the sequence state verification including authentication, and send requests that transition to forbidden states relative to the current one, thereby updating the current context with illegitimate data.cThanks to the modular design of EVerest, authorization is handled in a separate module and EVSEManager Charger internal state machine cannot transition out of the `WaitingForAuthentication` state through ISO 15118-2 communication. From this state, it was however possible through ISO 15118-2 messages which are published to the MQTT server to trick it into preparing to charge, and even to prepare to send current. The final requirement to actually send current to the EV was the closure of the contactors, which does not appear to be possible without leaving the `WaitingForAuthentication` state and leveraging ISO 15118-2 messages. As of time of publication, no fixed versions are available.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack.CVE-2026-23955 · Other software · EVerest · reported by GitHubMedium 4.2
EVerest is an EV charging software stack. Prior to version 2025.9.0, in several places, integer values are concatenated to literal strings when throwing errors. This results in pointers arithmetic instead of printing the integer value as expected, like most of interpreted languages. This can be used by malicious operator to read unintended memory regions, including the heap and the stack. Version 2025.9.0 fixes the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack.CVE-2025-68141 · Other software · EVerest · reported by GitHubHigh 7.4
EVerest is an EV charging software stack. Prior to version 2025.10.0, during the deserialization of a `DC_ChargeLoopRes` message that includes Receipt as well as TaxCosts, the vector `<DetailedTax>tax_costs` in the target `Receipt` structure is accessed out of bounds. This occurs in the method `template <> void convert(const struct iso20_dc_DetailedTaxType& in, datatypes::DetailedTax& out)` which leads to a null pointer dereference and causes the module to terminate. The EVerest processes and all its modules shut down, affecting all EVSE. Version 2025.10.0 fixes the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack.CVE-2025-68140 · Other software · EVerest · reported by GitHubMedium 4.3
EVerest is an EV charging software stack. Prior to version 2025.9.0, once the validity of the received V2G message has been verified, it is checked whether the submitted session ID matches the registered one. However, if no session has been registered, the default value is 0. Therefore, a message submitted with a session ID of 0 is accepted, as it matches the registered value. This could allow unauthorized and anonymous indirect emission of MQTT messages and communication with V2G messages handlers, updating a session context. Version 2025.9.0 fixes the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack.CVE-2025-68139 · Other software · EVerest · reported by GitHubMedium 4.3
EVerest is an EV charging software stack. In all versions up to and including 2025.12.1, the default value for `terminate_connection_on_failed_response` is `False`, which leaves the responsibility for session and connection termination to the EV. In this configuration, any errors encountered by the module are logged but do not trigger countermeasures such as session and connection reset or termination. This could be abused by a malicious user in order to exploit other weaknesses or vulnerabilities. While the default will stay at the setting that is described as potentially problematic in this reported issue, a mitigation is available by changing the `terminate_connection_on_failed_response` setting to `true`. However this cannot be set to this value by default since it can trigger errors in vehicle ECUs requiring ECU resets and lengthy unavailability in charging for vehicles. The maintainers judge this to be a much more important workaround then short-term unavailability of an EVSE, therefore this setting will stay at the current value.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack, and EVerest libocpp is a C++ implementation of the Open Charge Point Protocol.CVE-2025-68138 · Other software · EVerest · reported by GitHubMedium 4.7
EVerest is an EV charging software stack, and EVerest libocpp is a C++ implementation of the Open Charge Point Protocol. In libocpp prior to version 0.30.1, pointers returned by the `strdup` calls are never freed. At each connection attempt, the newly allocated memory area will be leaked, potentially causing memory exhaustion and denial of service. Version 0.30.1 fixes the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack.CVE-2025-68137 · Other software · EVerest · reported by GitHubHigh 8.3
EVerest is an EV charging software stack. Prior to version 2025.10.0, an integer overflow occurring in `SdpPacket::parse_header()` allows the current buffer length to be set to 7 after a complete header of size 8 has been read. The remaining length to read is computed using the current length subtracted by the header length which results in a negative value. This value is then interpreted as `SIZE_MAX` (or slightly less) because the expected type of the argument is `size_t`. Depending on whether the server is plain TCP or TLS, this leads to either an infinite loop or a stack buffer overflow. Version 2025.10.0 fixes the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack.CVE-2025-68136 · Other software · EVerest · reported by GitHubHigh 7.4
EVerest is an EV charging software stack. Prior to version 2025.10.0, once the module receives a SDP request, it creates a whole new set of objects like `Session`, `IConnection` which open new TCP socket for the ISO15118-20 communications and registers callbacks for the created file descriptor, without closing and destroying the previous ones. Previous `Session` is not saved and the usage of an `unique_ptr` is lost, destroying connection data. Latter, if the used socket and therefore file descriptor is not the last one, it will lead to a null pointer dereference. Version 2025.10.0 fixes the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack.CVE-2025-68135 · Other software · EVerest · reported by GitHubMedium 6.5
EVerest is an EV charging software stack. Prior to version 2025.10.0, C++ exceptions are not properly handled for and by the `TbdController` loop, leading to its caller and itself to silently terminates. Thus, this leads to a denial of service as it is responsible of SDP and ISO15118-20 servers. Version 2025.10.0 fixes the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack.CVE-2025-68134 · Other software · EVerest · reported by GitHubHigh 7.4
EVerest is an EV charging software stack. Prior to version 2025.10.0, the use of the `assert` function to handle errors frequently causes the module to crash. This is particularly critical because the manager shuts down all other modules and exits when any one of them terminates, leading to a denial of service. In a context where a manager handles multiple EVSE, this would also impact other users. Version 2025.10.0 fixes the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 21, 2026EVerest is an EV charging software stack.CVE-2025-68132 · Other software · EVerest · reported by GitHubLow 2.4
EVerest is an EV charging software stack. Prior to version 2025.12.0, `is_message_crc_correct` in the DZG_GSH01 powermeter SLIP parser reads `vec[vec.size()-1]` and `vec[vec.size()-2]` without checking that at least two bytes are present. Malformed SLIP frames on the serial link can reach `is_message_crc_correct` with `vec.size() < 2` (only via the multi-message path), causing an out-of-bounds read before CRC verification and `pop_back` underflow. Therefore, an attacker controlling the serial input can reliably crash the process. Version 2025.12.0 fixes the issue.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jan 20, 2026EVerest is an EV charging software stack.CVE-2025-68133 · Other software · EVerest · reported by GitHubHigh 7.4
EVerest is an EV charging software stack. In versions 2025.9.0 and below, an attacker can exhaust the operating system's memory and cause the module to terminate by initiating an unlimited number of TCP connections that never proceed to ISO 15118-2 communication. This is possible because a new thread is started for each incoming plain TCP or TLS socket connection before any verification occurs, and the verification performed is too permissive. The EVerest processes and all its modules shut down, affecting all EVSE functionality. This issue is fixed in version 2025.10.0.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 10, 2024EVerest is an EV charging software stack.CVE-2024-37310 · Other software · EVerest · reported by GitHubCritical 9
EVerest is an EV charging software stack. An integer overflow in the "v2g_incoming_v2gtp" function in the v2g_server.cpp implementation can allow a remote attacker to overflow the process' heap. This vulnerability is fixed in 2024.3.1 and 2024.6.0.
- Product
- everest-core
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.