{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27816 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-27816 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27816 is a medium-severity memory corruption vulnerability in everest-core, published on 26 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27816 and fix it if it is affected.\n\nWhat it is: CVE-2026-27816 is a medium-severity memory corruption vulnerability in everest-core, published on 26 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-27816 in the wild and no public exploit code.\n\nAffected product: everest-core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-27816/ (Markdown: https://insights.sbomify.com/CVE-2026-27816/index.md)","id":"CVE-2026-27816","markdown":"https://insights.sbomify.com/CVE-2026-27816/index.md","name":"CVE-2026-27816","record":{"aliases":["GHSA-gq54-j8f4-xj8c"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["denial_of_service","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charging software","requires_auth":"none","summary":"Attackers can corrupt EVSE state or crash the process via oversized MQTT payloads due to missing bounds checking in EVerest's ISO15118 implementation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"everest","vendor":"linuxfoundation"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS: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","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"EVerest's ISO15118 update_energy_transfer_modes overflow can corrupt EVSE state","id":"CVE-2026-27816","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"TerriaJS-Server has a domain validation bypass vulnerability in its proxy allowlist","id":"CVE-2026-27818"},"packages":[],"prev":{"headline":"EVerest: ISO15118 session_setup payment options overflow can corrupt EVSE state","id":"CVE-2026-27815"},"products":["everest-core"],"published":"2026-03-26","related":[{"cvss_score":8.8,"headline":"EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload","id":"CVE-2026-22790","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.4,"headline":"EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing","id":"CVE-2026-22593","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.4,"headline":"EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ","id":"CVE-2026-23995","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.4,"headline":"EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop","id":"CVE-2025-68137","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":8.2,"headline":"EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio","id":"CVE-2026-33009","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":7.5,"headline":"EVerest has OOB via EVSE ID Indexing Mismatch in OCPP 2.0.1 UpdateAllowedEnergyTransferModes","id":"CVE-2026-26008","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":7.4,"headline":"EVerest's unlimited connections can lead to DoS through operating system resource exhaustion","id":"CVE-2025-68133","kev_date_added":null,"published":"2026-01-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-26","vendors":["EVerest"]},"summary":"Attackers can corrupt EVSE state or crash the process via oversized MQTT payloads due to missing bounds checking in EVerest's ISO15118 implementation.","url":"https://insights.sbomify.com/CVE-2026-27816/"}