{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68133 exists.","fix":"No fix has been published for CVE-2025-68133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68133 is a high-severity denial of service 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-68133 and fix it if it is affected.\n\nWhat it is: CVE-2025-68133 is a high-severity denial of service 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68133 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-2025-68133/ (Markdown: https://insights.sbomify.com/CVE-2025-68133/index.md)","id":"CVE-2025-68133","markdown":"https://insights.sbomify.com/CVE-2025-68133/index.md","name":"CVE-2025-68133","record":{"aliases":["GHSA-mv3w-pp85-5h7c"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charging software","requires_auth":"none","summary":"Attackers can cause denial of service in EVerest EV charging software by exhausting system resources through unlimited TCP connections.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"everest","vendor":"linuxfoundation"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"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.","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's unlimited connections can lead to DoS through operating system resource exhaustion","id":"CVE-2025-68133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"EVerest's use of assert functions can potentially lead to denial of service","id":"CVE-2025-68134"},"packages":[],"prev":{"headline":"EVerest has out-of-bounds read in DZG_GSH01 SLIP CRC parser that can crash powermeter driver","id":"CVE-2025-68132"},"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"}],"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-01-21","vendors":["EVerest"]},"summary":"Attackers can cause denial of service in EVerest EV charging software by exhausting system resources through unlimited TCP connections.","url":"https://insights.sbomify.com/CVE-2025-68133/"}