jaeger-ingester:1.58.0-6.9

bash

bash-sh

ca-certificates-mozilla-prebuilt

coreutils

glibc

gpg-pubkey

jaeger-1-ingester

libcap2

libgcc_s1

libncurses6

libpcre1

libpcre2-8-0

libreadline7

libselinux1

libstdc++6

skelcd-EULA-bci

sles-release

terminfo-base

jaeger-ingester:1.76.0-26.7

Parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service.

CVE-2026-25680

Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.

CVE-2026-25681

CVE-2026-27136

When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.

CVE-2026-33814

The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error. This behavior can lead to privilege escalation in programs using the idna package. For example, a program which performs privilege checks on the ASCII hostname may reject "example.com" but permit "xn--example-.com". If that program subsequently converts the ASCII hostname to Unicode, it will inadvertently permits access to the Unicode name "example.com".

CVE-2026-39821

An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server process and affecting all connected users. Rejected channels are now properly removed from the connection's internal state and released for garbage collection.

CVE-2026-39827

When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError now results in a connection error.

CVE-2026-39828

The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by unauthenticated clients during public key authentication. RSA moduli are now limited to 8192 bits, and DSA parameters are validated per FIPS 186-2.

CVE-2026-39829

A malicious SSH peer could send unsolicited global request responses to fill an internal buffer, blocking the connection's read loop. The blocked goroutine could not be released by calling Close(), resulting in a resource leak per connection. Unsolicited global responses are now discarded.

CVE-2026-39830

The Verify() method for FIDO/U2F security key types (sk-ecdsa-sha2-nistp256@openssh.com, sk-ssh-ed25519@openssh.com) did not check the User Presence flag. Signatures generated without physical touch were accepted, allowing unattended use of a hardware security key. To restore the previous behavior, return a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback.

CVE-2026-39831

When adding a key to a remote agent constraint extensions such as restrict-destination-v00@openssh.com were not serialized in the request. Destination restrictions were silently stripped when forwarding keys, allowing unrestricted use of the key on the remote host. The client now serializes all constraint extensions. Additionally, the in-memory keyring returned by NewKeyring() now rejects keys with unsupported constraint extensions instead of silently ignoring them.

CVE-2026-39832

The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. The key would sign without any confirmation prompt, with no indication to the caller that the constraint was not in effect. NewKeyring() now returns an error when unsupported constraints are requested.

CVE-2026-39833

When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.

CVE-2026-39834

SSH servers which use CertChecker as a public key callback without setting IsUserAuthority or IsHostAuthority could be caused to panic by a client presenting a certificate. CertChecker now returns an error instead of panicking when these callbacks are nil.

CVE-2026-39835

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

CVE-2026-39882

OpenTelemetry-Go is the Go implementation of OpenTelemetry. From 1.15.0 to 1.42.0, the fix for CVE-2026-24051 changed the Darwin ioreg command to use an absolute path but left the BSD kenv command using a bare name, allowing the same PATH hijacking attack on BSD and Solaris platforms. This vulnerability is fixed in 1.43.0.

CVE-2026-39883

CVE-2026-42502

CVE-2026-42506

Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.

CVE-2026-42508

Previously, CVE-2024-45337 fixed an authorization bypass for misused ssh server configurations; if any other type of callback is passed other than public key, then the source-address validation would be skipped.

CVE-2026-46595

An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs.

CVE-2026-46597

For certain crafted inputs, a 'ed25519.PrivateKey' was created by casting malformed wire bytes, leading to a panic when used.

CVE-2026-46598

Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer.

CVE-2026-46600

The source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2026-46595. Permissions returned by the PasswordCallback, KeyboardInteractiveCallback, NoClientAuthCallback, and GSSAPIWithMICConfig.AllowLogin callbacks were not validated against the client's remote address, so a source-address restriction set by those callbacks was silently ignored. The check is now applied to the Permissions returned by any authentication callback.

CVE-2026-56854

Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other messages as a protocol error and tear the connection down instead of buffering and blocking.

CVE-2026-56855

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time, handlePacket drops every packet other than the open confirmation/failure, without blocking and without tearing down the connection.

CVE-2026-78662

gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, the xDS RBAC HTTP filter in internal/xds/httpfilter/rbac/rbac.go does not lowercase header matcher names in normalizeHeaderMatcher even though incoming metadata keys are lowercase. A DENY policy using a mixed-case name such as X-Role or User-Agent therefore does not match and fails open, allowing requests that should be rejected. The same case mismatch permits :Scheme or Grpc-Status to evade gRFC A41 validation and prevents Host from being rewritten to :authority. This issue is fixed in version 1.83.1.

CVE-2026-84303

