Описание
Security update for alloy
This update for alloy fixes the following issues
Security issues:
- CVE-2026-4427: github.com/jackc/pgproto3/v2: improper validation of field length allows a malicious PostgreSQL server to crash a client application via a DataRow message (bsc#1259919).
- CVE-2026-25934: github.com/go-git/go-git/v5: improper verification of data integrity values for .pack and .idx files can lead to the consumption of corrupted files (bsc#1258099).
- CVE-2026-26958: filippo.io/edwards25519: failure to initialize receiver in MultiScalarMult can produce invalid results and lead to undefined behavior (bsc#1258609).
- CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2: path pseudo- header (bsc#1260317).
- CVE-2026-34986: github.com/go-jose/go-jose/v4: crafted JWE input with a missing encrypted key can lead to a denial of service (bsc#1262955).
- CVE-2026-41602: github.com/apache/thrift: TFramedTransport frame size headers can lead to a uint32 integer overflow (bsc#1263530).
Non security issue:
- Use systemd tmpfiles.d to create /var/lib/alloy hierarchy (jsc#PED-14815).
- Update to version 1.16.1
- Bug Fixes logging: Fix startup deadlock when components log before logging config is evaluated Update to Beyla 3.9.8 Migrate from Docker to Moby
- Use latest openSUSE Tumbleweed image for building web UI assets
- Install nvm to set node version specified upstream
- update to 1.16.0:
- Features
- Add clustering for loki.source.kubernetes_events (#6027) (3dbf587) (@petewall)
- Add otelcol.auth.google client auth provider (#5526) (da99a66) (@dashpole, @clayton-cornell)
- beyla.ebpf: Bump to v3.7.0 (#5966) (5126c2e) (@marctc)
- database_observability: Add support for GCP Cloud SQL metadata (#5875) (5d23245) (@cristiangreco, @clayton-cornell)
- database_observability: Make targets optional (#5924) (54664b2) (@matthewnolf)
- database_observability: Update default excluded schemas and users (#6080) (b386fff) (@cristiangreco)
- faro.receiver: Add sourcemap fetching from remote locations (#4614) (b6cb5da) (@Oxel40)
- helm: Add support for global.image.pullPolicy (#6069) (2e2ce72) (@petewall)
- helm: Allow configuring image pull policy for config reloader (#5923) (991539b) (@kalleep)
- loki.secretfilter: Add label_timed_out option to mark timed-out log lines (#5898) (2ad8834) (@kleimkuhler)
- loki.secretfilter: Add secrets_redacted_by_category_total metric combining rule and origin (#5855) (053a2f7) (@kleimkuhler)
- loki.secretfilter: Change secretfilter to use go-re2 regex library instead of stdlib (#5909) (c16a660) (@mikefat)
- loki.secretfilter: Remove redundant secrets_redacted_by_rule_total and secrets_redacted_by_origin metrics (#5970) (b16decb) (@kleimkuhler)
- Oracle exporter can scrape more than one DB (#6008) (6fbad38) (@ptodev)
- prometheus.exporter.cloudwatch: Upgrade YACE and drop aws-sdk-go v1 support (#5936) (f1c036d) (@x1unix)
- prometheus.exporter.mysql: Update to mysqld_exporter 0.19.0 (#5836) (4f49b57) (@cristiangreco)
- prometheus.remote_write: Sync WAL with upstream Prometheus (#5907) (e74a91b) (@x1unix)
- pyroscope: Add support for extra async-profiler CLI arguments (#5472) (9251e33) (@ivanape)
- pyroscope: Replace Parca gRPC debuginfo upload with Pyroscope Connect API (#5891) (e7ea34a) (@korniltsev-grafanista)
- pyroscope: Update debuginfo client for HTTP/1.1 upload API (#6037) (879d8e5) (@korniltsev-grafanista)
- Change service stop command from 'sc' to 'net' (#5906) (450973d) (@mateuszdrab)
- database_observability.mysql: Refactor explain plan loop batch size (#5894) (f0fcd6b) (@cristiangreco)
- database_observability.postgres: Cleanup embedded exporter collectors on reconnection (#6079) (f30d9ae) (@cristiangreco)
- database_observability.postgres: Fix EXPLAIN param count when placeholders repeat (#6082) (b612b81) (@rgeyer)
- database_observability: Drop schema_detection from logs (#6076) (b0105cb) (@cristiangreco)
- database_observability: Ensure connection_info_monitor goroutine exits on Stop (#5874) (1e3334b) (@cristiangreco)
- deps: Update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.97.3 [SECURITY] (#6004) (38f4346)
- deps: Update module github.com/go-git/go-git/v5 to v5.17.1 [SECURITY] (#5934) (a5154af)
- deps: Update module github.com/go-git/go-git/v5 to v5.18.0 [SECURITY] (#6090) (0e59d64)
- deps: Update module github.com/nwaples/rardecode/v2 to v2.2.0 [SECURITY] (b44d51a) (@jharvey10)
- deps: Update module go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp to v1.43.0 [SECURITY] (#6016) (d92c5c0) go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp to v1.43.0 [SECURITY] (#6017) (e655bbc)
- deps: Update module go.opentelemetry.io/otel/sdk to v1.43.0 [SECURITY] (#6018) (94006e8)
- deps: Update some minor go dep versions (#5896) (4ddd0ed) (@jharvey10)
- go: Update alloy builder image to Go 1.25.9 (#6012) (d2ae8b8) (@x1unix)
- go: Upgrade to Go 1.25.9 (#6019) (d777ed1) (@x1unix, @kalleep)
- Helm: RBAC template handles empty rule arrays (#4860) (c9430e9) (@naptalie, @dehaansa, @kalleep)
- loki.process: Eliminate per-stream goroutines in multiline stage (#6036) (c089e2e) (@kgeckhart)
- loki.process: Prevent stage.structured_metadata from adding the same metadata several times (#5965) (0ec8a26) (@kalleep, @thampiotr)
- loki.process: Wrap template in a custom type and move validation to syntax.Validator (#5910) (700dd7d) (@kalleep)
- prometheus.exporter.postgres: Close DB connections on update (#6021) (8da97cf) (@kalleep)
- prometheus.scrape: Update scrape_native_histograms to be updated at runtime (#6087) (18b205c) (@kalleep)
- pyroscope.ebpf: Fix deadlock on LRU eviction in irsymcache (#5911) (03ca563) (@luweglarz)
- pyroscope.ebpf: Move Pyroscope ebpf metrics registration after component error handling (#5540) (a3c57c0) (@crbednarz, @marcsanmi)
- pyroscope: Set user agent on debuginfo connect-go client (#6022) (38ad1ef) (@korniltsev-grafanista)
- ui: Large arguments are downloaded as files instead of rendered (#5268) (26c67b3) (@ptodev)
- Update go-m1cpu v0.1.7 -> v0.2.1 to fix M5 chip crash (#6034) (7fa0cbc) (@ymotongpoo)
- windows-installer: Increase service restart on failure delays (#5969) (add15b1) (@rknightion)
- add script to package webassets inside a podman container, to not endanger or pollute the host system with npm
- update to 1.15.1: goroutine exits on Stop
- CVE-2026-34986: Fix panic in JWE decryption (bsc#1262955)
- update to 1.15.0:
- BREAKING CHANGES
- otelcol: Upgrade to OTel Collector v0.147.0
- Renamed undocumented metrics that was previously prefixed with <component_id><metric_name> to loki_source_awsfirehose<metric_name>
- Security CVE-2026-26958: Update filippo.io/edwards25519 to version 1.1.1 (bsc#1258609).
- alloy-mixin: Add filters, groupBy, and multi-select dashboard variables
- beyla.ebpf: Add support for Prometheus native histograms
- beyla.ebpf: Bump Beyla to v3.6
- converters: Support converting Promtail limits_config
- database_observability.mysql: Add filtering of query samples and wait events by minimum duration
- database_observability.mysql: Embed prometheus exporter within db-o11y component
- database_observability.postgres: Add configurable limit to pg_stat_statements query
- database_observability.postgres: Embed prometheus exporter
- database_observability: Promote components to stable
- Expose Functionality to Handle syslogs with Empty MSG Field
- loki.process: Support structured metadata as source type of stage.labels for loki.process
- loki.secretfilter: Add sampling for secretfilter entries
- loki.source.gcplog: Add alloy config for MaxOutstandingBytes and MaxOutstandingMessages
- loki.write: Add loki pipeline latency metric
- mixin: Update loki dashboard
- otelcol.receiver.datadog: Expose intake proxy and trace_id_cache_size settings
- prometheus.exporter.cloudwatch: Use aws-sdk-go-v2 by default
- pyroscope.ebpf: Add comm, pid labels and kernel frame options
- update to 1.14.1:
- Correctly handle the deprecated topic field in otelcol.receiver.kafka configuration
- loki.process: Protect against json that does not look like docker json format
- loki.source.file: Keep positions for compressed files when reading is finished
- prometheus.scrape: Update arguments and targets even if scrape_native_histograms and extra_metrics are updated
- update to 1.14.0:
- loki.secretfilter: Some config options are removed entirely: partial_mask (replaced with redact_percent), allowlist (now controlled with custom gitleaks config), enable_entropy, include_generic, types (now controlled with custom gitleaks config).
- otelcol.receiver.prometheus: otelcol.receiver.prometheus no longer sets start times of OTLP metrics.
- Security:
- update to 1.13.2:
- Expose missing otelcol.processor.tail_sampling options
- mixin: Add zipped dashboards as a release artifact
- profiler: Backport Go 1.26 gopclntab textStart fix
- prometheus.exporter.postgres: Update version of the exporter fork to fix pg_settings
- pyroscope.ebpf: Backport dotnet nibble map fix
- update to 1.13.1:
- timeout before starting new ones
- update to 1.13.0:
- otelcol: Upgrade to OTel Collector v0.142.0
- otelcol.receiver.kafka: The global topic attribute has been deleted; use the topics attributes inside the logs, metrics, and traces blocks instead.
- otelcol.exporter > sending_queue > batch > min_size changed from 8192 to 2000 and max_size changed from 0 to 3000
- Add a virtual_node_peer_attributes and virtual_node_extra_label arguments to otelcol.connector.servicegraph
- Add an otelcol.processor.metric_start_time component
- Add job level period, length, and add_cloudwatch_timestamp options and labels_snake_case to CW exporter
- Add missing configuration parameter deployment_name_from_replicaset to k8sattributes processor
- Add parcas symbols upload to pyroscope.ebpf
- Add sharding for loki.write
- Add unexposed otel engine and extension to codebase and change build structure
- beyla.ebpf: Add meta_cache_address to beyla.ebpf.attributes.kubernetes
- beyla.ebpf: Upgrade Beyla to v2.8.5
- Change the defaults for sending_queue > batch block inside otelcol.exporter components
- cluster: Support DNS discovery mode prefixes in --cluster.join-addresses flag
- converter: Update promtail converter to use file_match block for loki.source.file
- database_observability: Add health check collector for postgres component
- database_observability: Expose exclude_schemas and exclude_databases settings
- database_observability: Support Azure cloud provider config data
- database_observability.mysql: Support excluding schemas in all collectors
- database_observability.postgres: Support excluding DBs in all collectors
Список пакетов
SUSE Linux Enterprise Module for Basesystem 15 SP7
Ссылки
- Link for SUSE-SU-2026:2438-1
- E-Mail link for SUSE-SU-2026:2438-1
- SUSE Security Ratings
- SUSE Bug 1258099
- SUSE Bug 1258609
- SUSE Bug 1259919
- SUSE Bug 1260317
- SUSE Bug 1262955
- SUSE Bug 1263530
- SUSE CVE CVE-2026-25934 page
- SUSE CVE CVE-2026-26958 page
- SUSE CVE CVE-2026-33186 page
- SUSE CVE CVE-2026-34986 page
- SUSE CVE CVE-2026-41602 page
- SUSE CVE CVE-2026-4427 page
Описание
go-git is a highly extensible git implementation library written in pure Go. Prior to 5.16.5, a vulnerability was discovered in go-git whereby data integrity values for .pack and .idx files were not properly verified. This resulted in go-git potentially consuming corrupted files, which would likely result in unexpected errors such as object not found. For context, clients fetch packfiles from upstream Git servers. Those files contain a checksum of their contents, so that clients can perform integrity checks before consuming it. The pack indexes (.idx) are generated locally by go-git, or the git cli, when new .pack files are received and processed. The integrity checks for both files were not being verified correctly. This vulnerability is fixed in 5.16.5.
Затронутые продукты
Ссылки
- CVE-2026-25934
- SUSE Bug 1258093
Описание
filippo.io/edwards25519 is a Go library implementing the edwards25519 elliptic curve with APIs for building cryptographic primitives. In versions 1.1.0 and earlier, MultiScalarMult produces invalid results or undefined behavior if the receiver is not the identity point. If (*Point).MultiScalarMult is called on an initialized point that is not the identity point, it returns an incorrect result. If the method is called on an uninitialized point, the behavior is undefined. In particular, if the receiver is the zero value, MultiScalarMult returns an invalid point that compares Equal to every other point. Note that MultiScalarMult is a rarely used, advanced API. For example, users who depend on filippo.io/edwards25519 only through github.com/go-sql-driver/mysql are not affected. This issue has been fixed in version 1.1.1.
Затронутые продукты
Ссылки
- CVE-2026-26958
- SUSE Bug 1258570
Описание
gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.
Затронутые продукты
Ссылки
- CVE-2026-33186
- SUSE Bug 1260085
Описание
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW, with the exception of A128GCMKW, A192GCMKW, and A256GCMKW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() in key_wrap.go attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key. This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping algorithms, parsing will fail and the application will be unaffected. This panic is also reachable by calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling this function directly is less common. Panics can lead to denial of service. This vulnerability is fixed in 4.1.4 and 3.0.5.
Затронутые продукты
Ссылки
- CVE-2026-34986
- SUSE Bug 1262805
Описание
Integer Overflow or Wraparound vulnerability in Apache Thrift TFramedTransport Go language implementation This issue affects Apache Thrift: before 0.23.0. Users are recommended to upgrade to version 0.23.0, which fixes the issue.
Затронутые продукты
Ссылки
- CVE-2026-41602
- SUSE Bug 1263496
Описание
Duplicate of CVE-2026-32286
Затронутые продукты
Ссылки
- CVE-2026-4427
- SUSE Bug 1259910