Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

tempo vulnerabilities

Recent CVEs affecting tempo products. 1 tracked.

tempo has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-10-31. Highest priority: CVE-2019-5095 (score 37/100).

FAQ

How do I fix tempo vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is tempo being exploited right now?

None of the tracked tempo CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which tempo CVE should I patch first?

CVE-2019-5095 currently ranks highest (37/100): An issue summary information disclosure vulnerability exists in Atlassian Jira Tempo plugin, version 4.10.0.

Products

← Back to latest CVEs