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.
CVE-2026-63102
Score 5.4 from GitHub Security Advisory published 2026-07-20. the CNA's CVSS baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 24(Track)EG Risk 24/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 computedSeverity54% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 16.0%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 21, 2026
Advisory Details (4)
Auto-updated Jul 20, 2026rConfig 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-fieldrConfig V8 Core 8.2.8
Patch available: rconfig/rconfig core-8.2.8
https://github.com/rconfig/rconfig/releases/tag/core-8.2.8Tighten 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/325commit 84822f4051ed (rconfig/rconfig)
Patch available: rconfig/rconfig core-8.2.8 (contains commit 84822f4051ed)
https://github.com/rconfig/rconfig/commit/84822f4051ed97d651b1b4d191c6da2aa8c3c037Vendor 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 14× in last 7d / 14× 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.
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 23:38 UTCEG score recompute
- 2026-07-22 23:37 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 23:14 UTCGHSA enrichment
- 2026-07-20 23:11 UTCGHSA enrichment
- 2026-07-20 19:00 UTCEG score recompute
- 2026-07-20 18:59 UTCGHSA enrichment
- 2026-07-20 16:37 UTCEG score recompute
- 2026-07-20 16:03 UTCEG score recompute
- 2026-07-20 16:02 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-63102?
When was CVE-2026-63102 disclosed?
Is CVE-2026-63102 actively exploited?
What is the CVSS score of CVE-2026-63102?
How do I remediate CVE-2026-63102?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63102
Is Your Infrastructure Affected by CVE-2026-63102?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.