CVE-2026-87867 json
Improper Certificate Validation in MRemoteNG
published 13h ago modified 10h ago also EUVD-2026-130326
- cvss
- 7.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
MRemoteNG establishes encrypted but unauthenticated channel with Microsoft SQL Server backend. Client accepts any certificate the server presents, including a self-signed certificate supplied by an attacker. An attacker positioned between the client and the SQL server (for example via ARP/DNS spoofing) can transparently pintercept the connection (man-in-the-middle) and read all traffic, including the encrypted connection-password table read and the database login.
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.
Is CVE-2026-87867 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
Affected products
- MRemoteNG MRemoteNG
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
cert.pl
/en/posts/2026/11/CVE-2026-87867
third-party-advisory
Sources
- CVE List CVE-2026-87867
- NVD CVE-2026-87867
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.