CVE-2026-19625

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: None knownExposed services: Not assessed

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

When a Quarkus application has multiple endpoints secured by individual OIDC provider tenants, such as "/oidc-provider1" that is secured by the OIDC Provider 1 and "/oidc-provider2" that is secured by the OIDC Provider 2, and an optional token introspection cache is also enabled, then a valid token issued by the OIDC Provider 1 that can be used to access "/oidc-provider1" can also be used to access "/oidc-provider2" that is secured by another OIDC Provider 2.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100CISA SSVC

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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 8, 2026

Last Modified

September 10, 2026

Advisory Details (1)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

Security Bulletin: IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities

https://www.ibm.com/support/pages/node/7286498

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 44× 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-10-04 23:23 UTCEG score recompute
  2. 2026-10-04 23:21 UTCEPSS rescore
  3. 2026-10-04 00:29 UTCEG score recompute
  4. 2026-10-03 00:14 UTCEG score recompute
  5. 2026-10-02 00:28 UTCEG score recompute
  6. 2026-10-01 19:49 UTCEPSS rescore
  7. 2026-10-01 01:06 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-30 02:12 UTCEG score recompute
  10. 2026-09-29 15:20 UTCEPSS rescore
  11. 2026-09-28 20:27 UTCEG score recompute
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 20:49 UTCEG score recompute
  14. 2026-09-27 13:47 UTCEPSS rescore
  15. 2026-09-26 21:55 UTCEG score recompute
  16. 2026-09-26 15:58 UTCEPSS rescore
  17. 2026-09-25 00:05 UTCEG score recompute
  18. 2026-09-24 01:09 UTCEG score recompute
  19. 2026-09-23 02:15 UTCEG score recompute
  20. 2026-09-22 03:21 UTCEG score recompute
  21. 2026-09-21 04:26 UTCEG score recompute
  22. 2026-09-20 05:28 UTCEG score recompute
  23. 2026-09-19 06:34 UTCEG score recompute
  24. 2026-09-18 19:27 UTCEPSS rescore
  25. 2026-09-18 07:39 UTCEG score recompute
Show 19 more
  1. 2026-09-17 08:45 UTCEG score recompute
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 09:51 UTCEG score recompute
  4. 2026-09-16 05:14 UTCEPSS rescore
  5. 2026-09-15 10:57 UTCEG score recompute
  6. 2026-09-14 12:03 UTCEG score recompute
  7. 2026-09-13 16:46 UTCEPSS rescore
  8. 2026-09-13 13:06 UTCEG score recompute
  9. 2026-09-12 15:00 UTCEPSS rescore
  10. 2026-09-11 15:17 UTCEG score recompute
  11. 2026-09-11 14:52 UTCEPSS rescore
  12. 2026-09-11 09:36 UTCEPSS rescore
  13. 2026-09-10 16:23 UTCEG score recompute
  14. 2026-09-10 15:24 UTCEG score recompute
  15. 2026-09-10 14:56 UTCEG score recompute
  16. 2026-09-10 09:34 UTCEPSS rescore
  17. 2026-09-08 21:34 UTCEG score recompute
  18. 2026-09-08 20:30 UTCEG score recompute
  19. 2026-09-08 20:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19625?
CVE-2026-19625 is a medium vulnerability published on September 8, 2026. When a Quarkus application has multiple endpoints secured by individual OIDC provider tenants, such as "/oidc-provider1" that is secured by the OIDC Provider 1 and "/oidc-provider2" that is secured by the OIDC Provider 2, and an optional token introspection cache is also enabled, then a valid token…
When was CVE-2026-19625 disclosed?
CVE-2026-19625 was first published on September 8, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19625 actively exploited?
CVE-2026-19625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19625?
CVE-2026-19625 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19625?
No fix for CVE-2026-19625 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-19625?

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

Book a Demo →Browse All CVEs