Categories
CVE-2026-11746

Vulnerability in com.linecorp.centraldogma:centraldogma-server (CVE-2026-11746)

Summary

Vulnerability in com.linecorp.centraldogma:centraldogma-server (CVE-2026-11746). Risk of unauthorized operations or information disclosure. Exploitable via replication.secret. Mitigation: upgrade to 0.84.0 or later.

Original description

The description as published by the source.

Vulnerability

ZooKeeperReplicationConfig.secret() silently substitutes the hard-coded constant "ch4n63m3" (leetspeak for "change me") whenever the operator omits replication.secret. The same secret is wired into both the client-facing SASL context and the quorum/learner SASL contexts of the embedded ZooKeeper. The constant is in OSS source on GitHub and is discoverable via code search in seconds.

Three Reinforcing Defects

  1. OSS-public credential — DEFAULT_SECRET is in line/centraldogma source.
  2. Silent fallback — firstNonNull(convertValue(...), DEFAULT_SECRET) substitutes the default with no log, no warning, no startup banner. The only sanity check checkArgument(!secret().isEmpty(), ...) passes because the getter substitutes the literal before the emptiness check runs.
  3. Dual-purpose secret — used for both ZK client-port super auth and inter-peer quorum SASL. A single leaked password authenticates against both surfaces.

Architecture Context (Important)

Central Dogma does NOT connect to an external ZooKeeper ensemble. Each replica embeds a QuorumPeer (EmbeddedZooKeeper extends QuorumPeer) inside its own JVM. The Central Dogma cluster IS the ZK ensemble. So the "ZK network" is the inter-replica network of the Central Dogma cluster itself.

Applicability

replication.method ZK Started? Applicable?
NONE (standalone, dev default) No NOT applicable
ZOOKEEPER (HA production…

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-11746 has been found in com.linecorp.centraldogma:centraldogma-server.
Attackers can target a specific entry point like replication.secret over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.linecorp.centraldogma:centraldogma-server to 0.84.0 or later.
If unsure, ask your IT team or search "com.linecorp.centraldogma:centraldogma-server CVE-2026-11746" on the vendor's site.

CVE-2026-11746 (com.linecorp.centraldogma:centraldogma-server) — CWE-798
Attack surface: replication.secret / DEFAULT_SECRET / QuorumPeer / replication.method
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-798) exists in com.linecorp.centraldogma:centraldogma-server. Attackers reach the vulnerable code path via replication.secret.

📍 Affected scope

Check the vendor advisory for the affected versions of com.linecorp.centraldogma:centraldogma-server. Attack surface: replication.secret / DEFAULT_SECRET / QuorumPeer / replication.method.

🔥 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 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade com.linecorp.centraldogma:centraldogma-server 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
[{"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