security hardening: relabel perf/dos guard

F-PROMETHEUS-RELABEL-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

prometheus/prometheus #17969Security PRprometheus/prometheus

security hardening: relabel perf/dos guard

merged

details

Finding IDs: F-PROMETHEUS-RELABEL-001
Status: merged
Rationale: reduces resource-exhaustion surface in relabel processing.
PR opened by: @1seal
PR state observed: closed; GitHub merged: true; 2026-09-24
PR observation basis: Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed.
Contribution boundary: @1seal opened this PR; this alone does not establish sole code authorship.

F-PROMETHEUS-RELABEL-001: Resource limits. Repeated relabel processing permits excessive work. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-PROMETHEUS-RELABEL-001

Security area (1seal assessment): Availability. Computing relabel steps in one pass removes repeated processing of preceding rules and limits amplification of work. Reviewed 21 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.