Central Dogma: SSH host-key verification permanently disabled in Git mirror (SshGitMirror)
CVE-2026-11745GHSA-vjfw-cpmh-xwv3
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (com.linecorp.centraldogma:centraldogma-server-mirror-git 0.84.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven com.linecorp.centraldogma:centraldogma-server-mirror-git
- Affected
- < 0.84.0
- Fixed in
- 0.84.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-vjfw-cpmh-xwv3 lists affected ranges: Maven com.linecorp.centraldogma:centraldogma-server-mirror-git >=0 <0.84.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-vjfw-cpmh-xwv3 lists affected ranges: Maven com.linecorp.centraldogma:centraldogma-server-mirror-git >=0 <0.84.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.8 · CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:L · score source
- EPSS
- CVE-2026-11745: 0.22% estimated exploitation activity in the next 30 days; percentile 12.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Vulnerability Central Dogma's Git mirror SSH client installs an Apache MINA SSHD ServerKeyVerifier lambda that returns true unconditionally for every outbound SSH connection used by git+ssh:// mirrors. The accompanying lines disable the knownhosts and ~/.ssh/config fallbacks, and a repo-wide search confirms that no host-key pinning mechanism (no acceptedHostKeys, knownHosts, KnownHostsServerKeyVerifier, StaticServerKeyVerifier, or RequiredServerKeyVerifier) exists anywhere in server-mirror-git/. Operators have no opt-in way to enable verification. Every outbound mirror connection blindly trusts whatever host key the remote presents. Evidence File: server-mirror-git/src/main/java/com/linecorp/centraldogma/server/internal/mirror/SshGitMirror.java Lines 143-160 (especially 149) on branch main @ commit d64a5151: Verification: - Read confirmed on 2026-05-21 against main @ d64a5151. - A multi-agent code audit verified that no operator-facing pinning field exists on SshKeyCredential,…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-vjfw-cpmh-xwv3
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-vjfw-cpmh-xwv3
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-11745 Advisory: Central Dogma: SSH host-key verification permanently disabled in Git mirror (SshGitMirror) IDs: CVE-2026-11745, GHSA-vjfw-cpmh-xwv3 Record: https://patchnext.com/advisories/cve-2026-11745 (revision 3, source checked 26 Oct 2026, 16:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: com.linecorp.centraldogma:centraldogma-server-mirror-git 0.84.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven com.linecorp.centraldogma:centraldogma-server-mirror-git: affected < 0.84.0; fixed in 0.84.0 ## Suggested inspection (read-only) - Maven com.linecorp.centraldogma:centraldogma-server-mirror-git: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on com.linecorp.centraldogma:centraldogma-server-mirror-git. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-vjfw-cpmh-xwv3 (OSV record GHSA-vjfw-cpmh-xwv3 lists affected ranges: Maven com.linecorp.centraldogma:centraldogma-server-mirror-git >=0 <0.84.0 (fixed)) - Verified: https://github.com/advisories/GHSA-vjfw-cpmh-xwv3 (GitHub-reviewed advisory GHSA-vjfw-cpmh-xwv3 lists affected ranges: Maven com.linecorp.centraldogma:centraldogma-server-mirror-git >=0 <0.84.0) Commands are suggestions: review each one before running it.
Loading voting…