dbcve.org
VulnerabilityAwaiting classification

CVE-2026-47840

HIGH · 7.5 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 network attacker positioned between UAA and its LDAP directory can impersonate the directory using any certificate from any trusted CA, then harvest the LDAP bind password and every end-user password sent during simple-bind authentication, and return forged group memberships that grant themselves admin scopes. This affects every deployment that authenticates users against LDAP over StartTLS. Affected versions: UAA versions prior to v78.13.0; Cf-deployment versions prior to v56.2.0.

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 man-in-the-middle vulnerability in UAA's LDAP authentication allows an attacker positioned on the network to impersonate the LDAP directory using any certificate from a trusted CA, enabling harvesting of the LDAP bind password and all user passwords sent during simple-bind authentication, plus injection of forged group memberships for privilege escalation.

MitigationUpgrade to UAA v78.13.0 or cf-deployment v56.2.0 or later, which contain fixes for proper LDAP server certificate validation. After upgrading, verify LDAP bind credentials have been rotated and monitor for any signs of compromise.

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

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. Determine UAA version
    Query the UAA instance for its version (typically via API endpoint, admin CLI, or version file in the UAA installation directory)
    Affected if The installed version is older than v78.13.0 (or cf-deployment older than v56.2.0)
  2. Confirm LDAP authentication is enabled
    Inspect UAA configuration for any configured LDAP identity providers or LDAP-based authentication backends
    Affected if LDAP authentication is actively configured and in use
  3. Review LDAP connection security settings
    Examine the LDAP provider configuration for TLS/SSL certificate validation settings (look for options like 'validateCertificates', 'sslVerification', or similar TLS verification controls)
    Affected if Certificate validation is disabled, set to allow any certificate, or not explicitly configured to enforce strict validation
  4. Identify trusted CA certificates for LDAP
    List the CA certificates trusted by UAA for LDAP connections (check the trust store or CA bundle configured for LDAP communications)
    Affected if The trust store contains certificates that were not intentionally provisioned for the legitimate LDAP server

You are affected if UAA is configured for LDAP authentication and runs a version older than 78.13.0, or if LDAP certificate validation is not strictly enforced regardless of version.

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 UAA v78.13.0 or cf-deployment v56.2.0 or later, which contain fixes for proper LDAP server certificate validation. After upgrading, verify LDAP bind credentials have been rotated and monitor for any signs of compromise.

Recommended fix High confidence

UAA v78.13.0 or cf-deployment v56.2.0

  1. 1. Upgrade UAA to version v78.13.0 or later, which includes proper LDAP certificate validation to prevent CA certificate impersonation attacks.
  2. 2. If using cf-deployment, upgrade to v56.2.0 or later, which bundles the fixed UAA version.
  3. 3. After upgrading, verify that LDAP over StartTLS authentication still functions correctly by testing user logins.
  4. 4. Review UAA configuration to ensure the LDAP certificate validation settings are properly applied (ensure 'ldap.url' uses StartTLS and certificates are properly validated).

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47840 — 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-47840 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