rConfig Core 8.2.3 < 8.2.13 Cleartext Credential Exposure via API
- Exploited
- No known exploitation
- Fix
- Fixed in 8.2.13
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects rConfig Core from 8.2.3 before 8.2.13 Applies to rConfig Core only; rConfig Pro is not affected
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
rConfig Core versions from 8.2.3 before 8.2.13 let an authenticated user read the stored SSH, Telnet, and enable passwords for managed network devices in cleartext through its device-credentials API. The attack can be carried out remotely over the network by any account with low-privilege login access.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects rConfig Core from 8.2.3 before 8.2.13 Applies to rConfig Core only; rConfig Pro is not affectedUpgrade to a fixed version: 8.2.13.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- rConfig rConfig
From 8.2.3 · fixed in 8.2.13
Evidence 3
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-70555
Is CVE-2026-70555 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user of rConfig Core can retrieve stored managed device credentials in cleartext through the API, including SSH, Telnet, and enable passwords for all managed devices. The credentials are exposed in readable form rather than protected.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-70555?
rConfig: from 8.2.3 before 8.2.13.Source: cve.now feed data
Am I affected, and how do I check?
rConfig Core versions from 8.2.3 before 8.2.13 are affected. rConfig Pro is not affected. To check, look at the rConfig Core version in the application's settings or about page and see whether it falls in that range.Source: vulncheck.com, github.com
How do I fix CVE-2026-70555?
Upgrade rConfig Core to version 8.2.13, which is the listed fixed version. No workaround is listed in the facts.Source: vulncheck.com, github.com