dbcve.org
CxfApplication · Apache

CVE-2026-44930

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-22
Fix available
A fix is available. Upgrade to 3.6.11 / 4.1.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
An LDAP injection vulnerability in the LDAP Certificate repository of the XKMS server in Apache CXF may allow an attacker to retrieve arbitrary certificates from the repository.  Users are recommended to upgrade to versions 4.2.1, 4.1.6 or 3.6.11, which fix this issue.

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

An LDAP injection vulnerability exists in Apache CXF's XKMS server LDAP certificate repository. The vulnerability allows attackers to manipulate LDAP queries through unsanitized input, enabling retrieval of arbitrary certificates from the repository.

MitigationUpgrade Apache CXF to versions 4.2.1, 4.1.6, or 3.6.11 to obtain the fixed code that properly sanitizes LDAP query inputs.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CxfApplication
Affected:< 3.6.11>= 4.0.0, < 4.1.6= 4.2.0

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

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

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 Apache CXF version
    Check the CXF version in your project dependencies (Maven pom.xml, Gradle build file, or JAR manifest). Common locations: META-INF/MANIFEST.MF in cxf-core.jar, or the CXF version declared in your dependency management.
    Affected if The installed version is < 3.6.11, OR >= 4.0.0 and < 4.1.6, OR exactly 4.2.0
  2. Determine if XKMS is deployed
    Search for XKMS-related configuration files (xkms-server.xml, xkms-servlet.xml) or XKMS bean definitions in your application context files. Check for org.apache.cxf.xkms.* classes in your classpath.
    Affected if XKMS server components are deployed in your environment
  3. Verify LDAP Certificate repository is configured
    Inspect your XKMS configuration for ldap: or LdapXKMSCertificateRepository bean definitions. Look for LDAP URL, base DN, and search filter configurations in xkms-server.xml or equivalent Spring/Blueprint XML.
    Affected if An LDAP-based certificate repository is configured for XKMS
  4. Check LDAP query handling
    Review the LDAP search filter patterns in your XKMS LDAP repository configuration. Look for user-controllable input being used directly in LDAP search filters without proper sanitization.
    Affected if LDAP search filters accept user input without parameterized query handling

You are affected if you run a vulnerable Apache CXF version (3.x before 3.6.11, 4.0.0-4.1.5, or 4.2.0) AND have XKMS with an LDAP Certificate repository actively configured.

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
Upgrade available Upgrade to 3.6.11 / 4.1.6 or later
Fixed in 3.6.114.1.6
Interim mitigation

Upgrade Apache CXF to versions 4.2.1, 4.1.6, or 3.6.11 to obtain the fixed code that properly sanitizes LDAP query inputs.

Recommended fix High confidence

Upgrade to CXF 3.6.11, 4.1.6, or 4.2.1 depending on your current major version branch

  1. 1. Identify the current Apache CXF version in use by checking pom.xml dependencies or build configuration
  2. 2. Determine the appropriate upgrade path based on your current version branch (3.x, 4.0.x-4.1.x, or 4.2.x)
  3. 3. For Maven projects: Update the CXF dependency version in pom.xml to 3.6.11 (for 3.x users), 4.1.6 (for 4.0.x-4.1.x users), or 4.2.1 (for 4.2.0 users)
  4. 4. For Gradle projects: Update the CXF dependency version in build.gradle to the appropriate fixed version
  5. 5. For direct JAR deployments: Replace the CXF JAR files with the new version from the Apache CXF download repository
  6. 6. Rebuild the application and run integration tests to verify the upgrade does not break existing functionality
  7. 7. Deploy the updated application to the target environment
Caveat Minor version upgrades typically have backward compatibility, but test thoroughly as LDAP configuration behavior may have changed

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

Fix this in Cxf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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