{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28207 exists.","fix":"No fix has been published for CVE-2026-28207 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-28207 is a medium-severity command injection vulnerability in z-libs Zen-C, published on 26 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-28207 and fix it if it is affected.\n\nWhat it is: CVE-2026-28207 is a medium-severity command injection vulnerability in z-libs Zen-C, published on 26 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28207 exists.\n\nAffected product: z-libs Zen-C. 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-28207/ (Markdown: https://insights.sbomify.com/CVE-2026-28207/index.md)","id":"CVE-2026-28207","markdown":"https://insights.sbomify.com/CVE-2026-28207/index.md","name":"CVE-2026-28207","record":{"aliases":["GHSA-9rff-x96h-76h2"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Zen C compiler","requires_auth":"none","summary":"Local attackers can execute arbitrary shell commands via crafted output filenames in the Zen C compiler due to unsafe system() usage.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zen_c","vendor":"zenc-lang"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Zen C is a systems programming language that compiles to human-readable GNU C/C11. Prior to version 0.4.2, a command injection vulnerability (CWE-78) in the Zen C compiler allows local attackers to execute arbitrary shell commands by providing a specially crafted output filename via the `-o` command-line argument. The vulnerability existed in the `main` application logic (specifically in `src/main.c`), where the compiler constructed a shell command string to invoke the backend C compiler. This command string was built by concatenating various arguments, including the user-controlled output filename, and was subsequently executed using the `system()` function. Because `system()` invokes a shell to parse and execute the command, shell metacharacters within the output filename were interpreted by the shell, leading to arbitrary command execution. An attacker who can influence the command-line arguments passed to the `zc` compiler (like through a build script or a CI/CD pipeline configuration) can execute arbitrary commands with the privileges of the user running the compiler. The vulnerability has been fixed in version 0.4.2 by removing `system()` calls, implementing `ArgList`, and internal argument handling. Users are advised to update to Zen C version v0.4.2 or later.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Zen-C Vulnerable to Command Injection via Malicious Output Filename","id":"CVE-2026-28207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Junrar has arbitrary file write due to backslash path traversal bypass in LocalFolderExtractor on Linux/Unix","id":"CVE-2026-28208"},"packages":[],"prev":{"headline":"Initialization of a resource with an insecure default in OpenPLC_V3","id":"CVE-2026-28205"},"products":["Zen-C"],"published":"2026-02-26","related":[{"cvss_score":7.8,"headline":"Zen-C has Stack-Based Buffer Overflow in Identifier Mangling","id":"CVE-2026-33491","kev_date_added":null,"published":"2026-03-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-02","vendors":["z-libs"]},"summary":"Local attackers can execute arbitrary shell commands via crafted output filenames in the Zen C compiler due to unsafe system() usage.","url":"https://insights.sbomify.com/CVE-2026-28207/"}