Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

suse-cvrf логотип

openSUSE-SU-2026:21136-1

Опубликовано: 18 июн. 2026
Источник: suse-cvrf

Описание

Security update for golang-github-prometheus-alertmanager

This update for golang-github-prometheus-alertmanager fixes the following issues:

Changes in golang-github-prometheus-alertmanager:

  • Update to version 0.28.1 (jsc#PED-13285):

    • Improved performance of inhibition rules when using Equal labels.
    • Improve the documentation on escaping in UTF-8 matchers.
    • Update alertmanager_config_hash metric help to document the hash is not cryptographically strong.
    • Fix panic in amtool when using --verbose.
    • Fix templating of channel field for Rocket.Chat.
    • Fix rocketchat_configs written as rocket_configs in docs.
    • Fix usage for --enable-feature flag.
    • Trim whitespace from OpsGenie API Key.
    • Fix Jira project template not rendered when searching for existing issues.
    • Fix subtle bug in JSON/YAML encoding of inhibition rules that would cause Equal labels to be omitted.
    • Fix header for slack_configs in docs.
    • Fix weight and wrap of Microsoft Teams notifications.

  • Upgrade to version 0.28.0:

    • CVE-2025-47908: Bump github.com/rs/cors (bsc#1247748).
    • Templating errors in the SNS integration now return an error.
    • Adopt log/slog, drop go-kit/log.
    • Add a new Microsoft Teams integration based on Flows.
    • Add a new Rocket.Chat integration.
    • Add a new Jira integration.
    • Add support for GOMEMLIMIT, enable it via the feature flag --enable-feature=auto-gomemlimit.
    • Add support for GOMAXPROCS, enable it via the feature flag --enable-feature=auto-gomaxprocs.
    • Add support for limits of silences including the maximum number of active and pending silences, and the maximum size per silence (in bytes). You can use the flags --silences.max-silences and --silences.max-silence-size-bytes to set them accordingly.
    • Muted alerts now show whether they are suppressed or not in both the /api/v2/alerts endpoint and the Alertmanager UI.

  • Upgrade to version 0.27.0:

    • API: Removal of all api/v1/ endpoints. These endpoints now log and return a deprecation message and respond with a status code of 410.
    • UTF-8 Support: Introduction of support for any UTF-8 character as part of label names and matchers.
    • Discord Integration: Enforce max length in message.
    • Metrics: Introduced the experimental feature flag --enable-feature=receiver-name-in-metrics to include the receiver name.
    • Metrics: Introduced a new gauge named alertmanager_inhibition_rules that counts the number of configured inhibition rules.
    • Metrics: Introduced a new counter named alertmanager_alerts_supressed_total that tracks muted alerts, it contains a reason label to indicate the source of the mute.
    • Discord Integration: Introduced support for webhook_url_file.
    • Microsoft Teams Integration: Introduced support for webhook_url_file.
    • Microsoft Teams Integration: Add support for summary.
    • Metrics: Notification metrics now support two new values for the label reason, contextCanceled and contextDeadlineExceeded.
    • Email Integration: Contents of auth_password_file are now trimmed of prefixed and suffixed whitespace.
    • amtool: Fixes the error scheme required for webhook url when using amtool with --alertmanager.url.
    • Mixin: Fix AlertmanagerFailedToSendAlerts, AlertmanagerClusterFailedToSendAlerts, and AlertmanagerClusterFailedToSendAlerts to make sure they ignore the reason label.

  • Security:

    • Fix proxy bypassing using IPv6 zone IDs (CVE-2025-22870, bsc#1238686)
    • Fix HTTP/2 CONTINUATION flood in net/http (CVE-2023-45288, bsc#1236516)
    • Add 0002-Bump-x-net.patch

Список пакетов

openSUSE Leap 16.0
golang-github-prometheus-alertmanager-0.28.1-bp160.1.1

Ссылки

Описание

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.

Затронутые продукты
openSUSE Leap 16.0:golang-github-prometheus-alertmanager-0.28.1-bp160.1.1
Ссылки

Описание

Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.

Затронутые продукты
openSUSE Leap 16.0:golang-github-prometheus-alertmanager-0.28.1-bp160.1.1
Ссылки

Описание

Middleware causes a prohibitive amount of heap allocations when processing malicious preflight requests that include a Access-Control-Request-Headers (ACRH) header whose value contains many commas. This behavior can be abused by attackers to produce undue load on the middleware/server as an attempt to cause a denial of service.

Затронутые продукты
openSUSE Leap 16.0:golang-github-prometheus-alertmanager-0.28.1-bp160.1.1
Ссылки
Уязвимость openSUSE-SU-2026:21136-1