CVE-2026-17569 Vulnerability Analysis & Exploit Intelligence

Improper access control in the NetBox synchronizer in Devolutions Server allows an authenticated user with view-only permission on an entry to obtain a stored API token via the partial connection endpoint. This issue affects : * Devolutions Server 2026.2.4.0 through 2026.2.12.0 * Devolutions Server 2026.1.23.0 and earlier

Published Jul 27, 2026Updated Jul 28, 2026Sources: cvelistV5, DEVOLUTIONS

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

devolutions

server

CVSS base

4.3

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

devolutions

Products (1)

server

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
4.3	CVSS 3.1	MEDIUM	—	—	cvelistV5

Weakness & attack patterns

CWE-522

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1552.004Unsecured Credentials: Private Keys
T1558.003Steal or Forge Kerberos Tickets: Kerberoasting
T1543Create or Modify System Process

References

1 on the record

devolutions.net/security/advisories/DEVO-2026-0026/
reference

Elsewhere on this site

devolutionsevery CVE for this vendor
CWE-522other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.