CVE-2026-50559

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
Trending — Patch released this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Quarkus is a Java framework for building cloud-native applications. Prior to versions 3.37.0, 3.36.3, 3.33.2.1, 3.33.3, 3.27.4.1, 3.27.5, and 3.20.6.2, Quarkus HTTP path-based authorization policies can be bypassed using encoded semicolons (%3B) to smuggle matrix parameters past the security layer, and using encoded slashes (%2F) or backslashes (%5C) to access protected static resources. This is a distinct issue from CVE-2026-39852, which addressed only literal semicolon stripping. Versions 3.37.0, 3.36.3, 3.33.2.1, 3.33.3, 3.27.4.1, 3.27.5, and 3.20.6.2 contain a patch.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
36.1%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 6, 2026

Advisory Details (1)

Auto-updated Jun 19, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Authentication/Authorization Bypass via Advanced Path Normalization Vulnerabilities · Advisory · quarkusio/quarkus · GitHub

https://github.com/quarkusio/quarkus/security/advisories/GHSA-qcxp-gm7m-4j5v

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatquarkus-vertx-http2026-07-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 34× in last 7d / 89× 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.

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

Frequently asked(5)

What is CVE-2026-50559?
CVE-2026-50559 is a high vulnerability published on June 19, 2026. Quarkus is a Java framework for building cloud-native applications. Prior to versions 3.37.0, 3.36.3, 3.33.2.1, 3.33.3, 3.27.4.1, 3.27.5, and 3.20.6.2, Quarkus HTTP path-based authorization policies can be bypassed using encoded semicolons (%3B) to smuggle matrix parameters past the security layer,…
When was CVE-2026-50559 disclosed?
CVE-2026-50559 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50559 actively exploited?
CVE-2026-50559 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50559?
CVE-2026-50559 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50559?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50559, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50559

Explore →

Is Your Infrastructure Affected by CVE-2026-50559?

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