{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-71449 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-71449 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-71449 is a critical vulnerability in Johnson Controls EasyIO FS32, published on 1 Oct 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-71449 and fix it if it is affected.\n\nWhat it is: CVE-2026-71449 is a critical vulnerability in Johnson Controls EasyIO FS32, published on 1 Oct 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-71449 in the wild and no public exploit code.\n\nAffected product: Johnson Controls EasyIO FS32. 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-71449/ (Markdown: https://insights.sbomify.com/CVE-2026-71449/index.md)","id":"CVE-2026-71449","markdown":"https://insights.sbomify.com/CVE-2026-71449/index.md","name":"CVE-2026-71449","record":{"aliases":["GHSA-w2h3-qvv9-248h"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"access control system","requires_auth":"none","summary":"An attacker can retrieve embedded sensitive data from Johnson Controls EasyIO FS32 devices due to a hard-coded cryptographic key.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jci","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:H/SI:H/SA:H/E:P","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":": Use of Hard-coded Cryptographic Key vulnerability in Johnson Controls EasyIO FS32 allows : Retrieve Embedded Sensitive Data.\n\nThis issue affects EasyIO FS32: before 3.0b63.","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":"Hardcoded credentials in EasyIO FS32","id":"CVE-2026-71449","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in EasyIO FS32","id":"CVE-2026-71451"},"packages":[],"prev":{"headline":"Auth bypass in EasyIO FS32","id":"CVE-2026-71448"},"products":["EasyIO FS32"],"published":"2026-10-01","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-10-02","vendors":["Johnson Controls"]},"summary":"An attacker can retrieve embedded sensitive data from Johnson Controls EasyIO FS32 devices due to a hard-coded cryptographic key.","url":"https://insights.sbomify.com/CVE-2026-71449/"}