{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-68140 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-68140 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68140 is a medium-severity authentication bypass vulnerability in everest-core, published on 21 Jan 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-2025-68140 and fix it if it is affected.\n\nWhat it is: CVE-2025-68140 is a medium-severity authentication bypass vulnerability in everest-core, published on 21 Jan 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-2025-68140 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-2025-68140/ (Markdown: https://insights.sbomify.com/CVE-2025-68140/index.md)","id":"CVE-2025-68140","markdown":"https://insights.sbomify.com/CVE-2025-68140/index.md","name":"CVE-2025-68140","record":{"aliases":["GHSA-w385-3jwp-x47x"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charging software","requires_auth":"none","summary":"Attackers can bypass session verification by using a null session ID, allowing unauthorized MQTT message emission and session context updates in EVerest.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"everest","vendor":"linuxfoundation"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"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.","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 allows null session ID to bypass session ID verification","id":"CVE-2025-68140","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"EVerest vulnerable to null pointer dereference during DC_ChargeLoopRes document deserialization","id":"CVE-2025-68141"},"packages":[],"prev":{"headline":"Business logic in everest-core","id":"CVE-2025-68139"},"products":["everest-core"],"published":"2026-01-21","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-01-22","vendors":["EVerest"]},"summary":"Attackers can bypass session verification by using a null session ID, allowing unauthorized MQTT message emission and session context updates in EVerest.","url":"https://insights.sbomify.com/CVE-2025-68140/"}