CVE-2026-77915
Unauthenticated registration yields Admin accounts in rConfig
Is CVE-2026-77915 being exploited?
Not confirmed. CVE-2026-77915 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-77915?
CVE-2026-77915 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-77915?
Yes. A fix has been recorded for CVE-2026-77915. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-77915 affect?
CVE-2026-77915 affects rConfig versions prior to 8.2.13 (rConfig 8.0.0 - 8.2.12). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-77915?
Upgrade to rConfig 8.2.13; disable registration, rotate credentials, and audit accounts
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can self-register Admin accounts, access stored device credentials, user data, and issue API tokens.
Immediate action required
- affected>= 8.0.0 and < 8.2.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.