CVE-2026-19130

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

Score 5.8 from GitHub Security Advisory published 2026-08-12. a secondary CVSS source baseline 5.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.8Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in the provider-credential-controller component of multicluster-engine (MCE). An attacker with specific permissions on the hub cluster, and knowledge of a prior credential value, could exploit an authorization bypass vulnerability. By manipulating copiedFrom labels, the attacker could intercept newly rotated provider credentials, leading to unauthorized information disclosure. This allows access to sensitive credentials that should otherwise be protected.

CVSS v3
5.8
EG Score
5.8(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity58% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 12, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Aug 12, 2026
Patch available. Sources: redhat.
redhat

2512105 – (CVE-2026-19130) CVE-2026-19130 provider-credential-controller: provider-credential-controller: cross-namespace credential propagation via attacker-controlled copiedFrom labels bypasses authorization

https://bugzilla.redhat.com/show_bug.cgi?id=2512105
redhat Patch Available

CVE-2026-19130 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-19130

Patch Availability(6)

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(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 119× 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 147 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-19130?
CVE-2026-19130 is a medium vulnerability published on August 12, 2026. A flaw was found in the provider-credential-controller component of multicluster-engine (MCE). An attacker with specific permissions on the hub cluster, and knowledge of a prior credential value, could exploit an authorization bypass vulnerability. By manipulating copiedFrom labels, the attacker…
When was CVE-2026-19130 disclosed?
CVE-2026-19130 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19130 actively exploited?
CVE-2026-19130 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 84.5% of all scored CVEs.
What is the CVSS score of CVE-2026-19130?
CVE-2026-19130 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-19130?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19130, 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-19130

Explore →

Is Your Infrastructure Affected by CVE-2026-19130?

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