{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-56437 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56437 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56437 is a high-severity vulnerability in Fuji Electric Co.,Ltd. Pupsman, published on 8 Jul 2026."},"fix_prompt":"Check this codebase for CVE-2026-56437 and fix it if it is affected.\n\nWhat it is: CVE-2026-56437 is a high-severity vulnerability in Fuji Electric Co.,Ltd. Pupsman, published on 8 Jul 2026. \nExploitation: There is no known exploitation of CVE-2026-56437 in the wild and no public exploit code.\n\nAffected product: Fuji Electric Co.,Ltd. Pupsman. 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-56437/ (Markdown: https://insights.sbomify.com/CVE-2026-56437/index.md)","id":"CVE-2026-56437","markdown":"https://insights.sbomify.com/CVE-2026-56437/index.md","name":"CVE-2026-56437","record":{"aliases":["GHSA-jrgq-cr5h-83px"],"analysis":null,"analysis_generated_by":null,"assigner":"jpcert","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"Uncontrolled search path element issue exists in Pupsman versions prior to 3.9.0. If a crafted DLL file is placed in the same folder as the affected installer and the installer is executed, arbitrary code may be executed with SYSTEM privilege.","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":"Uncontrolled search path element issue exists in Pupsman versions prior to 3.9.0.","id":"CVE-2026-56437","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Gitea: Token public-only scope bypassed on Limited-visibility owners (Repository + Package categories) — residual after CVE-2026-25714 / PR #37118","id":"CVE-2026-56443"},"packages":[],"prev":{"headline":"NGINX ngx_http_ssi_module vulnerability","id":"CVE-2026-56434"},"products":["Pupsman"],"published":"2026-07-08","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":"total"},"state":"PUBLISHED","updated":"2026-07-08","vendors":["Fuji Electric Co.,Ltd."]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-56437/"}