Security update for alloy
This update for alloy fixes the following issues: - CVE-2026-1229: github.com/cloudflare/circl: the CombinedMult function in the ecc/p384 package produces an incorrect value for specific inputs (bsc#1265542). - CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265845). - CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266654). - CVE-2026-41506: github.com/go-git/go-git/v5: HTTP authentication credential leak when following redirects during smart-HTTP clone and fetch operations (bsc#1264949). - CVE-2026-41606: github.com/apache/thrift: crafted nested messages in c_glib dispatch can lead to uncontrolled recursion and denial of service (bsc#1263324). - CVE-2026-41607: github.com/apache/thrift: crafted message with improper length validation can lead to an out-of-bounds read and potential information disclosure (bsc#1263289). Changes for alloy: - Update to version 1.18.0: * BREAKING: otelcol HTTP receivers default to idle_timeout="1m", read_header_timeout="1m", write_timeout="30s" to match upstream. Affects otlp, faro, jaeger, zipkin, influxdb, splunkhec, datadog and jaeger_remote_sampling. * Back off usage reporting on persistent failure * Fix Beyla glob parsing * Bump github.com/prometheus/procfs for XFS Collector fix * database_observability.mysql: Simplify denylist in-memory map * database_observability.po
SUSE-SU-2026:23853-1
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: osv:SUSE-SU-2026:23853-1
alloy
Source reference: /affected/0/package/name
- Affected versions
- Not stated in this record
- Fixed versions
- 1.18.0-160000.1.1
Source reference:
/affected/0/ranges - Prerequisites
- Not stated in this record
alloy
Source reference: /affected/1/package/name
- Affected versions
- Not stated in this record
- Fixed versions
- 1.18.0-160000.1.1
Source reference:
/affected/1/ranges - Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.18.0-160000.1.1"
}
]
}
],
"package": {
"name": "alloy",
"purl": "pkg:rpm/suse/alloy&distro=SUSE%20Linux%20Enterprise%20Server%2016.0",
"ecosystem": "SUSE:Linux Enterprise Server 16.0"
},
"database_specific": {
"source": "https://ftp.suse.com/pub/projects/security/osv/SUSE-SU-2026:23853-1.json"
},
"ecosystem_specific": {
"binaries": [
{
"alloy": "1.18.0-160000.1.1"
}
]
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.18.0-160000.1.1"
}
]
}
],
"package": {
"name": "alloy",
"purl": "pkg:rpm/suse/alloy&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20applications%2016.0",
"ecosystem": "SUSE:Linux Enterprise Server for SAP applications 16.0"
},
"database_specific": {
"source": "https://ftp.suse.com/pub/projects/security/osv/SUSE-SU-2026:23853-1.json"
},
"ecosystem_specific": {
"binaries": [
{
"alloy": "1.18.0-160000.1.1"
}
]
}
}
]Publisher severity
No explicit severity was provided.
- Event
- #20001 · Revision 1
- Added to Heist Feed
- Publisher date