CVE-2026-50629

HIGHPre-NVD 5.38.2▲
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-06-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 2.9.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
8.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

Published

June 12, 2026

Last Modified

August 7, 2026

Advisory Details (2)

Auto-updated Jun 12, 2026
Patch available.
generic

oss-security - CVE-2026-50629: Apache CXF: OAuth2: Log Injection via Unsanitized Client Identifier

http://www.openwall.com/lists/oss-security/2026/06/11/6

Vendor Advisories for CVE-2026-50629(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.cxf:cxf-rt-rs-security-oauth22.6.0 ... 4.1.6 (159 versions)
  • 4.2.0 up to 4.2.2: fixed in 4.2.2
  • every version up to 4.1.7: fixed in 4.1.7
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 257 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 08:39 UTCOSV refresh
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:27 UTCEPSS rescore
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-14 04:04 UTCEG score recompute
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-10 09:35 UTCEPSS rescore
  25. 2026-09-08 22:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-30 23:48 UTCEG score recompute
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-28 21:41 UTCEPSS rescore
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-26 14:46 UTCEPSS rescore
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-24 23:51 UTCEG score recompute
  15. 2026-08-23 10:38 UTCEG score recompute
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 09:55 UTCEG score recompute
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 08:48 UTCEG score recompute
  21. 2026-08-20 08:48 UTCGHSA enrichment
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-19 13:46 UTCEG score recompute
  24. 2026-08-19 13:46 UTCGHSA enrichment
  25. 2026-08-18 13:48 UTCEPSS rescore
  26. 2026-08-17 13:47 UTCEPSS rescore
  27. 2026-08-17 12:30 UTCGHSA enrichment
  28. 2026-08-17 00:12 UTCEG score recompute
  29. 2026-08-17 00:12 UTCGHSA enrichment
  30. 2026-08-16 14:56 UTCEPSS rescore
  31. 2026-08-16 11:55 UTCEG score recompute
  32. 2026-08-16 11:55 UTCGHSA enrichment
  33. 2026-08-16 02:14 UTCEPSS rescore
  34. 2026-08-15 23:40 UTCGHSA enrichment
  35. 2026-08-15 11:01 UTCEG score recompute
  36. 2026-08-15 11:01 UTCGHSA enrichment
  37. 2026-08-15 01:30 UTCEPSS rescore
  38. 2026-08-14 22:44 UTCGHSA enrichment
  39. 2026-08-14 10:28 UTCGHSA enrichment
  40. 2026-08-13 22:12 UTCEG score recompute
  41. 2026-08-13 22:12 UTCGHSA enrichment
  42. 2026-08-13 22:00 UTCEPSS rescore
  43. 2026-08-13 04:25 UTCGHSA enrichment
  44. 2026-08-12 16:10 UTCEG score recompute
  45. 2026-08-12 16:10 UTCGHSA enrichment
  46. 2026-08-12 13:51 UTCEPSS rescore
  47. 2026-08-12 03:54 UTCGHSA enrichment
  48. 2026-08-11 15:35 UTCEG score recompute
  49. 2026-08-11 15:35 UTCGHSA enrichment
  50. 2026-08-11 03:18 UTCEG score recompute
  51. 2026-08-11 03:18 UTCGHSA enrichment
  52. 2026-08-11 00:00 UTCEPSS rescore
  53. 2026-08-10 15:02 UTCGHSA enrichment
  54. 2026-08-10 02:44 UTCGHSA enrichment
  55. 2026-08-09 14:29 UTCEG score recompute
  56. 2026-08-09 14:29 UTCGHSA enrichment
  57. 2026-08-09 13:46 UTCEPSS rescore
  58. 2026-08-09 02:13 UTCEG score recompute
  59. 2026-08-09 02:13 UTCGHSA enrichment
  60. 2026-08-08 16:37 UTCEPSS rescore
  61. 2026-08-08 13:57 UTCGHSA enrichment
  62. 2026-08-08 01:41 UTCEG score recompute
  63. 2026-08-08 01:41 UTCGHSA enrichment
  64. 2026-08-07 13:26 UTCGHSA enrichment
  65. 2026-08-07 12:48 UTCEG score recompute
  66. 2026-08-07 12:48 UTCGHSA enrichment
  67. 2026-08-07 08:44 UTCGHSA enrichment
  68. 2026-08-06 20:28 UTCEG score recompute
  69. 2026-08-06 20:28 UTCGHSA enrichment
  70. 2026-08-06 13:47 UTCEPSS rescore
  71. 2026-08-06 08:12 UTCGHSA enrichment
  72. 2026-08-05 19:56 UTCEG score recompute
  73. 2026-08-05 19:56 UTCGHSA enrichment
  74. 2026-08-05 19:17 UTCEPSS rescore
  75. 2026-08-04 15:47 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-50629?
CVE-2026-50629 is a high vulnerability published on June 12, 2026. 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…
When was CVE-2026-50629 disclosed?
CVE-2026-50629 was first published on June 12, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50629 actively exploited?
CVE-2026-50629 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50629?
CVE-2026-50629 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.2 (HIGH).
How do I remediate CVE-2026-50629?
A fix for CVE-2026-50629 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50629 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50629

Explore →

Is Your Infrastructure Affected by CVE-2026-50629?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.