CVE-2019-5095: An issue summary information disclosure vulnerability exists in Atlassian Jira Tempo plugin, version 4.10.0

Routine

MEDIUM 4.3DOWNGRADE

CVE-2019-5095 is a medium-severity flaw (CVSS 4.3) affecting tempo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue summary information disclosure vulnerability exists in Atlassian Jira Tempo plugin, version 4.10.0. Authenticated users can obtain the summary for issues they do not have permission to view via the Tempo plugin.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-862
Published	2019-10-31
Last modified	2026-06-17

Publisher (CNA): Talos · Vendor: tempo

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-10-31 20:15 UTCPublished CVE record published
2026-06-17 02:37 UTCUpdated Record last modified

tempo tempo DOWNGRADE

Affected: 4.10.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.10.0

1. Check installed version

apt-cache policy tempo || rpm -q tempo || tempo --version

2. No fixed release: DOWNGRADE to a release before 4.10.0 (Debian / Ubuntu)

apt-cache madison tempo sudo apt install tempo=<VERSION_BEFORE_4.10.0> sudo apt-mark hold tempo

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list tempo sudo dnf downgrade tempo-<VERSION_BEFORE_4.10.0> sudo dnf versionlock add tempo

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-5095?

tempo: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-5095 being exploited?

CVE-2019-5095 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-5095 affect?

CVE-2019-5095 affects tempo. Severity is medium (CVSS 4.3). An issue summary information disclosure vulnerability exists in Atlassian Jira Tempo plugin, version 4.10.0. Authenticated users can obtain the summary for issues they do not have permission to view via the Tempo plugin.

How urgent is CVE-2019-5095?

Priority 37/100. Public exploit reference

Software pages

Atlassian Jira vulnerabilities

Related CVEs

CVE-2026-21728 HIGH 7.5 UPGRADE Tempo queries with large limits can cause large memory allocations which can impact the availability of the se
CVE-2026-28377 HIGH 7.5 UPGRADE A vulnerability in Grafana Tempo exposes the S3 SSE-C encryption key in plaintext through the /status/config e

References

← Back to latest CVEs