{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33014 exists.","fix":"No fix has been published for CVE-2026-33014 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33014 is a medium-severity 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-33014 and fix it if it is affected.\n\nWhat it is: CVE-2026-33014 is a medium-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33014 exists.\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-33014/ (Markdown: https://insights.sbomify.com/CVE-2026-33014/index.md)","id":"CVE-2026-33014","markdown":"https://insights.sbomify.com/CVE-2026-33014/index.md","name":"CVE-2026-33014","record":{"aliases":["GHSA-43xm-5m3v-52hm"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charging software","requires_auth":"none","summary":"Attackers can keep EV charging transactions open after remote stop commands by exploiting delayed authorization responses, requiring a software patch.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"everest","vendor":"linuxfoundation"}],"cvss":{"score":5.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"EVerest has Delayed Authorization Response Bypasses Termination After RemoteStop","id":"CVE-2026-33014","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"EVerest has RemoteStop Bypass via BCB Toggle Session Restart","id":"CVE-2026-33015"},"packages":[],"prev":{"headline":"Micronaut vulnerable to DoS via crafted form-urlencoded body binding with descending array indices","id":"CVE-2026-33013"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-26","vendors":["EVerest"]},"summary":"Attackers can keep EV charging transactions open after remote stop commands by exploiting delayed authorization responses, requiring a software patch.","url":"https://insights.sbomify.com/CVE-2026-33014/"}