Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 275/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 19:21 UTC Customize Public modeDiscuss ChangeIntel on Discord

Tempo query limit results in unbounded memory allocation

Collected exploitation and prediction evidence

Risk source coverage

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

cve-program · CVE-2026-21728

Published

Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18). Alternatively, automatically restart the service.

Source published
24 Apr 2026 08:00:47 UTC
Source modified
9 Sep 2026 12:04:42 UTC
Observed here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

euvd · EUVD-2026-25408

Published

Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18). Alternatively, automatically restart the service.

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Apr 24, 2026, 8:00:47 AM

dateUpdated: Sep 9, 2026, 12:04:42 PM

5 related source bulletins · separate from aliases

RHSA-2026:24503: Red Hat Security Advisory: Multicluster Global Hub 1.7.1 security update

CVE-2025-41118 · CVE-2026-21728 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-33813 · CVE-2026-33815 · CVE-2026-33816 · CVE-2026-34040 · CVE-2026-40293 · CVE-2026-40890 · CVE-2026-41602 · CVE-2026-43869

RHSA-2026:21769: Red Hat Security Advisory: Multicluster Global Hub 1.5.4 security update

CVE-2026-4427 · CVE-2026-21728 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-27889 · CVE-2026-29785 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-32283 · CVE-2026-32285 · CVE-2026-32286 · CVE-2026-33186 · CVE-2026-33215 · CVE-2026-33216 · CVE-2026-33217 · CVE-2026-33218 · CVE-2026-33219 · CVE-2026-33247 · CVE-2026-33413 · CVE-2026-33487 · CVE-2026-33810 · CVE-2026-33813 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-34986 · CVE-2026-40890 · CVE-2026-41602 · CVE-2026-41603 · CVE-2026-41604 · CVE-2026-41605 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-41636 · CVE-2026-43869

RHSA-2026:22423: Red Hat Security Advisory: Multicluster Global Hub 1.3.4 security update

CVE-2026-21728 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-32282 · CVE-2026-32283 · CVE-2026-32285 · CVE-2026-32286 · CVE-2026-33186 · CVE-2026-33487 · CVE-2026-33815 · CVE-2026-33816 · CVE-2026-34986 · CVE-2026-41602 · CVE-2026-41603 · CVE-2026-41604 · CVE-2026-41605 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-41636 · CVE-2026-43869

RHSA-2026:23345: Red Hat Security Advisory: Multicluster Global Hub 1.6.2 security update

CVE-2026-4427 · CVE-2026-21728 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-27889 · CVE-2026-29785 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-32283 · CVE-2026-32285 · CVE-2026-32286 · CVE-2026-33186 · CVE-2026-33215 · CVE-2026-33216 · CVE-2026-33217 · CVE-2026-33218 · CVE-2026-33219 · CVE-2026-33247 · CVE-2026-33413 · CVE-2026-33487 · CVE-2026-33810 · CVE-2026-33813 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-34986 · CVE-2026-40890 · CVE-2026-41602 · CVE-2026-41603 · CVE-2026-41604 · CVE-2026-41605 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-41636 · CVE-2026-43869

RHSA-2026:22347: Red Hat Security Advisory: Multicluster Global Hub 1.4.5 security update

CVE-2026-4427 · CVE-2026-21728 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-27889 · CVE-2026-29785 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-32283 · CVE-2026-32285 · CVE-2026-32286 · CVE-2026-33186 · CVE-2026-33215 · CVE-2026-33216 · CVE-2026-33217 · CVE-2026-33218 · CVE-2026-33219 · CVE-2026-33247 · CVE-2026-33413 · CVE-2026-33487 · CVE-2026-33810 · CVE-2026-33813 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-34986 · CVE-2026-40890 · CVE-2026-41602 · CVE-2026-41603 · CVE-2026-41604 · CVE-2026-41605 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-41636 · CVE-2026-43869

Source published
Apr 24, 2026, 8:00:47 AM (timezone not stated)
Source modified
Sep 9, 2026, 12:04:42 PM (timezone not stated)
Observed here
1 Nov 2026 03:06:31 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.

EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd · CVE-2026-21728

Published

Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18). Alternatively, automatically restart the service.

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-400 · CWE-770

Original publisher date fields

published: 2026-04-24T09:16:03.710

lastModified: 2026-10-26T21:10:00.170

1 source CPE criteria · context only
  • cpe:2.3:a:grafana:tempo:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
24 Apr 2026 09:16:03 UTC
Source modified
26 Oct 2026 21:10:00 UTC
Observed here
27 Oct 2026 06:23:31 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

osv · GHSA-p4r4-xvrq-gvmc

Published

Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18).

Source published
24 Apr 2026 09:30:30 UTC
Source modified
10 Sep 2026 03:50:44 UTC
Observed here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Publisher rating · HIGH

osv · GO-2026-5528

Published

Grafana Tempo has an Uncontrolled Resource Consumption issue in github.com/grafana/tempo. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/grafana/tempo before v2.8.4, from v2.9.0 before v2.9.2, from v2.10.0 before v2.10.2.

Source published
25 Jun 2026 22:34:34 UTC
Source modified
8 Jul 2026 15:29:23 UTC
Observed here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 1 Nov 19:21 UTC · 275 of 275 readable · 272 fully read · documentation 469/469 current