{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-22539 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22539 is a medium-severity vulnerability in EFACEC QC 60/90/120, published on 7 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-2026-22539 and fix it if it is affected.\n\nWhat it is: CVE-2026-22539 is a medium-severity vulnerability in EFACEC QC 60/90/120, published on 7 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-2026-22539 in the wild and no public exploit code.\n\nAffected product: EFACEC QC 60/90/120. 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-22539/ (Markdown: https://insights.sbomify.com/CVE-2026-22539/index.md)","id":"CVE-2026-22539","markdown":"https://insights.sbomify.com/CVE-2026-22539/index.md","name":"CVE-2026-22539","record":{"aliases":["GHSA-5c9g-c5m4-vmrj"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charging station","requires_auth":"none","summary":"Unauthenticated attackers can obtain charger information via OCPP protocol requests due to missing authentication in service interactions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"S21sec","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"As the service interaction is performed without authentication, an attacker with some knowledge of the protocol could obtain information about the charger via OCPP v1.6.","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":"INFORMATION DISCLOSURE VIA CURL REQUESTS (OCPP)","id":"CVE-2026-22539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"DENIAL OF SERVICE VIA ARP PACKETS","id":"CVE-2026-22540"},"packages":[],"prev":{"headline":"INFORMATION DISCLOSURE WITHIN THE OPERATING SYSTEM","id":"CVE-2026-22537"},"products":["QC 60/90/120"],"published":"2026-01-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09","vendors":["EFACEC"]},"summary":"Unauthenticated attackers can obtain charger information via OCPP protocol requests due to missing authentication in service interactions.","url":"https://insights.sbomify.com/CVE-2026-22539/"}