{"api_version":"1","generated_at":"2026-04-24T13:43:25+00:00","cve":"CVE-2026-21728","urls":{"html":"https://cve.report/CVE-2026-21728","api":"https://cve.report/api/cve/CVE-2026-21728.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-21728","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-21728"},"summary":{"title":"Tempo query limit results in unbounded memory allocation","description":"Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy.\n\nMitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18).","state":"PUBLISHED","assigner":"GRAFANA","published_at":"2026-04-24 09:16:03","updated_at":"2026-04-24 09:16:03"},"problem_types":[],"metrics":[{"version":"3.1","source":"security@grafana.com","type":"Secondary","score":"7.5","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.5","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","data":{"baseScore":7.5,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"references":[{"url":"https://grafana.com/security/security-advisories/cve-2026-21728","name":"https://grafana.com/security/security-advisories/cve-2026-21728","refsource":"security@grafana.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-21728","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-21728","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Grafana","product":"Tempo","version":"affected v1.3.0 v2.11.0 semver","platforms":["OnPrem"]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","platforms":["OnPrem"],"product":"Tempo","vendor":"Grafana","versions":[{"lessThan":"v2.11.0","status":"affected","version":"v1.3.0","versionType":"semver"}]}],"datePublic":"2026-02-23T07:40:45.862Z","descriptions":[{"lang":"en","value":"Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy.\n\nMitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18)."}],"metrics":[{"cvssV3_1":{"baseScore":7.5,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"providerMetadata":{"dateUpdated":"2026-04-24T08:00:47.074Z","orgId":"57da9224-a3e2-4646-9d0e-c4dc2e05e7da","shortName":"GRAFANA"},"references":[{"tags":["vendor-advisory"],"url":"https://grafana.com/security/security-advisories/cve-2026-21728"}],"source":{"discovery":"INTERNAL_FINDING"},"title":"Tempo query limit results in unbounded memory allocation","x_generator":{"engine":"cvelib 1.8.0"}}},"cveMetadata":{"assignerOrgId":"57da9224-a3e2-4646-9d0e-c4dc2e05e7da","assignerShortName":"GRAFANA","cveId":"CVE-2026-21728","datePublished":"2026-04-24T08:00:47.074Z","dateReserved":"2026-01-05T09:26:06.215Z","dateUpdated":"2026-04-24T08:00:47.074Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-04-24 09:16:03","lastModifiedDate":"2026-04-24 09:16:03","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"security@grafana.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":3.6}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"21728","Ordinal":"1","Title":"Tempo query limit results in unbounded memory allocation","CVE":"CVE-2026-21728","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"21728","Ordinal":"1","NoteData":"Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy.\n\nMitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18).","Type":"Description","Title":"Tempo query limit results in unbounded memory allocation"}]}}}