Jira Server
Atlassian- Product type
- Other
- Catalog vulnerabilities
- 99
Severity across 99 analyzed records
en
Verify to analyze this security profile
As of 09/13/2026, within CyStack's analyzed data, Jira Server has 0 security vulnerabilities published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Jira Server and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2019-15002 | Exploitation statusNot known exploited | FixYes | Published02/11/2025 | SeverityMedium |
CVE-2022-36801 | Exploitation statusNot known exploited | FixYes | Published08/10/2022 | SeverityMedium |
CVE-2022-36799 | Exploitation statusNot known exploited | FixYes | Published08/01/2022 | SeverityHigh |
CVE-2021-43944 | Exploitation statusNot known exploited | FixYes | Published03/08/2022 | SeverityHigh |
CVE-2021-43945 | Exploitation statusNot known exploited | FixYes | Published02/28/2022 | SeverityUnknown |
CVE-2021-43941 | Exploitation statusNot known exploited | FixYes | Published02/15/2022 | SeverityUnknown |
CVE-2021-43953 | Exploitation statusNot known exploited | FixYes | Published02/15/2022 | SeverityUnknown |
CVE-2021-43952 | Exploitation statusNot known exploited | FixYes | Published02/15/2022 | SeverityUnknown |
CVE-2021-43947 | Exploitation statusNot known exploited | FixYes | Published01/06/2022 | SeverityHigh |
CVE-2021-43946 | Exploitation statusNot known exploited | FixYes | Published01/05/2022 | SeverityUnknown |
CVE-2021-43942 | Exploitation statusNot known exploited | FixYes | Published01/04/2022 | SeverityUnknown |
CVE-2021-41311 | Exploitation statusNot known exploited | FixYes | Published12/08/2021 | SeverityHigh |
CVE-2021-41309 | Exploitation statusNot known exploited | FixYes | Published12/08/2021 | SeverityMedium |
CVE-2021-41312 | Exploitation statusNot known exploited | FixYes | Published11/03/2021 | SeverityHigh |
CVE-2021-41310 | Exploitation statusNot known exploited | FixYes | Published11/01/2021 | SeverityUnknown |
CVE-2021-41313 | Exploitation statusNot known exploited | FixYes | Published11/01/2021 | SeverityUnknown |
CVE-2021-41308 | Exploitation statusNot known exploited | FixYes | Published10/26/2021 | SeverityUnknown |
CVE-2021-41307 | Exploitation statusNot known exploited | FixYes | Published10/26/2021 | SeverityHigh |
CVE-2021-41306 | Exploitation statusNot known exploited | FixYes | Published10/26/2021 | SeverityHigh |
CVE-2021-41305 | Exploitation statusNot known exploited | FixYes | Published10/26/2021 | SeverityHigh |
CVE-2021-41304 | Exploitation statusNot known exploited | FixYes | Published10/26/2021 | SeverityUnknown |
CVE-2021-39126 | Exploitation statusNot known exploited | FixYes | Published10/21/2021 | SeverityUnknown |
CVE-2021-39127 | Exploitation statusNot known exploited | FixYes | Published10/21/2021 | SeverityMedium |
CVE-2021-39128 | Exploitation statusNot known exploited | FixYes | Published09/16/2021 | SeverityHigh |
CVE-2021-39125 | Exploitation statusNot known exploited | FixYes | Published09/14/2021 | SeverityMedium |
CVE-2019-20101 | Exploitation statusNot known exploited | FixYes | Published09/14/2021 | SeverityMedium |
CVE-2021-39118 | Exploitation statusNot known exploited | FixYes | Published09/14/2021 | SeverityMedium |
CVE-2021-39123 | Exploitation statusNot known exploited | FixYes | Published09/14/2021 | SeverityHigh |
CVE-2021-39124 | Exploitation statusNot known exploited | FixYes | Published09/14/2021 | SeverityUnknown |
CVE-2021-39122 | Exploitation statusNot known exploited | FixYes | Published09/08/2021 | SeverityMedium |
CVE-2021-39121 | Exploitation statusNot known exploited | FixYes | Published09/08/2021 | SeverityUnknown |
CVE-2021-39116 | Exploitation statusNot known exploited | FixYes | Published09/08/2021 | SeverityUnknown |
CVE-2021-39119 | Exploitation statusNot known exploited | FixYes | Published09/01/2021 | SeverityMedium |
CVE-2021-39117 | Exploitation statusNot known exploited | FixYes | Published08/30/2021 | SeverityUnknown |
CVE-2021-39113 | Exploitation statusNot known exploited | FixYes | Published08/30/2021 | SeverityHigh |
CVE-2021-39111 | Exploitation statusNot known exploited | FixYes | Published08/30/2021 | SeverityUnknown |
CVE-2021-39112 | Exploitation statusNot known exploited | FixYes | Published08/25/2021 | SeverityUnknown |
CVE-2021-26086 | Exploitation statusKEV | FixYes | Published08/16/2021 | SeverityMedium |
CVE-2017-18113 | Exploitation statusNot known exploited | FixYes | Published08/02/2021 | SeverityHigh |
CVE-2021-26083 | Exploitation statusNot known exploited | FixYes | Published07/20/2021 | SeverityUnknown |
CVE-2021-26082 | Exploitation statusNot known exploited | FixYes | Published07/20/2021 | SeverityUnknown |
CVE-2021-26081 | Exploitation statusNot known exploited | FixYes | Published07/20/2021 | SeverityMedium |
CVE-2021-26079 | Exploitation statusNot known exploited | FixYes | Published06/07/2021 | SeverityUnknown |
CVE-2021-26080 | Exploitation statusNot known exploited | FixYes | Published06/07/2021 | SeverityUnknown |
CVE-2021-26078 | Exploitation statusNot known exploited | FixYes | Published06/07/2021 | SeverityUnknown |
CVE-2020-36289 | Exploitation statusNot known exploited | FixYes | Published05/12/2021 | SeverityMedium |
CVE-2021-26076 | Exploitation statusNot known exploited | FixYes | Published04/14/2021 | SeverityUnknown |
CVE-2021-26075 | Exploitation statusNot known exploited | FixYes | Published04/14/2021 | SeverityUnknown |
CVE-2020-36288 | Exploitation statusNot known exploited | FixYes | Published04/14/2021 | SeverityUnknown |
CVE-2020-36287 | Exploitation statusNot confirmed | FixYes | Published04/09/2021 | SeverityUnknown |
CVE-2020-36286 | Exploitation statusNot confirmed | FixYes | Published04/01/2021 | SeverityUnknown |
CVE-2021-26071 | Exploitation statusNot confirmed | FixYes | Published04/01/2021 | SeverityUnknown |
CVE-2020-36238 | Exploitation statusNot confirmed | FixYes | Published04/01/2021 | SeverityUnknown |
CVE-2021-26069 | Exploitation statusNot confirmed | FixYes | Published03/22/2021 | SeverityUnknown |
CVE-2021-26070 | Exploitation statusNot confirmed | FixYes | Published03/22/2021 | SeverityUnknown |
CVE-2020-29453 | Exploitation statusNot confirmed | FixYes | Published02/18/2021 | SeverityUnknown |
CVE-2020-29451 | Exploitation statusNot confirmed | FixYes | Published02/15/2021 | SeverityUnknown |
CVE-2020-36234 | Exploitation statusNot confirmed | FixYes | Published02/15/2021 | SeverityUnknown |
CVE-2020-36237 | Exploitation statusNot confirmed | FixYes | Published02/14/2021 | SeverityUnknown |
CVE-2020-36236 | Exploitation statusNot confirmed | FixYes | Published02/14/2021 | SeverityUnknown |
CVE-2020-36235 | Exploitation statusNot confirmed | FixYes | Published02/14/2021 | SeverityUnknown |
CVE-2020-36231 | Exploitation statusNot confirmed | FixYes | Published02/01/2021 | SeverityUnknown |
CVE-2020-14185 | Exploitation statusNot confirmed | FixYes | Published10/15/2020 | SeverityUnknown |
CVE-2020-14184 | Exploitation statusNot confirmed | FixYes | Published10/12/2020 | SeverityUnknown |
CVE-2020-14183 | Exploitation statusNot confirmed | FixYes | Published10/06/2020 | SeverityUnknown |
CVE-2020-14177 | Exploitation statusNot confirmed | FixYes | Published09/21/2020 | SeverityUnknown |
CVE-2020-14179 | Exploitation statusNot confirmed | FixYes | Published09/21/2020 | SeverityUnknown |
CVE-2020-14181 | Exploitation statusNot confirmed | FixYes | Published09/17/2020 | SeverityUnknown |
CVE-2020-14178 | Exploitation statusNot confirmed | FixYes | Published09/01/2020 | SeverityUnknown |
CVE-2019-20901 | Exploitation statusNot confirmed | FixYes | Published07/13/2020 | SeverityUnknown |
CVE-2020-14174 | Exploitation statusNot confirmed | FixYes | Published07/13/2020 | SeverityUnknown |
CVE-2019-20900 | Exploitation statusNot confirmed | FixYes | Published07/13/2020 | SeverityUnknown |
CVE-2019-20899 | Exploitation statusNot confirmed | FixYes | Published07/13/2020 | SeverityUnknown |
CVE-2019-20898 | Exploitation statusNot confirmed | FixYes | Published07/13/2020 | SeverityUnknown |
CVE-2019-20897 | Exploitation statusNot confirmed | FixYes | Published07/13/2020 | SeverityUnknown |
CVE-2020-14173 | Exploitation statusNot confirmed | FixYes | Published07/03/2020 | SeverityUnknown |
CVE-2020-14172 | Exploitation statusNot confirmed | FixYes | Published07/03/2020 | SeverityUnknown |
CVE-2019-20419 | Exploitation statusNot confirmed | FixYes | Published07/03/2020 | SeverityUnknown |
CVE-2019-20418 | Exploitation statusNot confirmed | FixYes | Published07/03/2020 | SeverityUnknown |
CVE-2019-20408 | Exploitation statusNot confirmed | FixYes | Published07/01/2020 | SeverityUnknown |
CVE-2019-20416 | Exploitation statusNot confirmed | FixYes | Published06/30/2020 | SeverityUnknown |
CVE-2019-20415 | Exploitation statusNot confirmed | FixYes | Published06/30/2020 | SeverityUnknown |
CVE-2019-20414 | Exploitation statusNot confirmed | FixYes | Published06/29/2020 | SeverityUnknown |
CVE-2019-20413 | Exploitation statusNot confirmed | FixYes | Published06/29/2020 | SeverityUnknown |
CVE-2019-20412 | Exploitation statusNot confirmed | FixYes | Published06/29/2020 | SeverityUnknown |
CVE-2019-20411 | Exploitation statusNot confirmed | FixYes | Published06/29/2020 | SeverityUnknown |
CVE-2019-20410 | Exploitation statusNot confirmed | FixYes | Published06/29/2020 | SeverityUnknown |
CVE-2019-20409 | Exploitation statusNot confirmed | FixYes | Published06/23/2020 | SeverityUnknown |
CVE-2019-20100 | Exploitation statusNot confirmed | FixYes | Published02/12/2020 | SeverityUnknown |
CVE-2019-20099 | Exploitation statusNot confirmed | FixYes | Published02/12/2020 | SeverityUnknown |
CVE-2019-20098 | Exploitation statusNot confirmed | FixYes | Published02/12/2020 | SeverityUnknown |
CVE-2019-20405 | Exploitation statusNot confirmed | FixYes | Published02/06/2020 | SeverityUnknown |
CVE-2019-20404 | Exploitation statusNot confirmed | FixYes | Published02/06/2020 | SeverityUnknown |
CVE-2019-20403 | Exploitation statusNot confirmed | FixYes | Published02/06/2020 | SeverityUnknown |
CVE-2019-20402 | Exploitation statusNot confirmed | FixYes | Published02/06/2020 | SeverityUnknown |
CVE-2019-20401 | Exploitation statusNot confirmed | FixYes | Published02/06/2020 | SeverityUnknown |
CVE-2019-20400 | Exploitation statusNot confirmed | FixYes | Published02/06/2020 | SeverityUnknown |
CVE-2019-15005 | Exploitation statusNot confirmed | FixYes | Published11/08/2019 | SeverityUnknown |
CVE-2019-15001 | Exploitation statusNot confirmed | FixYes | Published09/19/2019 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan