In this article
NetBird's browser RDP client stops warning after one accepted certificate
The NetBird dashboard's browser RDP client warns about an untrusted server certificate only once per page session. After you accept one certificate, every later prompt is accepted silently, including the warning that a certificate has changed.
A substitute RDP endpoint can then collect your RDP username and password. NetBird rates the flaw Medium, with a CVSS 4.0 score of 5.9, and classes it as improper certificate validation (CWE-295).
A page-wide flag that never resets hides the changed-certificate modal
The first acceptance sets a page-wide flag in the client. Nothing clears it, not even a disconnect or the end of a session. Normally the validation code marks a changed or unknown certificate as needing confirmation, and a modal warns you that the certificate has changed. With the flag set, that modal never reaches you.
This connection path forces TLS, CredSSP and NLA. The CredSSP/NLA handshake sends your credentials through TLS that ends at the attacker, who also renders the desktop you see. The attacker must be the RDP endpoint or sit on the path inside the WireGuard tunnel, and must serve a different certificate to a user who already accepted one in that tab. Reconnects, including automatic ones when you resize the window, make this easy.
Dashboard 2.19.0 through 2.95.x using browser RDP is affected
Dashboard versions from 2.19.0 up to, but not including, 2.96.0 are affected. The flag arrived with the browser client in 2.19.0. NetBird Cloud and self-hosted deployments are both affected when you use the browser RDP client. The NetBird agent and the Android and iOS apps are not.
The advisory includes proof-of-concept steps: accept a peer's self-signed certificate with Remember unchecked, then connect to a peer with a different certificate. No modal appears and the session connects. NetBird notes that the flag lasts only until the page reloads, and that the attacker must already be a peer you are allowed to reach. It also points out that RDP hosts mostly use self-signed certificates, so the first prompt is already a click-through for most users.
Update the NetBird dashboard to 2.96.0
Upgrade the dashboard to 2.96.0. The release removes the page-wide flag. A certificate you accept now counts only for that host and fingerprint, and only while the page stays open.
NetBird states no formal workaround. Reloading the page clears the flag, since it lasts only until reload.
What the NetBird advisory text leaves unclear
The advisory text we have is cut off after the description of the per-host change, so the full behavior for changed fingerprints in 2.96.0 is not visible.
| Product | Affected | Fixed |
|---|---|---|
| NetBird dashboard (browser RDP client) | >= 2.19.0, < 2.96.0 | 2.96.0 |
Sources
This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].


Discussion