{"answers":{"affected":"4 open source packages ship an affected version, including org.yamcs:yamcs-core.","exploited":"There is no known exploitation of CVE-2026-55545 in the wild and no public exploit code.","fix":"Upgrade org.yamcs:yamcs-core to a fixed version for your release line: 5.12.8 or 5.13.2.","what":"CVE-2026-55545 is a medium-severity missing authorization 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-55545 and fix it if it is affected.\n\nWhat it is: CVE-2026-55545 is a medium-severity missing authorization 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: There is no known exploitation of CVE-2026-55545 in the wild and no public exploit code.\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-55545/ (Markdown: https://insights.sbomify.com/CVE-2026-55545/index.md)","id":"CVE-2026-55545","markdown":"https://insights.sbomify.com/CVE-2026-55545/index.md","name":"CVE-2026-55545","record":{"aliases":["GHSA-fwww-cp23-7f5g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mission control framework","requires_auth":"low_privilege","summary":"Low-privilege users can access restricted telemetry and database changes via WebSocket due to missing privilege checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs WebSocket subscription handlers fail to enforce the privileges required by equivalent REST endpoints. PacketsApi.subscribePackets exposes the packets WebSocket topic without ObjectPrivilegeType.ReadPacket, ProcessingApi.subscribeAlgorithmStatus exposes the algorithm-status WebSocket topic without ObjectPrivilegeType.ReadAlgorithm, and MdbOverrideApi.subscribeMdbChanges exposes the mdb-changes WebSocket topic without SystemPrivilege.GetMissionDatabase. A low-privilege authenticated user can receive telemetry packets, algorithm status, and mission database change information outside the assigned authorization scope. 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":"none_known"},"has_fix":true,"headline":"Yamcs: WebSocket subscription handlers omit the privilege checks their REST siblings enforce","id":"CVE-2026-55545","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"QWED-MCP: Unsafe SymPy `parse_expr()` Remote Code Execution via Unsanitized Math Expression Input","id":"CVE-2026-55546"},"packages":[{"ecosystem":"Maven","fixed":["5.12.8"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":null,"source":"GHSA-fwww-cp23-7f5g"},{"ecosystem":"Maven","fixed":["5.12.8"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":"pkg:maven/org.yamcs/yamcs-core","source":"GHSA-fwww-cp23-7f5g"},{"ecosystem":"Maven","fixed":["5.13.2"],"introduced":["5.13.0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":null,"source":"GHSA-fwww-cp23-7f5g"},{"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-fwww-cp23-7f5g"}],"prev":{"headline":"NextCRM has BOLA/IDOR in MCP Campaign Tools that Allows Cross-User Campaign Disclosure and Tampering","id":"CVE-2026-55544"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["yamcs"]},"summary":"Low-privilege users can access restricted telemetry and database changes via WebSocket due to missing privilege checks.","url":"https://insights.sbomify.com/CVE-2026-55545/"}