Is CVE-2026-70555 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-70555 being exploited in the wild.

How severe is CVE-2026-70555?

Medium severity, with a CVSS score of 6.5, published 9 November 2026.

Which products and versions are affected?

rConfig Core 8.2.3 to before 8.2.13.

Is there a fix for CVE-2026-70555?

Yes: fixed in rConfig Core 8.2.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-70555 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-70555?

Check whether you run rConfig Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-70555: rConfig Core information disclosure in device-credentials API

CVE-2026-70555 · Severity: medium · CVSS 6.5 · Published 2026-11-09

rConfig Core is a configuration management system that stores SSH, Telnet, and enable passwords for managed network devices. An authenticated user can retrieve cleartext credentials for all managed devices through the REST API due to missing authorization checks and automatic decryption, allowing an attacker to exfiltrate stored plaintext credentials and compromise managed infrastructure.

Technologies: rConfig Core. Vendors: Rconfig.

Quick answers

Is CVE-2026-70555 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-70555 being exploited in the wild.
How severe is CVE-2026-70555?: Medium severity, with a CVSS score of 6.5, published 9 November 2026.
Which products and versions are affected?: rConfig Core 8.2.3 to before 8.2.13.
Is there a fix for CVE-2026-70555?: Yes: fixed in rConfig Core 8.2.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-70555 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-70555?: Check whether you run rConfig Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: rConfig Core 8.2.13

Technical details

The vulnerability exists in the device-credentials API endpoints (GET /api/device-credentials, GET /api/device-credentials/{id}, and GET /api/v1/device-credentials) which automatically decrypt stored credentials on read without performing proper authorization checks. An authenticated user with any valid token (including those seeded as the administrator account) can statelessly request these endpoints to retrieve all plaintext device passwords. The external v1 API endpoint accepts any valid token as the seeded administrator account, bypassing expected access controls.

Affected products

rConfig Core 8.2.3 to before 8.2.13

Timeline

2026-11-09: disclosed
2026-08-10: patched: rConfig Core 8.2.13 released with credential masking in v1 API

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.