{"answers":{"affected":"4 open source packages ship an affected version, including org.yamcs:yamcs-core.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55559 exists.","fix":"Upgrade org.yamcs:yamcs-core to a fixed version for your release line: 5.12.8 or 5.13.2.","what":"CVE-2026-55559 is a critical code injection vulnerability in yamcs, published on 28 Aug 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-55559 and fix it if it is affected.\n\nWhat it is: CVE-2026-55559 is a critical code injection vulnerability in yamcs, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55559 exists.\n\nAffected packages and fixed versions:\n- org.yamcs:yamcs-core (Maven): affected all versions; fixed in 5.12.8\n- org.yamcs:yamcs-core (Maven): affected all versions; fixed in 5.12.8\n- org.yamcs:yamcs-core (Maven): affected from 5.13.0; fixed in 5.13.2\n- org.yamcs:yamcs-core (Maven): affected from 5.13.0; fixed in 5.13.2\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-55559/ (Markdown: https://insights.sbomify.com/CVE-2026-55559/index.md)","id":"CVE-2026-55559","markdown":"https://insights.sbomify.com/CVE-2026-55559/index.md","name":"CVE-2026-55559","record":{"aliases":["GHSA-73mf-m39p-wpm9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Yamcs mission control","requires_auth":"none","summary":"Attackers can execute arbitrary commands by injecting YAML into instance templates, affecting Yamcs mission control deployments.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-470","name":"Use of Externally-Controlled Input to Select Classes or Code"},{"id":"CWE-1336","name":"Improper Neutralization of Special Elements Used in a Template Engine"}],"description":"Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs inserts templateArgs from POST /api/instances and PATCH /api/instances/{instance} into YAML through VarStatement.append in yamcs-core/src/main/java/org/yamcs/templating/VarStatement.java without YAML-context escaping. The rendered configuration is parsed by YamcsServer.createInstance and loaded by YamcsServerInstance, allowing an attacker to inject a services entry for org.yamcs.ProcessRunner. Deployments without security.yaml expose the operation through the guest superuser, while secured deployments require SystemPrivilege.CreateInstances. Successful exploitation executes commands as the Yamcs service account. This issue is fixed in versions 5.12.8 and 5.13.2.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2026-10-02","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-02T14:30:25Z","kind":"github_poc","ref":"https://github.com/MRdark-ops/CVE-2026-55559","stars":1,"title":"Unauthenticated RCE in Yamcs mission control via YAML injection in reconfigureInstance()"}],"tier":"weaponised"},"has_fix":true,"headline":"Yamcs: Remote Code Execution via instance-template argument YAML injection (createInstance)","id":"CVE-2026-55559","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"InvoicePlane: Guest user IDOR in quote approval and rejection","id":"CVE-2026-55561"},"packages":[{"ecosystem":"Maven","fixed":["5.12.8"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":null,"source":"GHSA-73mf-m39p-wpm9"},{"ecosystem":"Maven","fixed":["5.12.8"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":"pkg:maven/org.yamcs/yamcs-core","source":"GHSA-73mf-m39p-wpm9"},{"ecosystem":"Maven","fixed":["5.13.2"],"introduced":["5.13.0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":null,"source":"GHSA-73mf-m39p-wpm9"},{"ecosystem":"Maven","fixed":["5.13.2"],"introduced":["5.13.0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":"pkg:maven/org.yamcs/yamcs-core","source":"GHSA-73mf-m39p-wpm9"}],"prev":{"headline":"aiosmtplib: STARTTLS response injection","id":"CVE-2026-55558"},"products":["yamcs"],"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["yamcs"]},"summary":"Attackers can execute arbitrary commands by injecting YAML into instance templates, affecting Yamcs mission control deployments.","url":"https://insights.sbomify.com/CVE-2026-55559/"}