dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2026-11746

CRITICAL · 9.4 CVSS v4.0 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A hard-coded default credential vulnerability in centraldogma-server's embedded ZooKeeper ensemble allows unauthenticated remote attackers to access replication logs or join the cluster quorum when replication.secret is not explicitly configured, enabling full compromise of the replicated data and cluster control.

MitigationUpgrade to centraldogma-server version 0.84.0 or later and explicitly configure a strong, unique value for replication.secret in all deployments using ZooKeeper replication.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify centraldogma-server version
    Locate the installed centraldogma-server binary or JAR file and query its version using --version or check the JAR manifest, then compare against the affected range (versions prior to 0.84.0)
    Affected if The installed version is before 0.84.0 and uses the embedded ZooKeeper ensemble for replication
  2. Confirm embedded ZooKeeper is in use
    Inspect the centraldogma-server configuration file (typically centraldogma.json or application.conf) for the replication.ensemble or zookeeper.embedded settings; verify that replication uses the built-in ZooKeeper rather than an external ZooKeeper instance
    Affected if Replication is configured to use the embedded ZooKeeper ensemble (not an external ZooKeeper)
  3. Check if replication.secret is explicitly configured
    Examine the replication or zookeeper configuration section in the centraldogma-server configuration file for the replication.secret property; verify whether a value is present or the property is missing/empty
    Affected if The replication.secret property is absent, commented out, or set to an empty value (relying on the hard-coded default credential)
  4. Verify ZooKeeper client port exposure
    Review network exposure settings or firewall rules to determine if the ZooKeeper client port (default 2181) or quorum port (default 2182) is accessible from untrusted networks
    Affected if The ZooKeeper ports are exposed to unauthenticated or untrusted network access

The environment is affected if centraldogma-server version is before 0.84.0, uses embedded ZooKeeper for replication, and replication.secret is not explicitly configured in the deployment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to centraldogma-server version 0.84.0 or later and explicitly configure a strong, unique value for replication.secret in all deployments using ZooKeeper replication.

Recommended fix High confidence

0.84.0

  1. Check the current installed version of centraldogma-server (e.g., via package manager or build configuration)
  2. Upgrade centraldogma-server to version 0.84.0 or later from the official release artifacts
  3. After upgrading, ensure ZooKeeper replication is configured with a strong, unique value for replication.secret in the configuration file (do not leave it unset)
  4. Restart the centraldogma-server service to apply the changes
  5. Verify the server starts successfully and ZooKeeper replication is operational with the new secret configured

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11746 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data