Skip to main content

Central Dogma CVE-2026-11748

| EUVDEUVD-2026-38208 MEDIUM
LDAP Injection (CWE-90)
2026-06-22 LY-Corporation GHSA-98q5-5qh2-7w75
6.9
CVSS 4.0 · Vendor: LY-Corporation
View

Attack ChainAIDerived

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

  1. Access
    Identify exposed Central Dogma login endpoint
  2. Delivery
    Craft username with LDAP filter metacharacters
  3. Exploit
    Submit unauthenticated login request
  4. Execution
    SearchFirstActiveDirectoryRealm builds malformed LDAP filter
  5. Persist
    Observe differential authentication responses
  6. Impact
    Enumerate AD structure and valid account names

Vulnerability Assessment

Weakness
CWE
MITRE ATT&CK

1 technique across 1 tactic: Initial 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 that the Central Dogma deployment has explicitly configured the SearchFirstActiveDirectoryRealm as its authentication mechanism, meaning Active Directory or LDAP-backed login must be enabled - this is not the default out-of-the-box configuration and requires deliberate administrator setup. Beyond that single configuration prerequisite, the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms no further conditions: no authentication, no user interaction, no special network position, and no elevated complexity are required. Exploitation is limited to the authentication confusion and directory enumeration impact; there is no indicated path to remote code execution or full credential bypass from description data alone. Deployments that authenticate via local accounts, OAuth, or other non-LDAP mechanisms are entirely unaffected.

Impact

The CVSS 4.0 score of 6.9 (Medium) is driven by a fully network-accessible, zero-complexity, unauthenticated attack surface (AV:N/AC:L/AT:N/PR:N/UI:N), tempered by limited impact metrics (VC:L/VI:L/VA:N/SC:L/SI:N/SA:N). The limited confidentiality and integrity ratings reflect that exploitation yields directory enumeration and authentication confusion rather than full credential disclosure or code execution. The SC:L (subsequent-system confidentiality impact) appropriately captures leakage of LDAP/AD structure beyond the Central Dogma process itself. No EPSS data was provided, and this CVE does not appear in the CISA KEV catalog, indicating no confirmed active exploitation at time of analysis. No public proof-of-concept code has been identified. Despite the moderate numeric score, the PR:N/UI:N combination means any internet-exposed Central Dogma instance using LDAP authentication is an attractive low-effort target for reconnaissance - real-world risk is elevated if the AD structure reveals privileged account names or group memberships. Defenders should treat this as a high priority for patching given the zero-barrier exploitation path, even absent KEV confirmation.

Exploit ScenarioDerived

