NVD / CVE Program· CNA apache

CVE-2026-50623: Apache CXF: Authentication Bypass in OAuth2 TokenIntrospectionService

MediumCVSS 4.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 19/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: Apache Software Foundation Apache CXF 3.6.12, 4.1.7, 4.2.2.

Low priority for now. Upgrade to Apache Software Foundation Apache CXF 3.6.12, 4.1.7, 4.2.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An authentication bypass vulnerability exists in the OAuth2 TokenIntrospectionService in Apache CXF. Due to a missing 'throw' keyword in the security context check, the introspection endpoint (/services/oauth2/introspect) can be accessed by any unauthenticated network attacker. However note that this is a safeguard only in the case that someone forgot to enable authentication on the service. Users are recommended to upgrade to version 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.

GHSA-542g-m3fx-q86f

Published: Jun 12, 2026
Updated: Nov 5, 2026
EPSS: 0.3% · 31th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 19 / 40 · 4.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	cxf	cpe:2.3:a:apache:cxf

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache CXF
- 4.2.0 and later · before 4.2.2affected · semver
- 4.0.0 and later · before 4.1.7affected · semver
- before 3.6.12affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache cxfbefore 3.6.12
apache cxf4.0.0 and later · before 4.1.7
apache cxf4.2.0 and later · before 4.2.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.apache.cxf:cxf-rt-rs-security-oauth2	from 4.2.0 · before 4.2.2	4.2.2
Maven	org.apache.cxf:cxf-rt-rs-security-oauth2	before 4.1.7	4.1.7

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2019-12419Apache CXF before 3.3.4 and 3.2.11 provides all of the components that are required to build a fully fledged OpenId Connect service.
43Plan
CVE-2010-2076Apache CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.2.9, as used in Apache ServiceMix, Apache Camel, Apache Chemistry…
42Plan
CVE-2012-2379Apache CXF 2.4.x before 2.4.8, 2.5.x before 2.5.4, and 2.6.x before 2.6.1, when a Supporting Token specifies a child WS-SecurityPolicy 1.1…
41Plan

Published before and after this one in the same product

← EarlierCVE-2026-44930May 22, 2026 · Apache CXF: LDAP Injection vulnerability in XKMS LDAP Repository
39Monitor
← EarlierCVE-2026-49875Jun 12, 2026 · Apache CXF: XML External Entity (XXE) Injection in W3CMultiSchemaFactory and EndpointReferenceUtils
39Monitor
Later →CVE-2026-50627Jun 12, 2026 · Apache CXF: OAuth2: Missing JWT Audience and Issuer Validation in Access Token Validator
37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Apache Software Foundation Apache CXF	3.6.12	Vendor (CNA)
Apache Software Foundation Apache CXF	4.1.7	Vendor (CNA)
Apache Software Foundation Apache CXF	4.2.2	Vendor (CNA)
Maven:org.apache.cxf:cxf-rt-rs-security-oauth2	4.1.7	Package registry (OSV)
Maven:org.apache.cxf:cxf-rt-rs-security-oauth2	4.2.2	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Guanping Zhang reported this vulnerability.finder

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-4441721 days apartApache CXF: Incomplete fix for CVE-2025-48913 (Untrusted JMS configuration can lead to RCE)
30Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: low · data can be read
Integrity: low · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: Low
Availability impact: None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

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

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

lists.apache.org/thread/ydzj8m5mqmjy13xgyj9mkk9hfff63qq7

Show all references (1 more)

www.openwall.com/lists/oss-security/2026/06/11/3

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records