{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-44104 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44104 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44104 is a critical 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-44104 and fix it if it is affected.\n\nWhat it is: CVE-2026-44104 is a critical 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-44104 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-44104/ (Markdown: https://insights.sbomify.com/CVE-2026-44104/index.md)","id":"CVE-2026-44104","markdown":"https://insights.sbomify.com/CVE-2026-44104/index.md","name":"CVE-2026-44104","record":{"aliases":["GHSA-fvfc-m52v-j2p2"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"EV charging controller","requires_auth":"none","summary":"An unauthenticated remote attacker can install modified firmware on Phoenix Contact charging controllers due to missing cryptographic signature verification, leading to full system compromise.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The firmware update process for the basemodule of the charging controller only validates the\nCRC32 checksum without cryptographic signature verification. This allows an unauthenticated remote attacker to install a modified firmware, resulting in full system compromise.","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":"ControllerAgent does not perform validation of firmware","id":"CVE-2026-44104","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cleartext password in logs","id":"CVE-2026-44105"},"packages":[],"prev":{"headline":"JupiCore does not perform validation of firmware","id":"CVE-2026-44103"},"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":"total"},"state":"PUBLISHED","updated":"2026-07-30","vendors":["Phoenix Contact"]},"summary":"An unauthenticated remote attacker can install modified firmware on Phoenix Contact charging controllers due to missing cryptographic signature verification, leading to full system compromise.","url":"https://insights.sbomify.com/CVE-2026-44104/"}