An unauthenticated attacker targeting an internet-exposed Central Dogma instance sends a series of login requests with crafted usernames such as admin)(|(uid=* or *)(objectClass=* to rewrite the LDAP filter constructed by SearchFirstActiveDirectoryRealm. By observing differences in authentication responses, the attacker enumerates valid AD usernames, group memberships, and OU structure without holding any credentials. No public proof-of-concept has been identified, but LDAP injection techniques of this class are well-documented and require no specialized tooling.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.4% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jun 22, 2026

LDAP injection in Central Dogma's Apache Shiro-based authentication module exposes unauthenticated remote attackers to authentication confusion and Active Directory enumeration. The SearchFirstActiveDirectoryRealm component in centraldogma-server-auth-shiro versions prior to 0.84.0 inserts the login username directly into an LDAP search filter without escaping metacharacters, allowing filter logic manipulation. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms no authentication or preconditions are required beyond reaching the login endpoint. No public exploit or CISA KEV listing has been identified at time of analysis.

RemediationAI

Upgrade centraldogma-server-auth-shiro to version 0.84.0 or later, which is the vendor-released patch confirmed by LY Corporation's advisory GHSA-98q5-5qh2-7w75 (https://github.com/line/centraldogma/security/advisories/GHSA-98q5-5qh2-7w75) and the EUVD entry EUVD-2026-38208. If immediate upgrade is not possible, a targeted compensating control is to disable the SearchFirstActiveDirectoryRealm and switch to a non-LDAP authentication backend (e.g., local account or OAuth), accepting the trade-off of temporarily losing Active Directory integration. Alternatively, place a WAF rule or reverse-proxy filter that rejects login requests containing LDAP metacharacters (*, (, ), \, NUL) in the username field - note this may block legitimate usernames containing parentheses in rare AD environments. Network-level restriction of the Central Dogma authentication endpoint to trusted internal IP ranges reduces exposure without requiring application changes.

Affected VersionsENISA

Central Dogma patch: 0.84.0

Affected Packages

maven com.linecorp.centraldogma:centraldogma-server-auth-shiro 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 version-control service for configuration data. Its optional LDAP/Active Directory authentication path relies on the centraldogma-server-auth-shiro module backed by Apache Shiro. The vulnerable class, SearchFirstActiveDirectoryRealm, constructs an LDAP search filter by directly substituting the user-supplied login name into a filter string - e.g., (sAMAccountName=<input>) - without neutralizing LDAP filter metacharacters such as *, (, ), \, and NUL. This is a classic LDAP injection flaw (aligned with CWE-90: Improper Neutralization of Special Elements in an LDAP Query, though NVD has not formally assigned a CWE). By injecting crafted metacharacters, an attacker can rewrite filter logic to match unintended directory objects, confuse the authentication decision, or probe the AD tree structure through differential responses. The CPE cpe:2.3:a:ly_corporation:central_dogma:*:*:*:*:*:*:*:* covers all pre-0.84.0 releases.

Know when LDAP 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 6.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Network-reachable login endpoint, no credentials required; limited confidentiality and integrity impact from directory enumeration and auth confusion only.

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

Primary rating from Vendor (LY-Corporation).

CVSS VectorVendor: LY-Corporation

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

DescriptionCVE.org

A vulnerability has been identified in centraldogma-server-auth-shiro versions prior to 0.84.0, where the SearchFirstActiveDirectoryRealm substitutes the login username into an LDAP search filter without neutralizing LDAP filter metacharacters, allowing an unauthenticated attacker to manipulate the filter to cause authentication confusion and enumerate the directory structure.

Threat Intelligence Overview

EPSS Score
0.4%
Top 70% exploitable
Prevalence
Low
LINE's config server; niche developer tool
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 MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
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· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

More in LDAP

View all
CVE-2016-9299 CRITICAL POC
9.8 Jan 12

The remoting module in Jenkins before 2.32 and LTS before 2.19.3 allows remote attackers to execute arbitrary code via a

CVE-2017-14596 CRITICAL POC
9.8 Sep 20

In Joomla!. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required,

CVE-2017-8790 CRITICAL POC
9.8 May 05

An issue was discovered on Accellion FTA devices before FTA_9_12_180. Rated critical severity (CVSS 9.8), this vulnerabi

CVE-2026-15723 HIGH POC
8.2 Oct 21

An authenticated GitLab user can seize control of an existing LDAP-backed account on instances that have both OmniAuth S

CVE-2023-28853 MEDIUM POC
6.5 Apr 04

Mastodon is a free, open-source social network server based on ActivityPub Mastodon allows configuration of LDAP for aut

CVE-2020-36966 MEDIUM POC
6.4 Jan 30

Dolibarr 11.0.3 contains a persistent cross-site scripting vulnerability in LDAP synchronization settings that allows at

CVE-2025-36556 MEDIUM POC
6.1 Jan 20

A reflected cross-site scripting (xss) vulnerability exists in the ldapUser functionality of MedDream PACS Premium 7.3.6

CVE-2026-23906 CRITICAL
9.8 Feb 10

Authentication bypass in Apache Druid versions 0.17.0 through 35.x. Affects all versions prior to 36.0.0 when specific p

CVE-2026-44930 CRITICAL
9.8 May 22

Arbitrary certificate disclosure in Apache CXF's XKMS server lets remote attackers abuse an LDAP injection flaw (CWE-90)

CVE-2024-33868 CRITICAL
9.8 May 14

An issue was discovered in linqi before 1.4.0.1 on Windows. Rated critical severity (CVSS 9.8), this vulnerability is re

CVE-2023-6905 CRITICAL
9.8 Dec 18

A vulnerability, which was classified as problematic, has been found in Jahastech NxFilter 4.3.2.5.jsp?actionFlag=test&i

CVE-2021-43350 CRITICAL
9.8 Nov 11

An unauthenticated Apache Traffic Control Traffic Ops user can send a request with a specially-crafted username to the P

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