{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-26787 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-26787 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-26787 is a medium-severity authentication bypass vulnerability in n/a, published on 22 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-26787 and fix it if it is affected.\n\nWhat it is: CVE-2025-26787 is a medium-severity authentication bypass vulnerability in n/a, published on 22 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-26787 in the wild and no public exploit code.\n\nAffected product: n/a. 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-26787/ (Markdown: https://insights.sbomify.com/CVE-2025-26787/index.md)","id":"CVE-2025-26787","markdown":"https://insights.sbomify.com/CVE-2025-26787/index.md","name":"CVE-2025-26787","record":{"aliases":["GHSA-93g4-gwqx-xffr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keyfactor SignServer","requires_auth":"high_privilege","summary":"A logic error resets access controls to allow any trusted client certificate on restart, bypassing intended restrictions in Keyfactor SignServer.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"signserver","vendor":"keyfactor"}],"cvss":{"score":4.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-642","name":"External Control of Critical State Data"}],"description":"An error in the SignServer container startup logic was found in Keyfactor SignServer versions prior to 7.2. The Admin CLI command used to configure Certificate access to the initial startup of the container sets a property of \"allowany\" to allow any user with a valid and trusted client auth certificate to connect. Admins can then set more restricted access to specific certificates. A logic error caused this admin CLI command to be run on each restart of the container instead of only the first startup as intended resetting the configuration to \"allowany\".","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":"Auth bypass in n/a","id":"CVE-2025-26787","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":"Auth bypass in FIDO Server","id":"CVE-2025-26788"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-26785"},"products":["n/a"],"published":"2025-12-22","related":[{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2025-47222","kev_date_added":null,"published":"2025-11-13"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2025-47220","kev_date_added":null,"published":"2025-11-13"},{"cvss_score":5.3,"headline":"Path traversal in n/a","id":"CVE-2025-47221","kev_date_added":null,"published":"2025-11-13"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-12-22","vendors":["n/a"]},"summary":"A logic error resets access controls to allow any trusted client certificate on restart, bypassing intended restrictions in Keyfactor SignServer.","url":"https://insights.sbomify.com/CVE-2025-26787/"}