CVE-2026-70555: rConfig Core 8.2.3 < 8.2.13 Cleartext Credential Exposure via API

Published Nov 9, 2026
·
Updated

rConfig Core 8.2.3 before 8.2.13 contains an information disclosure vulnerability that allows authenticated users to retrieve cleartext SSH, Telnet, and enable passwords for managed devices through the device-credentials API due to automatic decryption on read and missing authorization checks. Attackers can request GET /api/device-credentials, GET /api/device-credentials/{id}, or the external GET /api/v1/device-credentials endpoint, which authenticates any valid token as the seeded administrator account, to statelessly exfiltrate all stored plaintext device credentials. rConfig Pro is not affected.

Affected Software

1 affected component
rConfig rConfig Core>=8.2.3<8.2.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade rConfig Core to a version that resolves this vulnerability.

    Fixed in 8.2.13

Event History

Nov 9, 2026
CVE Published
via MITRE·06:24 PM
Data Sourced
via MITRE·06:24 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

rConfig Core versions 8.2.3 through versions before 8.2.13 are affected. rConfig Pro is not affected.

2

What does an attacker need to retrieve stored device credentials?

The attacker needs a valid authentication token. The external /api/v1/device-credentials endpoint treats any valid token as the seeded administrator account, allowing access to stored credentials.

3

What information can be exposed?

An authenticated attacker can retrieve cleartext SSH, Telnet, and enable passwords for managed devices. The affected API endpoints automatically decrypt credentials when they are read.

4

Which API endpoints should be reviewed for exposure?

Review access to GET /api/device-credentials, GET /api/device-credentials/{id}, and GET /api/v1/device-credentials. Requests to these endpoints may indicate attempted or successful credential retrieval.

5

What should be done if exposure is suspected?

Upgrade to rConfig Core 8.2.13 or later, then rotate SSH, Telnet, and enable passwords stored for managed devices. Also invalidate and replace authentication tokens that may have been available to untrusted users.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203