MRemoteNG weak key derivation exposes saved connection passwords
Confirmed in MRemoteNG 1.76.20, and other versions may also be vulnerable. The checked facts name no fixed version or vendor patch.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
MRemoteNG, a remote connection manager, uses a single unsalted MD5 hash with no iterations to derive the key that protects stored connection passwords. An attacker who can reach the encrypted data, without logging in to the software, can attempt to crack the passphrase offline and then decrypt every saved password; if the default passphrase is used, no cracking is needed because the key comes from a publicly known value.
Written by a model
Original description
MRemoteNG uses single MD5 hash with no salt and no iterations for key-derivation. An attacker who obtains the encrypted data can brute-force a weak or moderate passphrase offline at extreme speed and then decrypt every stored connection password. When the default passphrase is in use, no cracking is needed at all; the key is derived from a publicly known value.
Vendor did not provide the range of vulnerable versions. Only version 1.76.20 was tested and confirmed vulnerable. Other versions may also be vulnerable.
Who should check
Teams running MRemoteNG, especially version 1.76.20, which is confirmed vulnerable; other versions may also be affected.
“Only version 1.76.20 was tested and confirmed vulnerable.”
What to do
Workaround: The checked facts name no workaround. They note that with the default passphrase the key is derived from a publicly known value, so the default passphrase offers no protection against decryption.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-87868 (Use of weak hash in MRemoteNG), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-87868 (entry last updated 2026-11-19):
Affected:
- MRemoteNG MRemoteNG: versions 1.76.20
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- MRemoteNG version 1.76.20 is confirmed vulnerable; other versions may also be vulnerable. (source: https://cert.pl/en/posts/2026/11/CVE-2026-87867/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-87868 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-87868 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cert.pl/en/posts/2026/11/CVE-2026-87867
- https://cert.pl/en/posts/2026/11/CVE-2026-87867/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-87868
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-87868"}.Affected versions
- MRemoteNG MRemoteNG1.76.20
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-87868 |
| Record | NVD · CVE-2026-87868 |
| Other links 1 | |
| Link | cert.pl · en/posts/2026/11/CVE-2026-87867 |
Questions about CVE-2026-87868
Is CVE-2026-87868 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?
MRemoteNG encrypts stored connection passwords with a key derived from a weak hash. Someone who obtains the encrypted data can brute-force a weak or moderate passphrase offline and decrypt every stored connection password.
Source: cert.pl
Which versions are affected by CVE-2026-87868?
MRemoteNG: version 1.76.20.
Source: cve.now feed data
Am I affected, and how do I check?
Only MRemoteNG version 1.76.20 was tested and confirmed vulnerable. Other versions may also be vulnerable. The version in use can be checked in the application, and the default passphrase setting determines whether the key comes from a publicly known value.
Source: cert.pl
How do I fix CVE-2026-87868?
The checked facts do not name a fixed version or vendor patch identifiers for this vulnerability, so no upgrade target can be given from these facts.
Source: cert.pl
What if there's no patch?
The checked facts name no workaround. They note that with the default passphrase the key is derived from a publicly known value, so the default passphrase offers no protection against decryption.
Source: cert.pl
Related
- CVE-2026-87867Improper Certificate Validation in MRemoteNG
- CVE-2026-109805Weak Cryptography in SAP NetWeaver and ABAP Platform (Application Server ABAP)
- CVE-2026-77312Flyto2 Core: Arbitrary file write via unguarded data.*/file. modules (incomplete fix of CVE-2026-67429)
- CVE-2026-133323A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an…
- CVE-2026-131253Remote Code Execution (RCE) through the App Wizard in Splunk SOAR
- CVE-2026-129048WordPress WP Photo Album Plus plugin <= 9.3.06.003 - Remote Code Execution (RCE) vulnerability
No corrections so far. Something wrong on this page? Report an error.