dbcve.org
CxfApplication · Apache

CVE-2026-50629

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-12
Fix available
A fix is available. Upgrade to 4.1.7 / 4.2.2 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The 'clientId' parameter from incoming HTTP requests is directly concatenated into OAuth2 server log warning messages without sanitizing control characters. This allows an attacker to inject arbitrary content, including fake log entries, into the server's log files. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes 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

The 'clientId' parameter from incoming HTTP requests is directly concatenated into OAuth2 server log warning messages without sanitizing control characters, allowing an attacker to inject arbitrary content including fake log entries into the server's log files.

MitigationUpgrade to version 4.2.2 or 4.1.7 which contains the fix for this log injection vulnerability.

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:< 4.1.7>= 4.2.0, < 4.2.2

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Identify Apache CXF version
    Locate the CXF JAR file (cxf-core.jar, cxf-services-sts-core.jar, or similar) in your application lib directory or Maven dependencies, and read the version from the filename or MANIFEST.MF file inside the JAR.
    Affected if The version number is less than 4.1.7, or greater than or equal to 4.2.0 but less than 4.2.2.
  2. Verify OAuth2 server module is in use
    Search your application configuration files (often in src/main/resources or WEB-INF) for OAuth2-related configuration such as oauth2.provider, oauth2.service, or OAuth2Server bean definitions.
    Affected if OAuth2 server functionality is configured and active in your deployment.
  3. Confirm clientId parameter handling is active
    Review your OAuth2 server configuration for endpoints that accept clientId as a parameter, such as token issuance or client registration endpoints. Check if these endpoints process incoming HTTP request parameters.
    Affected if Your OAuth2 server accepts clientId parameters from incoming HTTP requests.
  4. Check log output for the vulnerable code path
    Review source code or decompiled classes for the OAuth2 server warning log statements that include the clientId parameter. Look for log.warn() or similar calls that concatenate clientId without sanitization.
    Affected if The code shows clientId being logged directly from request parameters without control character filtering.

You are affected if your deployed Apache CXF version falls within the vulnerable range (< 4.1.7 or >= 4.2.0 but < 4.2.2) AND your environment has OAuth2 server functionality enabled that processes clientId parameters from HTTP requests.

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 4.1.7 / 4.2.2 or later
Fixed in 4.1.74.2.2
Interim mitigation

Upgrade to version 4.2.2 or 4.1.7 which contains the fix for this log injection vulnerability.

Recommended fix High confidence

4.2.2 or 4.1.7

  1. Locate the Apache CXF dependency in your project's build configuration (pom.xml, build.gradle, or similar)
  2. Update the CXF version to either 4.2.2 or 4.1.7
  3. Run your build tool to download and integrate the updated dependency (e.g., mvn clean install for Maven, ./gradlew build for Gradle)
  4. Verify the upgrade by running your application's test suite
  5. Redeploy the application with the updated dependency
Caveat Minor version upgrades within the same major version typically have low risk, but review CXF 4.2.2 and 4.1.7 release notes for any behavioral changes

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

Fix this in Cxf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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