{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-44102 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44102 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44102 is a medium-severity vulnerability in Phoenix Contact CHARX SEC-3000, published on 30 Jul 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-44102 and fix it if it is affected.\n\nWhat it is: CVE-2026-44102 is a medium-severity vulnerability in Phoenix Contact CHARX SEC-3000, published on 30 Jul 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-44102 in the wild and no public exploit code.\n\nAffected product: Phoenix Contact CHARX SEC-3000. 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-44102/ (Markdown: https://insights.sbomify.com/CVE-2026-44102/index.md)","id":"CVE-2026-44102","markdown":"https://insights.sbomify.com/CVE-2026-44102/index.md","name":"CVE-2026-44102","record":{"aliases":["GHSA-qrwj-j5f7-cjgm"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"EV charging controller","requires_auth":"none","summary":"An unauthenticated attacker can access a temporary firmware file due to a race condition in the cleanup process, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"An unauthenticated remote attacker can trigger a firmware update download via the OCPP backend by supplying an invalid firmware file. This will cause the file to remain accessible for a short period before it is deleted due to improper locking during the cleanup process.","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":"OCPP Firmware download is not properly locked","id":"CVE-2026-44102","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"JupiCore does not perform validation of firmware","id":"CVE-2026-44103"},"packages":[],"prev":{"headline":"OCPP reconfiguration vulnerability","id":"CVE-2026-44101"},"products":["CHARX SEC-3000","CHARX SEC-3050","CHARX SEC-3100","CHARX SEC-3150"],"published":"2026-07-30","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-30","vendors":["Phoenix Contact"]},"summary":"An unauthenticated attacker can access a temporary firmware file due to a race condition in the cleanup process, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-44102/"}