{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55109 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55109 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55109 is a critical authentication bypass vulnerability in BMC Control-M/Agent, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55109 and fix it if it is affected.\n\nWhat it is: CVE-2025-55109 is a critical authentication bypass vulnerability in BMC Control-M/Agent, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-55109 in the wild and no public exploit code.\n\nAffected product: BMC Control-M/Agent. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-55109/ (Markdown: https://insights.sbomify.com/CVE-2025-55109/index.md)","id":"CVE-2025-55109","markdown":"https://insights.sbomify.com/CVE-2025-55109/index.md","name":"CVE-2025-55109","record":{"aliases":["GHSA-gh47-wqwg-v2cm"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"BMC Control-M Agent","requires_auth":"none","summary":"Remote attackers can bypass authentication on BMC Control-M/Agent by using default or empty keystores with trusted third-party certificates.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"airbus","cpe":[{"product":"control-m\\/agent","vendor":"bmc"}],"cvss":{"score":9.5,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An authentication bypass vulnerability exists in the out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions when using an empty or default kdb keystore or a default PKCS#12 keystore. A remote attacker with access to a signed third-party or demo certificate for client authentication can bypass the need for a certificate signed by the certificate authority of the organization during authentication on the Control-M/Agent.\n\nThe Control-M/Agent contains hardcoded certificates which are only trusted as fallback if an empty kdb keystore is used; they are never trusted if a PKCS#12 keystore is used. All of these certificates are now expired.\n\nIn addition, the Control-M/Agent default kdb and PKCS#12 keystores contain trusted third-party certificates (external recognized CAs and default self-signed demo certificates) which are trusted for client authentication.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"BMC Control-M/Agent default SSL/TLS configuration authenticated bypass","id":"CVE-2025-55109","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"BMC Control-M/Agent hardcoded default keystore password","id":"CVE-2025-55110"},"packages":[],"prev":{"headline":"Missing authorization in Control-M/Agent","id":"CVE-2025-55108"},"products":["Control-M/Agent"],"published":"2025-09-16","related":[{"cvss_score":9.5,"headline":"BMC Control-M/Agent unescaped NULL byte in access control list checks","id":"CVE-2025-55113","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":9.3,"headline":"BMC Control-M/Agent path traversal local privilege escalation","id":"CVE-2025-55115","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":9.3,"headline":"BMC Control-M/Agent buffer overflow local privilege escalation","id":"CVE-2025-55116","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":7.6,"headline":"BMC Control-M/Agent hardcoded Blowfish keys","id":"CVE-2025-55112","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":6.3,"headline":"BMC Control-M/Agent buffer overflow in SSL/TLS communication","id":"CVE-2025-55117","kev_date_added":null,"published":"2025-09-16"},{"cvss_score":5.7,"headline":"BMC Control-M/Agent insecure default file permissions","id":"CVE-2025-55111","kev_date_added":null,"published":"2025-09-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["BMC"]},"summary":"Remote attackers can bypass authentication on BMC Control-M/Agent by using default or empty keystores with trusted third-party certificates.","url":"https://insights.sbomify.com/CVE-2025-55109/"}