{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26290 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26290 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26290 is a medium-severity authentication bypass vulnerability in ev.energy, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26290 and fix it if it is affected.\n\nWhat it is: CVE-2026-26290 is a medium-severity authentication bypass vulnerability in ev.energy, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-26290 in the wild and no public exploit code.\n\nAffected product: ev.energy. 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-26290/ (Markdown: https://insights.sbomify.com/CVE-2026-26290/index.md)","id":"CVE-2026-26290","markdown":"https://insights.sbomify.com/CVE-2026-26290/index.md","name":"CVE-2026-26290","record":{"aliases":["GHSA-cc2q-7r88-56q9"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["account_takeover","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"EV charging backend","requires_auth":"none","summary":"Attackers can hijack EV charging sessions or cause denial of service by exploiting predictable WebSocket session identifiers in the EV Energy backend.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"ev.energy","vendor":"ev.energy"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"The WebSocket backend uses charging station identifiers to uniquely \nassociate sessions but allows multiple endpoints to connect using the \nsame session identifier. This implementation results in predictable \nsession identifiers and enables session hijacking or shadowing, where \nthe most recent connection displaces the legitimate charging station and\n receives backend commands intended for that station. This vulnerability\n may allow unauthorized users to authenticate as other users or enable a\n malicious actor to cause a denial-of-service condition by overwhelming \nthe backend with valid session requests.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"EV Energy ev.energy Insufficient Session Expiration","id":"CVE-2026-26290","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in GROWI","id":"CVE-2026-26291"},"packages":[],"prev":{"headline":"Subnet Solutions PowerSYSTEM Center Incorrect Authorization","id":"CVE-2026-26289"},"products":["ev.energy"],"published":"2026-02-27","related":[{"cvss_score":9.3,"headline":"EV Energy ev.energy Missing Authentication for Critical Function","id":"CVE-2026-27772","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":8.7,"headline":"EV Energy ev.energy Improper Restriction of Excessive Authentication Attempts","id":"CVE-2026-24445","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":6.9,"headline":"EV Energy ev.energy Insufficiently Protected Credentials","id":"CVE-2026-25774","kev_date_added":null,"published":"2026-02-27"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-31","vendors":["EV Energy"]},"summary":"Attackers can hijack EV charging sessions or cause denial of service by exploiting predictable WebSocket session identifiers in the EV Energy backend.","url":"https://insights.sbomify.com/CVE-2026-26290/"}