Skip to main content

Central Dogma CVE-2026-11746

| EUVDEUVD-2026-38207 CRITICAL
Use of Hard-coded Credentials (CWE-798)
2026-06-22 LY-Corporation GHSA-2j95-gqxf-v3vg
9.4
CVSS 4.0 · Vendor: LY-Corporation
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify reachable Central Dogma cluster
  2. Delivery
    Connect to ZooKeeper replication port
  3. Exploit
    Authenticate with hard-coded secret
  4. Execution
    Join quorum or tail replication log
  5. Persist
    Submit replicated commands cluster-wide
  6. Impact
    Pivot via exfiltrated config secrets

Vulnerability Assessment

Weakness
CWE
MITRE ATT&CK

2 techniques across 2 tactics: Persistence, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires (1) the target centraldogma-server to be running a version prior to 0.84.0 with ZooKeeper replication enabled, (2) the operator to have failed to set the replication.secret configuration property - which triggers the silent fallback to the hard-coded value, and (3) the attacker to have adjacent-network reachability (CVSS AV:A) to the embedded ZooKeeper ensemble ports on a cluster node. Single-node deployments without replication, and clusters where replication.secret was explicitly configured, are not exposed. No authentication, user interaction, or special platform is required once the network and configuration prerequisites are met (PR:N, UI:N, AT:N).

Impact

The CVSS 4.0 vector AV:A/AC:L/AT:N/PR:N/UI:N with VC:H/VI:H/VA:H and subsequent-system SC:H/SI:H/SA:H produces a 9.4 score, reflecting an adjacent-network, unauthenticated path to full compromise of every node in the cluster - a realistic rating given the hard-coded secret. EPSS, KEV status, and POC availability are not provided in the source data, so exploitation probability cannot be quantified; however, hard-coded secrets historically attract rapid public exploitation once disclosed. The AV:A (adjacent) constraint and the requirement that an operator actually enabled replication without setting replication.secret do meaningfully limit the exposed population compared with a default-on internet-facing flaw. Treat as high-priority for any deployment running replicated Central Dogma, but lower priority for single-node or properly-configured clusters; verify your replication.secret setting before patch scheduling.

Exploit ScenarioDerived

An attacker who gains a foothold on the same network segment as a Central Dogma cluster (for example, a compromised CI runner or neighboring container) scans for the ZooKeeper replication ports and connects using the publicly known hard-coded secret. Once authenticated to the ensemble they either passively stream the replication log to harvest configuration secrets stored in Central Dogma, or actively join the quorum and submit replicated commands that propagate malicious configuration to every consuming application. No public exploit identified at time of analysis, but reproducing this requires only reading the open-source repository to recover the hard-coded value.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 22, 2026

Cluster-wide remote code execution in LY Corporation's centraldogma-server prior to 0.84.0 occurs when ZooKeeper replication is enabled without explicitly configuring replication.secret, causing the embedded ZooKeeper ensemble to authenticate using a hard-coded, publicly known fallback credential. An adjacent attacker with network reachability to the replication ports can read the entire replication log or join the quorum to issue arbitrary replicated commands. No public exploit identified at time of analysis, but the issue is a default-credential failure that is trivial to weaponize once discovered.

RemediationAI

Vendor-released patch: Central Dogma 0.84.0 - upgrade centraldogma-server to 0.84.0 or later, which removes the silent fallback to the hard-coded secret. As an immediate workaround on unpatched nodes, explicitly set a strong, randomly generated replication.secret in the server configuration on every cluster member so the hard-coded default is never used; restart nodes in a rolling fashion to avoid quorum loss. If patching is delayed, restrict network reachability of the ZooKeeper replication ports to only the cluster's own nodes (host firewall or security group rules) - this prevents external quorum-joining but does not protect against adjacent attackers already on the management network. Review historical replication logs for unexpected writes or membership changes, and rotate any secrets or configuration data stored in Central Dogma that may have been exposed. Refer to the vendor advisory at https://github.com/line/centraldogma/security/advisories/GHSA-2j95-gqxf-v3vg for canonical guidance.

Affected VersionsENISA

Central Dogma patch: 0.84.0

Affected Packages

maven com.linecorp.centraldogma:centraldogma-server fix: 0.84.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in maven

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Central Dogma is LY Corporation's highly-available, Git-backed configuration repository service that uses an embedded Apache ZooKeeper ensemble to coordinate replication across nodes (CPE cpe:2.3:a:ly_corporation:central_dogma). ZooKeeper quorum members authenticate to each other using a shared secret; in vulnerable releases the server fails open when the operator does not set the replication.secret configuration key, silently substituting a hard-coded value baked into the codebase. Although no CWE is assigned in the input, this matches CWE-798 (Use of Hard-coded Credentials) combined with CWE-1188 (insecure default initialization). Because the ZooKeeper ensemble is the source of truth for replicated commands, anyone who can speak the quorum protocol with the right secret becomes a peer of the cluster.

Know when Central Dogma gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (LY-Corporation) PRIMARY 9.4 CRITICAL
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
vuln.today AI 9.6 CRITICAL

Adjacent ZooKeeper port reachability (AV:A), no auth thanks to hard-coded secret (PR:N), low complexity, and scope change because cluster-wide replicated commands affect all peers.

3.1 AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (LY-Corporation).

CVSS VectorVendor: LY-Corporation

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

LY Corporation's centraldogma-server is vulnerable to cluster-wide remote code execution when ZooKeeper replication is enabled without explicit credential configuration. Attackers with network access to replication ports can execute arbitrary commands using hard-coded default credentials, exposing the entire system to immediate compromise. Organizations running this component with default replication settings face critical risk of infrastructure takeover and data breach.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Explicitly configure a non-default replication.secret value in all deployment configurations immediately to override hard-coded fallback credential; (2) Restrict network access to ZooKeeper replication ports via firewall to trusted internal networks only; (3) Disable ZooKeeper replication if operationally feasible; (4) Implement continuous monitoring and alerting for unauthorized access attempts to replication ports.

Threat Intelligence Overview

EPSS Score
0.1%
Top 96% exploitable
Prevalence
Low
Niche configuration management server, limited production footprint
Threat Intel
1
1 sources
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Controlled
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

67
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +47
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy