{"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-44596 exists.","fix":"Upgrade org.yamcs:yamcs-core to 5.12.7 or later.","what":"CVE-2026-44596 is a medium-severity vulnerability in yamcs, published on 16 Jul 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-44596 and fix it if it is affected.\n\nWhat it is: CVE-2026-44596 is a medium-severity vulnerability in yamcs, published on 16 Jul 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-44596 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-44596/ (Markdown: https://insights.sbomify.com/CVE-2026-44596/index.md)","id":"CVE-2026-44596","markdown":"https://insights.sbomify.com/CVE-2026-44596/index.md","name":"CVE-2026-44596","record":{"aliases":["GHSA-w5r6-mcgq-7pq4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Mission control framework","requires_auth":"none","summary":"An unauthenticated attacker can brute-force user passwords due to missing rate limiting on the authentication endpoint, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"yamcs","vendor":"spaceapplications"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"Yamcs is a mission control framework. Prior to 5.12.7, the authentication endpoint POST /auth/token in yamcs-core, handled by yamcs-core/src/main/java/org/yamcs/http/auth/AuthHandler.java, lacked any rate limiting, account lockout, or failed-attempt throttling, so an unauthenticated remote attacker could perform unlimited password-guessing attempts against any user account, significantly increasing the risk of successful brute-force attacks. 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-29T13:42:06Z","kind":"github_poc","ref":"https://github.com/ex-cal1bur/CVE-2026-44596","stars":0,"title":"YAMCS yamcs-core \u003c 5.12.7 lacks rate limiting on POST /auth/token. An unauthenticated attacker can perform unlimited brute-force attempts against any account. Never returns HTTP 429. Fixed in 5.12.7."},{"date":"2026-05-30","kind":"exploitdb","ref":"52605","stars":null,"title":"YAMCS yamcs-core  5.12.7 - No Rate Limiting"}],"tier":"weaponised"},"has_fix":true,"headline":"Yamcs: No Rate Limiting on Authentication Endpoint","id":"CVE-2026-44596","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Denial of service in Tor","id":"CVE-2026-44597"},"packages":[{"ecosystem":"Maven","fixed":["5.12.7"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":null,"source":"GHSA-w5r6-mcgq-7pq4"},{"ecosystem":"Maven","fixed":["5.12.7"],"introduced":["0"],"last_affected":[],"package":"org.yamcs:yamcs-core","purl":"pkg:maven/org.yamcs/yamcs-core","source":"GHSA-w5r6-mcgq-7pq4"}],"prev":{"headline":"Yamcs: Unauthorized user enumeration via IAM API endpoints","id":"CVE-2026-44595"},"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.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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-17","vendors":["yamcs"]},"summary":"An unauthenticated attacker can brute-force user passwords due to missing rate limiting on the authentication endpoint, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-44596/"}