dbcve.org
CxfApplication · Apache

CVE-2026-50630

MEDIUM · 6.5 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 →
74/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
A CRLF injection vulnerability exists in the OAuth2 AuthorizationUtils class. When constructing the WWW-Authenticate response header, the 'realm' parameter is concatenated without sanitizing Carriage Return (CR) and Line Feed (LF) characters. If an attacker can control the realm value, they can inject arbitrary HTTP headers or split the HTTP response entirely. 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

A CRLF injection vulnerability exists in the OAuth2 AuthorizationUtils class where the 'realm' parameter is concatenated into the WWW-Authenticate response header without sanitizing Carriage Return (CR) and Line Feed (LF) characters. An attacker who can control the realm value can inject arbitrary HTTP headers or perform HTTP response splitting attacks.

MitigationUpgrade to version 4.2.2 or 4.1.7 of the affected OAuth2 library, which includes proper sanitization of CR/LF characters in the realm parameter.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installation
    Search for CXF JAR files (cxf-*.jar) in your application classpath, lib directories, or dependency manifests (Maven pom.xml, Gradle build.gradle). Use commands like: find . -name "cxf-*.jar" or grep -r "org.apache.cxf" pom.xml
    Affected if Apache CXF is present in the environment
  2. Determine CXF version
    Check the CXF JAR file name for version (e.g., cxf-core-4.2.1.jar) or inspect the MANIFEST.MF file inside the JAR for the Implementation-Version attribute. For Maven projects, run: mvn dependency:tree | grep cxf
    Affected if Version is < 4.1.7 OR >= 4.2.0 AND < 4.2.2
  3. Verify OAuth2 module usage
    Search your codebase for imports or usage of OAuth2-related classes: org.apache.cxf.rs.security.oauth2.*, particularly AuthorizationUtils or any realm configuration. Check web.xml or application configuration for CXF OAuth2 filter registration.
    Affected if The application uses CXF's OAuth2 security features with realm configuration
  4. Inspect realm configuration
    Search configuration files (XML, properties, or YAML) for 'realm' settings related to OAuth2 or WWW-Authenticate headers. Look for patterns like: oauth2.realm, security.realm, or realm= in your CXF configuration.
    Affected if A realm value is explicitly configured in OAuth2 settings
  5. Check for untrusted realm input sources
    Review code that passes user-controlled input into the realm parameter of AuthorizationUtils. Search for: new AuthorizationInfo(..., realm, ...) or realm= request parameters without validation.
    Affected if The realm parameter accepts external/user-controlled input without validation

You are affected if you run Apache CXF with a version in the affected ranges AND use OAuth2 AuthorizationUtils with a configurable realm parameter that could accept external input.

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 of the affected OAuth2 library, which includes proper sanitization of CR/LF characters in the realm parameter.

Recommended fix High confidence

4.2.2 (or 4.1.7 for CXF 4.1.x line)

  1. Identify all Apache CXF dependencies in the project (e.g., cxf-core, cxf-rt-security-oauth2) by reviewing pom.xml or build.gradle
  2. Upgrade Apache CXF to version 4.2.2 (or 4.1.7 for those on the 4.1.x line)
  3. For Maven projects: Update the <version> tag for each CXF dependency to 4.2.2 (or 4.1.7)
  4. For Gradle projects: Update the CXF dependency version to 4.2.2 (or 4.1.7)
  5. Run dependency resolution to ensure no version conflicts exist (mvn dependency:tree or gradle dependencies)
  6. Rebuild the application and run tests to verify the upgrade does not break existing functionality
  7. Redeploy the updated application

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

Fix this in Cxf Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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