{"answers":{"affected":"2 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-55552 exists.","fix":"Upgrade org.yamcs:yamcs-core to 5.12.0 or later.","what":"CVE-2026-55552 is a high-severity path traversal 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-55552 and fix it if it is affected.\n\nWhat it is: CVE-2026-55552 is a high-severity path traversal 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-55552 exists.\n\nAffected packages and fixed versions:\n- org.yamcs:yamcs-core (Maven): affected all versions; fixed in 5.12.0\n- org.yamcs:yamcs-core (Maven): affected all versions; fixed in 5.12.0\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-55552/ (Markdown: https://insights.sbomify.com/CVE-2026-55552/index.md)","id":"CVE-2026-55552","markdown":"https://insights.sbomify.com/CVE-2026-55552/index.md","name":"CVE-2026-55552","record":{"aliases":["GHSA-9jg3-g3wh-w9pj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Yamcs mission control","requires_auth":"none","summary":"Unauthenticated attackers can read arbitrary host files via path traversal in Yamcs mission control framework.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Yamcs is a mission control framework. Prior to 5.11.13, Yamcs StaticFileHandler.locateFile resolves an unauthenticated request path without using Path.normalize and Path.toAbsolutePath to confirm that the absolute path remains within the configured staticRoots. A path containing traversal segments can escape the intended web root and return an arbitrary readable host file. The flaw is in yamcs-core/src/main/java/org/yamcs/http/StaticFileHandler.java and can disclose sensitive operating-system and application data. This issue is fixed in version 5.11.13, and the 5.12 line is fixed from version 5.12.0.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-55552.yaml","stars":null,"title":"Yamcs \u003c=5.11.12 - Arbitrary File Read"}],"tier":"weaponised"},"has_fix":true,"headline":"Yamcs: Unauthenticated Directory Traversal","id":"CVE-2026-55552","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"urllib: Cross-origin redirects preserve credential-bearing request headers, leading to potential credential leakage","id":"CVE-2026-55553"},"packages":[{"ecosystem":"Maven","fixed":["5.12.0"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":null,"source":"GHSA-9jg3-g3wh-w9pj"},{"ecosystem":"Maven","fixed":["5.12.0"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":"pkg:maven/org.yamcs/yamcs-core","source":"GHSA-9jg3-g3wh-w9pj"}],"prev":{"headline":"NextCRM has RBAC Bypass in MCP Product Tools that Allows Low-Privileged Users to Modify the CRM Product Catalog","id":"CVE-2026-55550"},"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":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["yamcs"]},"summary":"Unauthenticated attackers can read arbitrary host files via path traversal in Yamcs mission control framework.","url":"https://insights.sbomify.com/CVE-2026-55552/"}