Skip to main content
Menu
CVEs

MRemoteNG man-in-the-middle via unvalidated SQL Server certificate

CVE-2026-87867Published November 19, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

MRemoteNG accepts any certificate presented by the Microsoft SQL Server backend, including a self-signed one supplied by an attacker, so its encrypted connection to that server is not actually authenticated. An attacker on the adjacent network who can sit between the client and the SQL server (for example through ARP or DNS spoofing) can intercept the connection without logging in or any user action and read the traffic, including the connection-password table and the database login.

Written by a model

Original description

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.

Who should check

Teams running MRemoteNG 1.76.20 (other versions unconfirmed) that connect to Microsoft SQL Server backends.

“Only version 1.76.20 was tested and confirmed vulnerable.”

cert.pl

What to do

Workaround: The checked facts give no workaround or fix. Until one is published, limit the exposed setup by avoiding the MRemoteNG to SQL Server backend connection on networks where an attacker could sit between the client and the server.

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-87867 (Improper Certificate Validation 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-87867 (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 connects to a Microsoft SQL Server backend over an encrypted but unauthenticated channel. (source: https://cert.pl/en/posts/2026/11/CVE-2026-87867/)
- Only version 1.76.20 was tested and 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: adjacent access, no login, no user action.
CISA KEV: CVE-2026-87867 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-87867 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-87867
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-87867"}.

Affected versions

cve.now Index

12Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure?/25Unknown. Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-87867
RecordNVD · CVE-2026-87867
Other links 1
Linkcert.pl · en/posts/2026/11/CVE-2026-87867

Questions about CVE-2026-87867

Is CVE-2026-87867 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 connects to a Microsoft SQL Server backend over a channel that is encrypted but not authenticated. An attacker positioned between the client and the SQL server can intercept the connection and read all traffic, including the encrypted connection-password table and the database login.

Source: cert.pl

Which versions are affected by CVE-2026-87867?

MRemoteNG: version 1.76.20.

Source: cve.now feed data

Am I affected, and how do I check?

The only version tested and confirmed vulnerable is 1.76.20, and other versions may also be vulnerable. The exposed setup is MRemoteNG using a Microsoft SQL Server backend, so check the installed MRemoteNG version and whether it connects to a SQL Server backend.

Source: cert.pl

How do I fix CVE-2026-87867?

The checked facts name no fixed version and no vendor patch, so no upgrade target can be given. Check the vendor's advisory for an update before relying on any version.

Source: cert.pl

What if there's no patch?

The checked facts give no workaround or fix. Until one is published, limit the exposed setup by avoiding the MRemoteNG to SQL Server backend connection on networks where an attacker could sit between the client and the server.

Source: cert.pl

No corrections so far. Something wrong on this page? Report an error.