Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-11745

Vulnerability in com.linecorp.centraldogma:centraldogma-server-mirror-git (CVE-2026-11745)

Summary

Vulnerability in com.linecorp.centraldogma:centraldogma-server-mirror-git (CVE-2026-11745). Risk of unauthorized operations or information disclosure. Exploitable via ServerKeyVerifier. Mitigation: upgrade to 0.84.0 or later.

Original description

The description as published by the source.

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 known_hosts 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:

private SshClient createSshClient() {
    final ClientBuilder builder = ClientBuilder.builder();
    // Do not use local file system.
    builder.hostConfigEntryResolver(HostConfigEntryResolver.EMPTY);   // line 146
    builder.fileSystemFactory(NoneFileSystemFactory.INSTANCE);        // line 147
    // Do not verify the server key.
    builder.serverKeyVerifier((clientSession, remoteAddress, serverKey) -> true);  // line 149
    ...
}

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, `PasswordC…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-11745 has been found in com.linecorp.centraldogma:centraldogma-server-mirror-git.
Attackers can target a specific entry point like ServerKeyVerifier over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.linecorp.centraldogma:centraldogma-server-mirror-git to 0.84.0 or later.
If unsure, ask your IT team or search "com.linecorp.centraldogma:centraldogma-server-mirror-git CVE-2026-11745" on the vendor's site.

CVE-2026-11745 (com.linecorp.centraldogma:centraldogma-server-mirror-git) — CWE-322
Attack surface: ServerKeyVerifier / true / known_hosts / acceptedHostKeys
Patched: 0.84.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-322) exists in com.linecorp.centraldogma:centraldogma-server-mirror-git. Attackers reach the vulnerable code path via ServerKeyVerifier.

📍 Affected scope

Check the vendor advisory for the affected versions of com.linecorp.centraldogma:centraldogma-server-mirror-git. Attack surface: ServerKeyVerifier / true / known_hosts / acceptedHostKeys.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.84.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.linecorp.centraldogma:centraldogma-server-mirror-git を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade com.linecorp.centraldogma:centraldogma-server-mirror-git to 0.84.0

    ステージング環境で 0.84.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven com.linecorp.centraldogma:centraldogma-server-mirror-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.84.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details