Linux · SUSE Linux Enterprise · Security advisory · October 6, 2026
SUSE-SU-2026:24148-1: alloy security update
SUSE-SU-2026:24148-1, released October 6, 2026, fixes 19 CVEs in alloy (version 1.19.2-160000.1.1). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
19
None rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0055
46th percentile
Priority of the 19 CVEs
Patch now 0
Urgent 0
High 9
Routine 10
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| alloy | sles 16.0 | 1.19.2-160000.1.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-46600 | Parsing an invalid SVCB or HTTPS RR can panic in golang.org/x/net/dns/dnsmessage | 7.5 | 0.0055 | None reported |
| High | CVE-2026-56855 | Prevent DoS on deadlocked established channel in golang.org/x/crypto/ssh | 7.5 | 0.0050 | None reported |
| High | CVE-2026-56852 | Infinite loop on invalid input in golang.org/x/text | 8.8 | 0.0048 | None reported |
| High | CVE-2026-56854 | amazon-ssm-agent: golang.org/x/crypto/ssh: source-address restriction bypassed in 5 callback families (bsc#1278681) | 7.5 | 0.0044 | None reported |
| High | CVE-2026-37236 | grpc-gateway v2.28.0 is vulnerable to Incorrect Access Control. The application processes the X-HTTP-Method-Override header in ServeMux.ServeHTTP without restricting allowed methods. When a POST request with Content-Type application/x-www-form-urlencoded includes this header, the request method is rewritten to an arbitrary attacker-supplied value before routing. This allows bypassing method-based access controls enforced by upstream proxies or WAFs. | 9.8 | 0.0043 | None reported |
| High | CVE-2026-78662 | Prevent DoS on deadlocked undecided channel in golang.org/x/crypto/ssh | 7.5 | 0.0043 | None reported |
| High | CVE-2026-71556 | go-git: Worktree operations may follow symlinks | 7.1 | 0.0036 | None reported |
| High | CVE-2026-41178 | alloy: go.opentelemetry.io/otel/baggage: no rejection of raw-length headers in baggage parsing allows for DoS | 8.2 | 0.0034 | None reported |
| High | CVE-2026-81521 | flightctl: The MongoDB Go Driver's client-level bulk write operation may accept a caller-supplied database name containing a res... | 7.5 | 0.0024 | None reported |
| Routine | CVE-2026-71557 | go-git: Malicious reference names may modify files outside the reference storage | 6.3 | 0.0041 | None reported |
| Routine | CVE-2026-45680 | alloy: go.opentelemetry.io/obi: unbounded BPF internal metrics replay can exhaust CPU and cause a DoS | n/a | 0.0032 | None reported |
| Routine | CVE-2026-2303 | alloy: go.mongodb.org/mongo-driver: mongo-go-driver has Heap Out-of-Bounds Read in GSSAPI Error Handling | n/a | 0.0031 | None reported |
| Routine | CVE-2026-89090 | alloy: github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream: malformed EventStream response frames | n/a | 0.0031 | None reported |
| Routine | CVE-2026-45681 | alloy: go.opentelemetry.io/obi: CPU-mismatch fallback uses 256-byte buffer with 8KB size and can cause OBI | n/a | 0.0029 | None reported |
| Routine | CVE-2026-75889 | alloy: arbitrary file reads due to the `prometheus.operator.servicemonitors` component allowing users who can | n/a | 0.0022 | None reported |
| Routine | CVE-2026-45679 | alloy: go.opentelemetry.io/obi: Redis error text is exported in span status messages and can lead to | n/a | 0.0021 | None reported |
| Routine | CVE-2026-45683 | alloy: go.opentelemetry.io/obi: Java TLS ioctl kprobe allows a user to point OBI at kernel memory and cause | n/a | 0.0017 | None reported |
| Routine | CVE-2026-45684 | alloy: go.opentelemetry.io/obi: log enricher mishandled `writev` buffers and allows multi-segment calls to | n/a | 0.0017 | None reported |
| Routine | CVE-2026-48496 | alloy: opentelemetry-ebpf-profiler: Unprivileged process can trigger a denial of service on the ebpf-profiler | n/a | 0.0014 | None reported |
Showing 1 to 19 of 19
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.