Description
In Apache CXF's OAuth2 Dynamic Client Registration endpoint, the authorization server accepts and stores the `scope` value supplied in the client registration request verbatim, without validating it against an AS-defined allowlist. This could lead to a client self-assigning privileged scopes at registration time. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.
Published: 2026-08-06
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability resides in Apache CXF’s OAuth2 Dynamic Client Registration endpoint, where the authorization server stores the "scope" field supplied by a client without any validation against its own allowlist. This flaw enables a client to request and persist privileged scopes that it would normally be denied, effectively granting it broader permissions than intended. The weakness is captured by CWE‑304, indicating insufficient authorization checks. The impact is a serious privilege escalation for any client that manages or registers with the server, potentially granting unauthorized access to protected resources or administrative functions.

Affected Systems

Affected products are those provided by the Apache Software Foundation under the Apache CXF umbrella. Versions before 4.2.3, 4.1.8, or 3.6.12 lack the fix that enforces scope validation. Users should verify the version of Apache CXF in use and apply the corresponding update to eliminate the capability to self‑assign privileged scopes.

Risk and Exploitability

The CVSS score is not provided in the data, but the flaw allows an attacker who can register a client to obtain elevated privileges. The EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog, indicating no known active exploitation. Based on the description, the likely attack vector is a client registration request—typically exposed to any who can reach the endpoint—and the risk is moderate to high, especially in environments where client registration is open to untrusted parties.

Generated by OpenCVE AI on August 6, 2026 at 14:06 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Apache CXF to version 4.2.3, 4.1.8, or 3.6.12 to enable scope validation
  • If an upgrade is not immediately feasible, temporarily disable dynamic client registration or restrict it to trusted clients until the patch is applied
  • Configure the authorization server to enforce a strict allowlist of scopes for all client registrations, ensuring that only approved scopes can be requested

Generated by OpenCVE AI on August 6, 2026 at 14:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 06 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache cxf
Vendors & Products Apache
Apache cxf

Thu, 06 Aug 2026 12:00:00 +0000

Type Values Removed Values Added
Description In Apache CXF's OAuth2 Dynamic Client Registration endpoint, the authorization server accepts and stores the `scope` value supplied in the client registration request verbatim, without validating it against an AS-defined allowlist. This could lead to a client self-assigning privileged scopes at registration time. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.
Title Apache CXF: OAuth2 Dynamic Client Registration Scope Self-Escalation
Weaknesses CWE-304
References

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-08-06T15:19:29.688Z

Reserved: 2026-07-09T14:46:58.308Z

Link: CVE-2026-61466

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-06T14:30:04Z

Weaknesses
  • CWE-304

    Missing Critical Step in Authentication