The golang.org/x/crypto/openpgp package is unsafe by design, has numerous known security issues, is not maintained, and should not be used.

If you are required to interoperate with OpenPGP systems and need a maintained package, consider github.com/ProtonMail/go-crypto/openpgp which is a maintained fork that aims to be a drop-in replacement for this package.

	1.58.0-6.9	1.76.0-26.7
Details
Registered	2 years ago	15 days ago
Digest	180992b	8b5640d
Version	1.58.0	1.76.0
Revision	6.9	26.7
Base image	SLE BCI-micro 15.5.24.1	SLE BCI-micro 15.7-60.7
Operating System	SLE 15.5	SLE 15.7
Architecture	x86_64	x86_64
Size	25.1 MB	28.9 MB
System Packages
bash	4.4-150400.25.22	4.4-150400.27.6.1
bash-sh	4.4-150400.25.22	4.4-150400.27.6.1
ca-certificates-mozilla-prebuilt	2.62-150200.30.1	2.84-150200.44.1
coreutils	8.32-150400.9.6.1	8.32-150400.9.12.1
glibc	2.31-150300.83.1	2.38-150600.14.52.1
gpg-pubkey	-	3fa1d6ce-67c856ee
jaeger-1-ingester	1.58.0-150500.1.1	1.76.0-150700.3.6
libcap2	2.63-150400.3.3.1	2.63-150400.3.6.1
libgcc_s1	13.2.1+git8285-150000.1.9.1	15.3.0+git11272-150000.1.12.1
libncurses6	6.1-150000.5.24.1	6.1-150000.5.33.1
libpcre1	8.45-150000.20.13.1	Removed
libpcre2-8-0	-	10.42-150600.1.26
libreadline7	7.0-150400.25.22	7.0-150400.27.6.1
libselinux1	3.1-150400.1.69	3.5-150600.3.3.1
libstdc++6	13.2.1+git8285-150000.1.9.1	15.3.0+git11272-150000.1.12.1
skelcd-EULA-bci	2023.03.06-150500.2.1	20250430-150700.1.1
sles-release	15.5-150500.43.4	15.7-150700.67.6.1
terminfo-base	6.1-150000.5.24.1	6.1-150000.5.33.1
Vulnerabilities
CVE-2026-33186	Not present	Found
CVE-2026-24051	Not present	Found
CVE-2026-25681	Not present	Found Not affected
CVE-2026-27136	Not present	Found Not affected
CVE-2026-29181	Not present	Found
CVE-2026-33814	Not present	Found Not affected
CVE-2026-39821	Not present	Found Not affected
CVE-2026-39828	Not present	Found Not affected
CVE-2026-39829	Not present	Found Not affected
CVE-2026-39830	Not present	Found Not affected
CVE-2026-39831	Not present	Found Not affected
CVE-2026-39832	Not present	Found Not affected
CVE-2026-39835	Not present	Found Not affected
CVE-2026-39883	Not present	Found Not affected
CVE-2026-41602	Not present	Found
CVE-2026-42508	Not present	Found Not affected
CVE-2026-43871	Not present	Found
CVE-2026-46595	Not present	Found Not affected
CVE-2026-46597	Not present	Found Not affected
CVE-2026-46600	Not present	Found Not affected
CVE-2026-56852	Not present	Found
CVE-2026-56854	Not present	Found Not affected
CVE-2026-84304	Not present	Found
CVE-2026-84445	Not present	Found
GHSA-hrxh-6v49-42gf	Not present	Found
CVE-2026-25680	Not present	Found Not affected
CVE-2026-39827	Not present	Found Not affected
CVE-2026-39833	Not present	Found Not affected
CVE-2026-39834	Not present	Found Not affected
CVE-2026-39882	Not present	Found Not affected
CVE-2026-42502	Not present	Found Not affected
CVE-2026-42506	Not present	Found Not affected
CVE-2026-46598	Not present	Found Not affected
CVE-2026-56855	Not present	Found Not affected
CVE-2026-78662	Not present	Found Not affected
CVE-2026-84303	Not present	Found Not affected
CVE-2026-39824	Not present	Found
GO-2026-5932	Not present	Found Not affected
OCI Annotations
org.opencontainers.image.base.digest	sha256:934320b0d4c297307483eedcb05654ffba491973d518d08e8fc4c7399febcc91	sha256:4cdcad941236068fdf4cac1f3008600d478ebbf78236677452a662ae1f3fe792
org.opencontainers.image.base.name	registry.suse.com/bci/bci-micro:15.5.24.1	registry.suse.com/bci/bci-micro:15.7-60.7

jaeger-ingester

These are the differences found between the artifacts selected