Skip to main content
VulnerabilityPublished

CVE-2026-3224: Devolutions Server · Improper Authentication, CWE-347: Improper Verification of Cryptographic Signature

Affects Devolutions ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
DevolutionsServerAffected
  • <=2025.3.15.0
Fixed in–

AI-suggested

  1. Monitor Devolutions’ official channels for the release of a security patch addressing CVE-2026-3224 and apply it immediately upon availability.
  2. Until a patch is available, consider disabling Microsoft Entra ID (Azure AD) authentication mode in Devolutions Server or restrict its usage to trusted networks and users only.
  3. Implement additional token validation layers, such as validating JWT signatures externally or using a Web Application Firewall (WAF) with custom rules to detect anomalous JWTs.
  4. Enforce strict logging and monitoring of authentication events to detect suspicious login attempts or token anomalies.
  5. Conduct regular audits of user accounts and permissions within Devolutions Server and Microsoft Entra ID to limit the impact of potential compromises.
  6. Educate security teams about the vulnerability to ensure rapid incident response if exploitation is suspected.
  7. Use network segmentation and zero trust principles to minimize lateral movement if an attacker gains access.
  8. Review and tighten the configuration of identity providers and token issuance policies to reduce the risk of token forgery.
  9. Consider multi-factor authentication (MFA) enforcement on all critical accounts to add an additional layer of defense.
  10. Engage with Devolutions support for guidance and interim protective measures.

Description

Authentication bypass in the Microsoft Entra ID (Azure AD) authentication mode in Devolutions Server 2025.3.15.0 and earlier allows an unauthenticated user to authenticate as an arbitrary Entra ID user via a forged JSON Web Token (JWT).

References

Community reviews

Loading reviews…