# Apache CXF OAuth2 Missing JWT Audience and Issuer Validation in Access Token Validator Advisory record · `GHSA-9mrv-8pvf-hf4m` - **Identifiers:** `GHSA-9mrv-8pvf-hf4m` · `CVE-2026-50627` - **State:** Confirmed - **Severity:** CVSS 9.1 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-289](https://cwe.mitre.org/data/definitions/289.html) · [CWE-303](https://cwe.mitre.org/data/definitions/303.html) - **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-289](https://agentprime.io/advisories/tag/cwe-289.md) - **Published:** 12 Jun 2026 - **Updated:** 20 Aug 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 12 Jun 2026, 12:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.1: 9.0 or more. How we decide what’s critical: ## Affected packages - `org.apache.cxf:cxf-rt-rs-security-oauth2` (Maven): affected `>=4.2.0, <4.2.2 || <4.1.7`; fixed in `4.2.2`, `4.1.7` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache CXF's cxf-rt-rs-security-oauth2 package, versions from 4.2.0 before 4.2.2 and before 4.1.7, does not validate the audience claim of incoming JWT access tokens in its JwtAccessTokenValidator class. An attacker holding a token issued for one resource server can replay it against a different resource server and have it accepted. The source gives few details on the exact attacker position required. Upgrade to version 4.2.2 or 4.1.7. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.045, the 91st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 12 Jun 2026, 10:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-50627) - 31 Oct 2026, 14:19 UTC: First seen by agentprime - 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9mrv-8pvf-hf4m) ## Sources - [GitHub Advisory Database: GHSA-9mrv-8pvf-hf4m](https://github.com/advisories/GHSA-9mrv-8pvf-hf4m) - [OSV: GHSA-9mrv-8pvf-hf4m](https://osv.dev/vulnerability/GHSA-9mrv-8pvf-hf4m) - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .