{"answers":{"affected":"2 open source packages ship an affected version, including org.yamcs:yamcs-core. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44595 exists.","fix":"Upgrade org.yamcs:yamcs-core to 5.12.7 or later.","what":"CVE-2026-44595 is a medium-severity missing authorization vulnerability in yamcs, published on 16 Jul 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-44595 and fix it if it is affected.\n\nWhat it is: CVE-2026-44595 is a medium-severity missing authorization vulnerability in yamcs, published on 16 Jul 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-44595 exists.\n\nAffected packages and fixed versions:\n- org.yamcs:yamcs-core (Maven): affected all versions; fixed in 5.12.7\n- org.yamcs:yamcs-core (Maven): affected all versions; fixed in 5.12.7\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-44595/ (Markdown: https://insights.sbomify.com/CVE-2026-44595/index.md)","id":"CVE-2026-44595","markdown":"https://insights.sbomify.com/CVE-2026-44595/index.md","name":"CVE-2026-44595","record":{"aliases":["GHSA-p2rj-mrmc-9w29"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Mission control framework","requires_auth":"low_privilege","summary":"Authenticated users can enumerate all system accounts and group memberships due to missing privilege checks in Yamcs IAM API endpoints.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"yamcs","vendor":"spaceapplications"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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.7, the IAM API endpoints listUsers, getUser, listGroups, and getGroup in yamcs-core did not enforce the required SystemPrivilege.ControlAccess check in yamcs-core/src/main/java/org/yamcs/http/api/IamApi.java, so any authenticated user, even one with low or no privileges, could enumerate all user accounts in the system including their usernames, superuser status, and group memberships. This issue is fixed in versions 5.12.7 and 5.13.0.","ecosystems":["Maven"],"exploits":{"exploitdb":1,"first_seen":"2026-05-29","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-29T14:31:15Z","kind":"github_poc","ref":"https://github.com/ex-cal1bur/CVE-2026-44595","stars":0,"title":"# CVE-2026-44595 YAMCS Unauthorized User Enumeration via IAM API "},{"date":"2026-05-30","kind":"exploitdb","ref":"52604","stars":null,"title":"YAMCS yamcs-core  5.12.7 - User Enumeration"}],"tier":"weaponised"},"has_fix":true,"headline":"Yamcs: Unauthorized user enumeration via IAM API endpoints","id":"CVE-2026-44595","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Yamcs: No Rate Limiting on Authentication Endpoint","id":"CVE-2026-44596"},"packages":[{"ecosystem":"Maven","fixed":["5.12.7"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":null,"source":"GHSA-p2rj-mrmc-9w29"},{"ecosystem":"Maven","fixed":["5.12.7"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":"pkg:maven/org.yamcs/yamcs-core","source":"GHSA-p2rj-mrmc-9w29"}],"prev":{"headline":"esm.sh: Path Traversal via package.json browser field allows reading arbitrary server files","id":"CVE-2026-44594"},"products":["yamcs"],"published":"2026-07-16","related":[{"cvss_score":9.8,"headline":"Yamcs: Remote Code Execution via Mission Database algorithm override","id":"CVE-2026-46562","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":9.1,"headline":"Yamcs: Server-Side Code Injection (RCE) via Janino Expression Engine in `JavaExprAlgorithmExecutionFactory`","id":"CVE-2026-44632","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":9.1,"headline":"Yamcs: Authenticated Remote Code Execution (RCE) via Jython Algorithm Code Injection","id":"CVE-2026-46621","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":9.1,"headline":"Yamcs API Directory Traversal vulnerability","id":"CVE-2023-45278","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":7.5,"headline":"Yamcs Path Traversal vulnerability","id":"CVE-2023-45277","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":6.5,"headline":"Yamcs: No Rate Limiting on Authentication Endpoint","id":"CVE-2026-44596","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2023-45281","kev_date_added":null,"published":"2023-10-19"}],"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":"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-18","vendors":["yamcs"]},"summary":"Authenticated users can enumerate all system accounts and group memberships due to missing privilege checks in Yamcs IAM API endpoints.","url":"https://insights.sbomify.com/CVE-2026-44595/"}