VYPR

apk package

chainguard/request-9047-keycloak-fips-26.4-iamguarded-fips

pkg:apk/chainguard/request-9047-keycloak-fips-26.4-iamguarded-fips

Vulnerabilities (37)

  • CVE-2026-54515MedJun 23, 2026
    affected < 26.4.7-r20fixed 26.4.7-r20

    jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.8.0 until 2.18.9, 2.21.5, and 3.1.4, in BeanDeserializerBase.createContextual(), per-property @JsonIgnoreProperties exclusions are applied by _handleByNameIn

  • CVE-2026-54514MedJun 23, 2026
    affected < 26.4.7-r19fixed 26.4.7-r19

    jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.0.0 until 2.18.8, 2.21.4, and 3.1.4, JDKFromStringDeserializer constructed InetSocketAddress with new InetSocketAddress(host, port), which performs eager DNS

  • CVE-2026-54513HigJun 23, 2026
    affected < 26.4.7-r19fixed 26.4.7-r19

    jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and 3.1.4, BasicPolymorphicTypeValidator.Builder.allowIfSubTypeIsArray() allowlists any array type based only on clazz.isArray(),

  • CVE-2026-54512HigJun 23, 2026
    affected < 26.4.7-r19fixed 26.4.7-r19

    jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and 3.1.4, jackson-databind's PolymorphicTypeValidator (PTV) is the primary safety mechanism guarding polymorphic deserialization.

  • CVE-2026-50559HigJun 19, 2026
    affected < 26.4.7-r30fixed 26.4.7-r30

    Quarkus is a Java framework for building cloud-native applications. Prior to versions 3.37.0, 3.36.3, 3.33.2.1, 3.33.3, 3.27.4.1, 3.27.5, and 3.20.6.2, Quarkus HTTP path-based authorization policies can be bypassed using encoded semicolons (%3B) to smuggle matrix parameters past

  • CVE-2026-50010HigJun 12, 2026
    affected < 26.4.7-r18fixed 26.4.7-r18

    Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, SimpleTrustManagerFactory.engineGetTrustManagers() and related paths wrap any user-supplied plain X509TrustManager in X509TrustManagerWrappe

  • CVE-2026-48059HigJun 12, 2026
    affected < 26.4.7-r17fixed 26.4.7-r17

    Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, the HAProxy PROXY protocol v2 codec in netty leaks native or heap memory on every connection when a client sends a syntactically valid heade

  • CVE-2026-48043MedJun 12, 2026
    affected < 26.4.7-r17fixed 26.4.7-r17

    Netty is a network application framework for development of protocol servers and clients. In netty-codec-http2 prior to versions 4.1.135.Final and 4.2.15.Final, the `DelegatingDecompressorFrameListener` class orchestrates HTTP/2 decompression by embedding a per-stream `EmbeddedCh

  • CVE-2026-47691HigJun 12, 2026
    affected < 26.4.7-r17fixed 26.4.7-r17

    Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty's `DnsResolveContext` insufficiently validates the bailiwick of NS records, enabling DNS Cache Poisoning. An attacker controlling an a

  • CVE-2026-47244MedJun 12, 2026
    affected < 26.4.7-r17fixed 26.4.7-r17

    Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, DefaultHttp2Connection.DefaultEndpoint initialises maxActiveStreams/maxStreams to Integer.MAX_VALUE, and Http2Settings never inserts SETTING

  • CVE-2026-45674HigJun 12, 2026
    affected < 26.4.7-r17fixed 26.4.7-r17

    Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty's DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses. Versions 4.1.135.Final and 4.2.15.Fina

  • CVE-2026-45673MedJun 12, 2026
    affected < 26.4.7-r17fixed 26.4.7-r17

    Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty's DNS resolver uses a predictable PRNG for generating DNS transaction IDs and defaults to a static UDP source port. This combination r

  • CVE-2026-45536MedJun 12, 2026
    affected < 26.4.7-r18fixed 26.4.7-r18

    Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, netty_unix_socket_recvFd sets msg_control to `char control[CMSG_SPACE(sizeof(int))]` (line 940) — 24 bytes on 64-bit Linux. A peer-sent SCM_

  • CVE-2026-45416HigJun 12, 2026
    affected < 26.4.7-r18fixed 26.4.7-r18

    Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, SslClientHelloHandler.decode() reads the 24-bit TLS handshake length and, when the ClientHello does not fit in the first record, eagerly all

  • CVE-2026-44893HigJun 12, 2026
    affected < 26.4.7-r17fixed 26.4.7-r17

    Netty is a network application framework for development of protocol servers and clients. In netty-codec-haproxy prior to versions 4.1.135.Final and 4.2.15.Final, when decoding a PP2_TYPE_SSL TLV, HAProxyMessage.readNextTLV() first calls `header.retainedSlice(header.readerIndex()

  • CVE-2026-44249HigJun 11, 2026
    affected < 26.4.7-r18fixed 26.4.7-r18

    Netty is a network application framework for development of protocol servers and clients. In netty-handler prior to versions 4.1.135.Final and 4.2.15.Final, an attacker can bypass IPv6 subnet rules due to an incorrect masking operation in IpSubnetFilterRule.compareTo(). Valid pub

  • CVE-2026-6860MedMay 6, 2026
    affected < 26.4.7-r28fixed 26.4.7-r28

    A TCP client can perform a TLS handshake and present the server name extension with a server name that is accepted by a server wildcard name, e.g. if the server is configured with a certificate accepting *.example.com, any XYZ.example.com where xyz is a valid name can be used.

Page 2 of 2