CVE-2026-4434
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper certificate validation in the PAM propagation WinRM connections allows a network attacker to perform a man-in-the-middle attack via disabled TLS certificate verification.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper certificate validation in PAM propagation for WinRM connections allows man-in-the-middle attacks due to disabled TLS certificate verification. An attacker on the network can intercept and manipulate communications between client and server by presenting a fraudulent certificate that is not being validated.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.1.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Devolutions Server versionCheck the installed version of Devolutions Server on your system. This is typically found in the application properties, about screen, or installed programs list.Affected if The installed version is prior to 2026.1.6.0
-
Verify PAM module configuration for WinRMInspect the PAM (Privileged Access Management) module configuration to determine if WinRM propagation is enabled. Look for settings related to WinRM connection propagation within the PAM configuration.Affected if PAM propagation for WinRM connections is enabled and configured
-
Examine TLS certificate validation settingsCheck the WinRM connection settings within the PAM module configuration for TLS certificate verification. Look for options that control certificate validation during WinRM connections.Affected if TLS certificate validation is explicitly disabled or set to bypass verification for WinRM connections
-
Review WinRM client configurationInspect the WinRM client settings on the system for any configuration that disables certificate validation, such as skip-CN-check or similar trust bypass options.Affected if WinRM client is configured to skip certificate validation
You are affected if running Devolutions Server versions prior to 2026.1.6.0 with PAM propagation enabled for WinRM connections and TLS certificate validation disabled in the configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.1.6.0
Enable TLS certificate validation in WinRM connections and ensure PAM modules properly verify server certificates before establishing connections. Use valid certificates from trusted Certificate Authorities and implement certificate pinning where appropriate.
2026.1.6.0
- 1. Identify the current Devolutions Server version by checking the application or documentation
- 2. Create a complete backup of the Devolutions Server database and configuration
- 3. Download Devolutions Server version 2026.1.6.0 or later from the official Devolutions website
- 4. Install the upgrade following the vendor's standard upgrade procedure
- 5. Verify the upgrade was successful by checking the application version
- 6. Test WinRM PAM propagation connections to confirm TLS certificate validation is now properly enabled
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4434 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4434 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data