prometheus
prometheus
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Prometheus. Use that record for publisher support phases and retirement dates.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-44903 | 26 May 2026 | >= 2.49.0, < 3.5.3; >= 3.6.0-rc.0, < 3.11.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-42154 | 4 May 2026 | prometheus: < 3.5.3, >= 3.6.0, < 3.11.3 | RHSA-2026:41019: RHEM 1.1 for RHEL 10, RHEM 1.1 for RHEL 9 | Update reference ↗ |
| CVE-2026-42151 | 4 May 2026 | prometheus: < 3.5.3, >= 3.6.0, < 3.11.3 | RHSA-2026:41019: RHEM 1.1 for RHEL 10, RHEM 1.1 for RHEL 9 | Update reference ↗ |
| CVE-2026-40179 | 15 Apr 2026 | >= 3.0.0, < 3.5.2; >= 3.6.0, < 3.11.2; < 0.311.2-0.20260410083055-07c6232d159b | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-29622 | 19 May 2021 | >= 2.23.0, < 2.27.1 | For OpenShift Container Platform 4.8 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.8/updating/updating-cluster-cli.html | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.