Central Dogma: LDAP injection in SearchFirstActiveDirectoryRealm enables authentication confusion and audit log evasion
CVE-2026-11748GHSA-98q5-5qh2-7w75
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (com.linecorp.centraldogma:centraldogma-server-auth-shiro 0.84.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven com.linecorp.centraldogma:centraldogma-server-auth-shiro
- Affected
- < 0.84.0
- Fixed in
- 0.84.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-98q5-5qh2-7w75 lists affected ranges: Maven com.linecorp.centraldogma:centraldogma-server-auth-shiro >=0 <0.84.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-98q5-5qh2-7w75 lists affected ranges: Maven com.linecorp.centraldogma:centraldogma-server-auth-shiro >=0 <0.84.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 6.9 · 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 · score source
- EPSS
- CVE-2026-11748: 0.48% estimated exploitation activity in the next 30 days; percentile 41.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Vulnerability SearchFirstActiveDirectoryRealm.findUserDn() substitutes the user-supplied username from the login form into an LDAP search filter template (default cn={0}) without escaping RFC 4515 filter metacharacters (, (, ), \, NUL). Combined with SearchControls.setCountLimit(1) on the same call site, this allows three distinct attack primitives: 1. Authentication confusion — typing username causes the realm to construct filter cn=, return the first directory entry (typically a privileged account in AD ordering), and attempt bind against that DN with the attacker's password. 2. Audit log evasion — payload bob)(uid=alice is recorded verbatim in audit logs while the realm searches with the malformed filter, breaking accountability/compliance (SOX, PCI-DSS, ISO 27001). 3. Directory enumeration — wildcards and timing differences allow reconnaissance of OU structure and admin group membership. A repo-wide search for any LDAP escape helper (escapeLdap, encodeFilter, escapeFilter,…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-98q5-5qh2-7w75
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-98q5-5qh2-7w75
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-11748 Advisory: Central Dogma: LDAP injection in SearchFirstActiveDirectoryRealm enables authentication confusion and audit log evasion IDs: CVE-2026-11748, GHSA-98q5-5qh2-7w75 Record: https://patchnext.com/advisories/cve-2026-11748 (revision 3, source checked 26 Oct 2026, 16:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: com.linecorp.centraldogma:centraldogma-server-auth-shiro 0.84.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven com.linecorp.centraldogma:centraldogma-server-auth-shiro: affected < 0.84.0; fixed in 0.84.0 ## Suggested inspection (read-only) - Maven com.linecorp.centraldogma:centraldogma-server-auth-shiro: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on com.linecorp.centraldogma:centraldogma-server-auth-shiro. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-98q5-5qh2-7w75 (OSV record GHSA-98q5-5qh2-7w75 lists affected ranges: Maven com.linecorp.centraldogma:centraldogma-server-auth-shiro >=0 <0.84.0 (fixed)) - Verified: https://github.com/advisories/GHSA-98q5-5qh2-7w75 (GitHub-reviewed advisory GHSA-98q5-5qh2-7w75 lists affected ranges: Maven com.linecorp.centraldogma:centraldogma-server-auth-shiro >=0 <0.84.0) Commands are suggestions: review each one before running it.
Loading voting…