{"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-55565 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-55565 is a critical code injection vulnerability in yamcs, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55565 and fix it if it is affected.\n\nWhat it is: CVE-2026-55565 is a critical code injection vulnerability in yamcs, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55565 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-55565/ (Markdown: https://insights.sbomify.com/CVE-2026-55565/index.md)","id":"CVE-2026-55565","markdown":"https://insights.sbomify.com/CVE-2026-55565/index.md","name":"CVE-2026-55565","record":{"aliases":["GHSA-c64q-hj4j-375f"],"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":"low_privilege","summary":"Authenticated attackers can execute arbitrary code on Yamcs servers by injecting Java code via unescaped SQL LIKE patterns.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs LikeExpression.fillCode_getValueReturn in yamcs-core/src/main/java/org/yamcs/yarch/streamsql/LikeExpression.java inserts an unescaped LIKE pattern into Java source compiled by Expression.getCompiledExpression through SimpleCompiler.cook instead of applying ValueExpression.escapeJavaString. The pattern can originate from POST /api/archive/{instance}:executeSql, POST /api/archive/{instance}:streamSql, POST /api/archive/{instance}/tables/{table}:readRows, GET /api/archive/{instance}/events, or activity searches, including paths available with ReadTables, ReadEvents, or ReadActivities. A quote in the pattern can inject Java that runs as the Yamcs server process. This issue is fixed in versions 5.12.8 and 5.13.2.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Yamcs: Authenticated remote code execution via unescaped StreamSQL `LIKE` pattern compiled by Janino (`LikeExpression`)","id":"CVE-2026-55565","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":"Yamcs: DOM XSS in Extension Routing","id":"CVE-2026-55566"},"packages":[{"ecosystem":"Maven","fixed":["5.12.8"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":null,"source":"GHSA-c64q-hj4j-375f"},{"ecosystem":"Maven","fixed":["5.12.8"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":"pkg:maven/org.yamcs/yamcs-core","source":"GHSA-c64q-hj4j-375f"},{"ecosystem":"Maven","fixed":["5.13.2"],"introduced":["5.13.0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":null,"source":"GHSA-c64q-hj4j-375f"},{"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-c64q-hj4j-375f"}],"prev":{"headline":"FreeRDP: Out-of-bounds read in glyph_cache_get via crafted glyph fragments","id":"CVE-2026-55564"},"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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["yamcs"]},"summary":"Authenticated attackers can execute arbitrary code on Yamcs servers by injecting Java code via unescaped SQL LIKE patterns.","url":"https://insights.sbomify.com/CVE-2026-55565/"}