Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-vjfw-cpmh-xwv3

Central Dogma: SSH host-key verification permanently disabled in Git mirror (SshGitMirror)

CVSS 8.8 HighEPSS 0.0022 · 12th percentile

Published by the GitHub Advisory Database at 11 Sept 2026, 20:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.linecorp.centraldogma:centraldogma-server-mirror-gitMaven<0.84.00.84.0
Identifiers
GHSA-vjfw-cpmh-xwv3 · CVE-2026-11745
Weakness (CWE)
CWE-322
Tags
Published
11 Sept 2026
Updated
11 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Central Dogma's Git mirror server package (centraldogma-server-mirror-git, Maven) before 0.84.0 does not verify SSH host keys for git+ssh mirrors; the verifier accepts any host key presented. An attacker with network position between Central Dogma and the remote git server, such as through ARP spoofing or DNS poisoning, can impersonate that server, reading mirrored repository contents or serving arbitrary commits, and may capture credentials. Upgrade to 0.84.0. The source does not describe a workaround.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 4.0 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 CNA (LY-Corporation)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 12th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.