CVE-2026-13603

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% 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: epss, secondary
Trending — 3 sources updated this week
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The payment integration pretix-oppwa provides support for the payment providers VR Payment, Hobex, and potentially others based on Oppwa's technology. The integration of Oppwa, following their official documentation, includes a step where the user is redirected from the payment provider back to our system with a query parameter like ?resourcePath=/v1/checkouts/{checkoutId}/payment in the URL. Our system is then supposed to fetch the status of the transaction from the URL given by baseUrl + resourcePath.

Our plugin pretix-oppwa did so insecurely by concatenating the parameter form the URL to the base domain of the API without further validation and, critically, without a / at the end of the baseUrl. Therefore, an attacker could inject a resourcePath argument in a way that causes pretix to call a different server instead. Since the request includes the access token (API key) of the Oppwa account, this would leak the access token, giving access to data contained in the payment provider's system. This is fixed with the release today by strictly validating the given API URL.

After installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.

CVSS v3
9.0
EG Score
9.0(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

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
Severity90% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 2, 2026
No patch confirmed yet.
generic

Security release 2026.5.3 of pretix and multiple plugins – pretix – Reinventing ticket sales for conferences, festivals, exhibitions, ...

https://pretix.eu/about/en/blog/20260701-release-2026-5-3/

Vendor Advisories for CVE-2026-13603(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 68× 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 404 total refreshes for this CVE.

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

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(5)

What is CVE-2026-13603?
CVE-2026-13603 is a critical vulnerability published on July 1, 2026. The payment integration pretix-oppwa provides support for the payment providers VR Payment, Hobex, and potentially others based on Oppwa's technology. The integration of Oppwa, following their official documentation, includes a step where the user is redirected from the payment provider back to our…
When was CVE-2026-13603 disclosed?
CVE-2026-13603 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13603 actively exploited?
CVE-2026-13603 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.4% of all scored CVEs.
What is the CVSS score of CVE-2026-13603?
CVE-2026-13603 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-13603?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13603, 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-13603

Explore →

Is Your Infrastructure Affected by CVE-2026-13603?

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