Server-side request forgery in the Jira ticketing filter lookup in Devolutions Server 2026.2.22.0 and earlier allows an authenticated…
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.2.23.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026.2.23.0.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure?/25Exposure: unknown (data gap). No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity?/10Severity: unknown (data gap). No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
CVE-2026-121580 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Server; fixed in 2026.2.23.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- Fix
- Fixed in 2026.2.23.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Devolutions Server, a password and credential management platform, is affected through its Jira ticketing integration. An authenticated user with low privileges could exploit this flaw to obtain the stored Jira service account credentials, potentially gaining unauthorized access to the connected Jira system.
Read the original description
Server-side request forgery in the Jira ticketing filter lookup in Devolutions Server 2026.2.22.0 and earlier allows an authenticated low-privileged user to obtain the stored Jira service account credentials via an attacker-controlled server address in the request.
What to do
Upgrade to a fixed version: 2026.2.23.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Devolutions Server
fixed in 2026.2.23.0
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121580
Is CVE-2026-121580 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
Which versions are affected by CVE-2026-121580?
Server: before 2026.2.23.0.Source: cve.now feed data
How do I fix CVE-2026-121580?
Upgrade to a fixed version: 2026.2.23.0.Source: cve.now feed data