CVE-2026-63102

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-07-20. the CNA's CVSS baseline 5.4; sources differ by 0.0.

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

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

rConfig Core before 8.2.8 contains a privilege escalation vulnerability that allows authenticated users to assign arbitrary roles to any account by submitting an unvalidated role field through the Users API during user creation or profile updates. Attackers can exploit the missing allowlist validation and absent admin-level authorization check in StoreUserRequest to mass-assign the Admin role directly to the User model, granting access to privileged features. rConfig Pro and Enterprise are not affected.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
24(Track)
EPSS
16.0%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 21, 2026

Advisory Details (4)

Auto-updated Jul 20, 2026
Patch available. Sources: github_commit, github_pr, github_release.
generic

rConfig Core < 8.2.8 Privilege Escalation via Users API role field | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rconfig-privilege-escalation-via-users-api-role-field
github_release Patch Available

rConfig V8 Core 8.2.8

Patch available: rconfig/rconfig core-8.2.8

https://github.com/rconfig/rconfig/releases/tag/core-8.2.8
github_pr Patch Available

Tighten role field validation on user create/update

Patch available: rconfig/rconfig core-8.2.8 (PR #325 merged 2026-07-17)

https://github.com/rconfig/rconfig/pull/325
github_commit Patch Available

commit 84822f4051ed (rconfig/rconfig)

Patch available: rconfig/rconfig core-8.2.8 (contains commit 84822f4051ed)

https://github.com/rconfig/rconfig/commit/84822f4051ed97d651b1b4d191c6da2aa8c3c037

Vendor Advisories for CVE-2026-63102(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 13× 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-22 23:38 UTCEG score recompute
  2. 2026-07-22 23:37 UTCGHSA enrichment
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-20 23:14 UTCGHSA enrichment
  8. 2026-07-20 23:11 UTCGHSA enrichment
  9. 2026-07-20 19:00 UTCEG score recompute
  10. 2026-07-20 18:59 UTCGHSA enrichment
  11. 2026-07-20 16:37 UTCEG score recompute
  12. 2026-07-20 16:03 UTCEG score recompute
  13. 2026-07-20 16:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63102?
CVE-2026-63102 is a medium vulnerability published on July 20, 2026. rConfig Core before 8.2.8 contains a privilege escalation vulnerability that allows authenticated users to assign arbitrary roles to any account by submitting an unvalidated role field through the Users API during user creation or profile updates. Attackers can exploit the missing allowlist…
When was CVE-2026-63102 disclosed?
CVE-2026-63102 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63102 actively exploited?
CVE-2026-63102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-63102?
CVE-2026-63102 has a CVSS v4.0 base score of 5.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63102?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63102, 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-63102

Explore →

Is Your Infrastructure Affected by CVE-2026-63102?

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

Start Free Scan →Browse All CVEs