# CVE-2026-11746: LY Corporation Central Dogma hard-coded secret in ZooKeeper replication

Source: https://junglewise.ai/threats/cve-2026-11746-ly-corporation-central-dogma-hard-coded-secret-in-zookeeper  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-22. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-11746 · Severity: critical · CVSS 4 · Published 2026-06-22

Central Dogma is a configuration management system used by LINE for storing and distributing versioned configuration data across microservices. When ZooKeeper replication is enabled for high availability without explicitly setting a replication secret, the system silently falls back to a hard-coded default credential "ch4n63m3" (leetspeak for "change me") that is visible in public source code. An attacker with local or network access to a Central Dogma replica can use this known credential to read the entire replication log—exposing all configuration changes, secrets, and encryption key rotations—or to impersonate a cluster member and inject malicious commands that execute on all replicas, effectively compromising the entire configuration infrastructure.

Technologies: [com.linecorp.centraldogma:centraldogma-server (Maven)](https://junglewise.ai/threats/technologies/com-linecorp-centraldogma-centraldogma-server). Vendors: [LY Corporation](https://junglewise.ai/threats/vendors/ly-corporation), [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2026-11746 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-11746 being exploited in the wild.

**How severe is CVE-2026-11746?** Critical severity, with a CVSS score of 4, published 22 June 2026.

**Which products and versions are affected?** com.linecorp.centraldogma:centraldogma-server (Maven) < 0.84.0, ECOSYSTEM:introduced=0,fixed=0.84.0.

**Is there a fix for CVE-2026-11746?** Yes. com.linecorp.centraldogma:centraldogma-server (Maven): upgrade to 0.84.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-11746 attacked?** It is attacked over the network or with local access, in a hosted service.

**Am I affected by CVE-2026-11746?** Check whether you run LY Corporation Central Dogma Server or com.linecorp.centraldogma:centraldogma-server (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- com.linecorp.centraldogma:centraldogma-server (Maven): upgrade to 0.84.0 or later

  ```sh
  # set com.linecorp.centraldogma:centraldogma-server to 0.84.0 in your pom.xml or build.gradle
  ```


## Technical details

The vulnerability exists in `ZooKeeperReplicationConfig.secret()`, which uses `firstNonNull(convertValue(secret, "replication.secret"), DEFAULT_SECRET)` to silently substitute the hard-coded constant `"ch4n63m3"` when the configuration parameter is missing or null. Central Dogma embeds an Apache ZooKeeper instance in each replica (via `EmbeddedZooKeeper extends QuorumPeer`), creating a distributed ensemble across the cluster's inter-replica network. The same default secret is wired into both the client-port SASL context (used for local authentication) and the quorum/learner SASL contexts (used for inter-replica peer communication). The credential is public in the GitHub repository, discoverable within seconds. An attacker with local host access (Surface A) can authenticate to the loopback-bound client port (127.0.0.1:2381) and read `/dogma/logs` and `/dogma/log_blocks`, obtaining all replicated commands—including master-key rotations and encryption metadata. An attacker with network access to a replica (Surface B, multi-tenant Kubernetes or shared VPC scenarios) can reach the quorum/election ports (not loopback-bound), impersonate a legitimate peer, receive all commits in real time, and inject forged log entries that are auto-replayed on every replica via `ZooKeeperCommandExecutor.replayLogs()`, enabling arbitrary command execution across the cluster. The patch, released in version 0.84.0, removes the default constant and enforces an explicit non-empty, non-placeholder secret via `checkArgument()` at startup, causing the process to fail closed if replication.secret is missing.

## Affected products

- LINE Central Dogma < 0.84.0

## Identifiers

- CVE-2026-11746
- GHSA-2j95-gqxf-v3vg

## Timeline

- 2026-06-22: disclosed: Advisory published on GitHub
- 2026-06-22: patched: Fixed in version 0.84.0
- 2026-09-11: advisory: CVE-2026-11746 assigned

## References

- [https://github.com/line/centraldogma/security/advisories/GHSA-2j95-gqxf-v3vg](https://github.com/line/centraldogma/security/advisories/GHSA-2j95-gqxf-v3vg)
- [https://api.github.com/repos/line/centraldogma/security-advisories/GHSA-2j95-gqxf-v3vg](https://api.github.com/repos/line/centraldogma/security-advisories/GHSA-2j95-gqxf-v3vg)

## Related threats

- [Central Dogma Authentication Bypass Vulnerability via Session Leakage](https://junglewise.ai/threats/cve-2024-1143-central-dogma-authentication-bypass-vulnerability-via-session)
- [Duplicate Advisory: Central Dogma Authentication Bypass Vulnerability via Session Leakage](https://junglewise.ai/threats/duplicate-advisory-central-dogma-authentication-bypass-vulnerability-f9d8d063)