container statistics
11 container package(s) · generated 2026-11-22T04:45:29Z
ghcr.io/openvoxproject/openbolt
ghcr.io/openvoxproject/openbolt:latest (2026-08-27)
Trivy
HIGH 8
MEDIUM 12
LOW 2
UNKNOWN 6
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-85396 | rubyzip | 2.4.1 | >= 3.4.0 | rubyzip: rubyzip: Arbitrary file write via path traversal — Ruby |
| HIGH | CVE-2026-80212 | resolv | 0.2.3 | ~> 0.3.2, >= 0.7.2 | resolv: resolv gem: Denial of Service via uncontrolled memory growth from crafted DNS responses — Ruby |
| HIGH | GHSA-vxj5-fg65-x765 | net-ssh | 7.3.3 | ~> 7.3, >= 7.3.4, >= 8.0.0.beta3 | net-ssh - SSH host-certificate authentication bypass — @cert-authority verifier skips valid_principals / validity window / cert type / critical options, so any CA-signed cert impersonates any host trusting that CA (CWE-295) — Ruby |
| HIGH | GHSA-qpg5-fx6p-8cq3 | net-ssh | 7.3.3 | ~> 7.3, >= 7.3.5, >= 8.0.0.rc2 | Using port forwarding silently enables server access to the local SSH agent — Ruby |
| HIGH | GHSA-hjwv-j52r-xcg7 | net-ssh | 7.3.3 | ~> 7.3.9, >= 8.1.1 | net-ssh - @revoked known_hosts entries are treated as valid pinned host keys — revoked host key accepted — Ruby |
| HIGH | CVE-2026-107891 | musl | 1.2.5-r23 | 1.2.5-r24 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/openvoxproject/openbolt:latest (alpine 3.23.4) |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.5-r23 | 1.2.5-r24 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/openvoxproject/openbolt:latest (alpine 3.23.4) |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | zlib: zlib: Heap buffer overflow in gz_vacate() allows arbitrary code execution — ghcr.io/openvoxproject/openbolt:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-80213 | resolv | 0.2.3 | ~> 0.3.2, >= 0.7.2 | resolv: Resolv gem: DNS allowlist and egress bypass, and cache poisoning via crafted hostnames — Ruby |
| MEDIUM | GHSA-qcf4-j55x-72hv | net-ssh | 7.3.3 | ~> 7.3.10, >= 8.1.2 | Net::SSH::Proxy::HTTPS disables TLS certificate verification by default (CWE-295) — Ruby |
| MEDIUM | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | Improper Restriction of Operations within the Bounds of a Memory Buffe ... — ghcr.io/openvoxproject/openbolt:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-126348 | addressable | 2.9.0 | 2.9.1 | CVE-2026-126348 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| MEDIUM | GHSA-r6vf-943r-2wvw | minitar | 1.1.0 | ~> 1.1.1, >= 1.2.0 | minitar path traversal vulnerability on Windows with a maliciously crafted tarball — Ruby |
| MEDIUM | GHSA-9crm-g4mf-wc5j | addressable | 2.9.0 | >= 2.9.1 | Addressable display_uri can show misleading hosts with invalid Punycode A-labels — Ruby |
| MEDIUM | GHSA-8gmh-2hhj-2hv9 | addressable | 2.9.0 | >= 2.9.1 | Addressable URI normalization resolves some dotted path segments to the wrong path — Ruby |
| MEDIUM | GHSA-4w5q-wg7v-w6gp | addressable | 2.9.0 | >= 2.9.1 | Regular Expression Denial of Service in Addressable templates with several exploded variables — Ruby |
| MEDIUM | CVE-2026-126354 | addressable | 2.9.0 | 2.9.1 | CVE-2026-126354 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| MEDIUM | CVE-2026-126352 | addressable | 2.9.0 | >= 2.9.1 | CVE-2026-126352 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| MEDIUM | CVE-2026-126351 | addressable | 2.9.0 | >= 2.9.1 | CVE-2026-126351 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| MEDIUM | CVE-2026-126350 | addressable | 2.9.0 | >= 2.9.1 | CVE-2026-126350 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| LOW | GHSA-539f-xcgw-2gjg | addressable | 2.9.0 | >= 2.9.1 | Addressable display_uri can show misleading hosts containing bidi and invisible characters — Ruby |
| LOW | CVE-2026-126349 | addressable | 2.9.0 | 2.9.1 | CVE-2026-126349 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| UNKNOWN | GHSA-3x7f-q7wf-fp73 | net-ssh | 7.3.3 | ~> 7.3, >= 7.3.5, >= 8.0.0.rc2 | Shell injection via unescaped substitution in ProxyCommand and ProxyJump command templates in net-ssh — Ruby |
| UNKNOWN | GHSA-ggxh-cfwq-5xqc | net-ssh | 7.3.3 | ~> 7.3, >= 7.3.5, >= 8.0.0.rc2 | Pre-auth unbounded KEX packet queue leads to memory exhaustion — Ruby |
| UNKNOWN | GHSA-pfqh-p9vh-wx4p | net-ssh | 7.3.3 | ~> 7.3, >= 7.3.5, >= 8.0.0.rc2 | Pre-auth unbounded transport packet_size leads to memory exhaustion — Ruby |
| UNKNOWN | GHSA-r75w-7fhp-84w8 | net-ssh | 7.3.3 | ~> 7.3, >= 7.3.5, >= 8.0.0.rc2 | Pre-auth unbounded banner/identification buffering DoS — Ruby |
| UNKNOWN | GHSA-rpq3-v334-f5pm | net-ssh | 7.3.3 | ~> 7.3, >= 7.3.5, >= 8.0.0.rc2 | Parsing a specifically crafted ed25519 ssh key will lock net/ssh in DOS — Ruby |
| UNKNOWN | GHSA-cx24-f932-rr55 | rubyntlm | 0.6.5 | >= 0.6.6 | NTLMv2 authentication bypass - Type3#password? ignores its password argument and verifies every message against the empty password — Ruby |
Grype
CRITICAL 7
HIGH 7
MEDIUM 6
LOW 1
NVD/CPE filtered 54
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | GHSA-qm4g-8pfh-6996 | ruby | 3.2.11 | 3.3.13 | Overflow of internal identifiers in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-22mf-ggw7-pxfx | ruby | 3.2.11 | 3.3.13 | Integer overflow in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-gfj3-8wj9-qx8p | ruby | 3.2.11 | 3.3.13 | Double free in regular expression parsing — /usr/local/bin/ruby |
| CRITICAL | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | /lib/apk/db/installed |
| CRITICAL | GHSA-7x2q-68qv-6p8x | ruby | 3.2.11 | 3.3.14 | Double free in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-3p8q-wmhx-vm2w | ruby | 3.2.11 | 3.3.14 | Heap buffer overflow in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-34m4-m9fh-gqp5 | ruby | 3.2.11 | 3.3.14 | Heap buffer overflow in case conversion of strings — /usr/local/bin/ruby |
| HIGH | GHSA-47m2-wp7j-p9vc | rubyzip | 2.4.1 | 3.4.0 | rubyzip path traversal vulnerability — /opt/openbolt/vendor/bundle/ruby/3.2.0/specifications/rubyzip-2.4.1.gemspec |
| HIGH | CVE-2026-107891 | musl | 1.2.5-r23 | 1.2.5-r24 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.5-r23 | 1.2.5-r24 | /lib/apk/db/installed |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | /lib/apk/db/installed |
| HIGH | GHSA-wpqw-5qxg-m68r | ruby | 3.2.11 | 3.3.14 | Out-of-bounds read in case-insensitive regular expression matching — /usr/local/bin/ruby |
| HIGH | GHSA-87fm-7w84-j2px | ruby | 3.2.11 | 3.3.14 | Integer overflow in case conversion of strings — /usr/local/bin/ruby |
| HIGH | GHSA-7whj-cfh7-xgm4 | ruby | 3.2.11 | 3.3.14 | Heap buffer overflow in Regexp#to_s — /usr/local/bin/ruby |
| MEDIUM | GHSA-pvgc-g7gj-pv6h | ruby | 3.2.11 | 3.3.14 | Out-of-bounds read in case-insensitive backreference matching — /usr/local/bin/ruby |
| MEDIUM | GHSA-9crm-g4mf-wc5j | addressable | 2.9.0 | 2.9.1 | Addressable display_uri can show misleading hosts with invalid Punycode A-labels — /opt/openbolt/vendor/bundle/ruby/3.2.0/specifications/addressable-2.9.0.gemspec |
| MEDIUM | GHSA-8gmh-2hhj-2hv9 | addressable | 2.9.0 | 2.9.1 | Addressable URI normalization resolves some dotted path segments to the wrong path — /opt/openbolt/vendor/bundle/ruby/3.2.0/specifications/addressable-2.9.0.gemspec |
| MEDIUM | GHSA-qq38-m9mg-xjj5 | addressable | 2.9.0 | 2.9.1 | Addressable: Denial of service in URI path normalization — /opt/openbolt/vendor/bundle/ruby/3.2.0/specifications/addressable-2.9.0.gemspec |
| MEDIUM | GHSA-j82w-28jv-3pmj | addressable | 2.9.0 | 2.9.1 | Addressable: Regular Expression Denial of Service in templates with certain exploded expressions — /opt/openbolt/vendor/bundle/ruby/3.2.0/specifications/addressable-2.9.0.gemspec |
| MEDIUM | GHSA-9f42-57jx-vpp3 | addressable | 2.9.0 | 2.9.1 | Addressable: Regular Expression Denial of Service in templates with multiple variables — /opt/openbolt/vendor/bundle/ruby/3.2.0/specifications/addressable-2.9.0.gemspec |
| LOW | GHSA-539f-xcgw-2gjg | addressable | 2.9.0 | 2.9.1 | Addressable display_uri can show misleading hosts containing bidi and invisible characters — /opt/openbolt/vendor/bundle/ruby/3.2.0/specifications/addressable-2.9.0.gemspec |
Filtered NVD/CPE matches (54)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-107493 | libssl3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-132825 | ruby | 3.2.11 | 3.3.14, 3.4.13, 4.0.10 | Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. — /usr/local/bin/ruby |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-88823 | libssl3 | 3.5.8-r0 | Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-88823 | libcrypto3 | 3.5.8-r0 | Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95691 | libssl3 | 3.5.8-r0 | Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95691 | libcrypto3 | 3.5.8-r0 | Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107496 | libssl3 | 3.5.8-r0 | Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely. Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service. CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns. The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option. The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected. The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely. FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107496 | libcrypto3 | 3.5.8-r0 | Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely. Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service. CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns. The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option. The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected. The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely. FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached. — /lib/apk/db/installed | |
| HIGH | CVE-2026-54873 | libcrypto3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libcrypto3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libssl3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libssl3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-54873 | libssl3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libcrypto3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libcrypto3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95692 | libssl3 | 3.5.8-r0 | Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected. Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV. CWE: CWE-125: Out-of-bounds Read Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length. The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery. Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application. FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95692 | libcrypto3 | 3.5.8-r0 | Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected. Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV. CWE: CWE-125: Out-of-bounds Read Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length. The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery. Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application. FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libssl3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-88822 | libssl3 | 3.5.8-r0 | Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-88822 | libcrypto3 | 3.5.8-r0 | Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75806 | libssl3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75806 | libcrypto3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libssl3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libcrypto3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libcrypto3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libssl3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libcrypto3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libssl3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libcrypto3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libssl3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libssl3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libcrypto3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libssl3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libssl3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libcrypto3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libcrypto3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed |
ghcr.io/openvoxproject/openvoxagent
Downloads
ghcr.io/openvoxproject/openvoxagent:latest (2026-10-14)
Trivy
HIGH 6
MEDIUM 72
LOW 6
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-111943 | stdlib | v1.26.7 | 1.26.10, 1.27.3 | crypto/x509: golang: crypto/x509: Man-in-the-middle attacks via untrusted intermediate certificates — usr/bin/pebble |
| HIGH | CVE-2026-78667 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | net/http: golang: golang: Denial of Service via crafted HTTP Range headers — usr/bin/pebble |
| HIGH | CVE-2026-78669 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames — usr/bin/pebble |
| HIGH | CVE-2026-97031 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references — usr/bin/pebble |
| HIGH | CVE-2026-109518 | libapt-pkg7.0 | 3.2.0 | 3.2.1ubuntu0.1 | apt: apt: Remote code execution via hard link reuse during package download retries — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| HIGH | CVE-2026-109518 | apt | 3.2.0 | 3.2.1ubuntu0.1 | apt: apt: Remote code execution via hard link reuse during package download retries — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-97054 | stdlib | v1.26.7 | 1.26.11, 1.27.4 | net/http: golang: net/http: Denial of Service via race condition when handling oversized HTTP/1 requests — usr/bin/pebble |
| MEDIUM | CVE-2026-9538 | perl-base | 5.40.1-7ubuntu0.3 | perl-Archive-Tar: perl-Archive-Tar: Denial of Service via crafted tar header with large entry size — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-82560 | perl-base | 5.40.1-7ubuntu0.3 | 5.40.1-7ubuntu0.4 | Pod::Text versions before 6.1.1 for Perl allow CPU and memory exhausti ... — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-48962 | perl-base | 5.40.1-7ubuntu0.3 | perl-IO-Compress: perl-IO-Compress: Arbitrary code execution via attacker-controlled output glob — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | mount | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | mount | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | mount | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-18374 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-78408 | libsmartcols1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | libsmartcols1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | libuuid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libuuid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-121876 | libsystemd0 | 259.5-0ubuntu3.4 | sandboxed-containers: kernel: systemd-gpt-auto-generator: Guest Data Leakage in Confidential Computing (Sandboxed Containers) — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libuuid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-121876 | libudev1 | 259.5-0ubuntu3.4 | sandboxed-containers: kernel: systemd-gpt-auto-generator: Guest Data Leakage in Confidential Computing (Sandboxed Containers) — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-97032 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: net/http: Denial of Service via concurrent HPACK encoder modification — usr/bin/pebble |
| MEDIUM | CVE-2026-97030 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | html/template: golang: html/template: Cross-site scripting via improper escaping of yield keyword — usr/bin/pebble |
| MEDIUM | CVE-2026-94448 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | html/template: golang: golang: cross-site scripting via consecutive expressions in JavaScript template literals — usr/bin/pebble |
| MEDIUM | CVE-2026-94440 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | net/textproto: mime/multipart: golang: golang: Denial of Service via memory limit bypass in multipart form parsing — usr/bin/pebble |
| MEDIUM | CVE-2026-94439 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | net/http: golang: net/http: HTTP request smuggling via improper handling of HTTP/1 CONNECT responses — usr/bin/pebble |
| MEDIUM | CVE-2026-78663 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: golang: flow control limit bypass via double refund in HTTP/2 server — usr/bin/pebble |
| MEDIUM | CVE-2026-78660 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | net/http: golang: golang.org/x/net/http2: net/http: HTTP response smuggling via malformed HTTP/2 framing headers — usr/bin/pebble |
| MEDIUM | CVE-2026-78659 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | net/http: golang.org/x/net/http2: golang: net/http: Denial of Service via HTTP/2 trailer header memory exhaustion — usr/bin/pebble |
| MEDIUM | CVE-2026-56866 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | net/http: golang: golang: Cross-user response poisoning via desynchronized HTTP CONNECT connections — usr/bin/pebble |
| MEDIUM | CVE-2026-85091 | zlib1g | 1:1.3.dfsg+really1.3.1-1ubuntu3.1 | 1:1.3.dfsg+really1.3.1-1ubuntu3.2 | zlib: zlib: Heap buffer overflow in gz_vacate() allows arbitrary code execution — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-78410 | util-linux | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | util-linux | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | util-linux | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-18508 | tar | 1.35+dfsg-4ubuntu0.4 | tar: tar: --one-top-level hardlink targets not confined to top-level directory enabling arbitrary file overwrite — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-18477 | tar | 1.35+dfsg-4ubuntu0.4 | tar: tar: TOCTOU in incremental dumpdir 'X' rename handling allows restore path escape — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-35371 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | The id utility in uutils coreutils exhibits incorrect behavior in its ... — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-35370 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | The id utility in uutils coreutils miscalculates the groups= section o ... — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-97399 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Denial of Service via out-of-bounds read in strncasecmp — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-95818 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Local attacker can cause denial of service and information disclosure via stack-based buffer overflow. — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-86805 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Privilege escalation and arbitrary code execution via TOCTOU race condition in dynamic loader — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-8674 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc DNS stub resolver: Denial of Service via long search domain in configuration — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-84243 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Arbitrary code execution via directory traversal in LANGUAGE environment variable — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-18374 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-97399 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Denial of Service via out-of-bounds read in strncasecmp — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-95818 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Local attacker can cause denial of service and information disclosure via stack-based buffer overflow. — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-86805 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Privilege escalation and arbitrary code execution via TOCTOU race condition in dynamic loader — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-8674 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc DNS stub resolver: Denial of Service via long search domain in configuration — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-84243 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Arbitrary code execution via directory traversal in LANGUAGE environment variable — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-18374 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-78410 | libblkid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libblkid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libblkid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-102474 | dash | 0.5.12-12ubuntu3 | dash: dash: Heap out-of-bounds write in conv_escape via undersized Unicode escape reservation — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-102473 | dash | 0.5.12-12ubuntu3 | dash: dash: Super-polynomial backtracking in pmatch when libc fnmatch is disabled — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | bsdutils | 1:2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | bsdutils | 1:2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | bsdutils | 1:2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libsmartcols1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-89162 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | pcre2: PCRE2: Information disclosure via pcre2_serialize_encode — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-89161 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-89160 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | pcre2: PCRE2: Denial of Service via out-of-bounds read during invalid UTF matching — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-89158 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-89157 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | pcre2: PCRE2: Out-of-bounds write via large pattern input — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-89156 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | PCRE2: PCRE2: Out-of-bounds read via invalid UTF data during JIT fallback — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-86145 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-103111 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | pcre2: pcre2: Out-of-bounds write via crafted regular expression — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-78410 | libmount1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libmount1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libmount1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-97399 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Denial of Service via out-of-bounds read in strncasecmp — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-95818 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Local attacker can cause denial of service and information disclosure via stack-based buffer overflow. — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-86805 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Privilege escalation and arbitrary code execution via TOCTOU race condition in dynamic loader — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-8674 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc DNS stub resolver: Denial of Service via long search domain in configuration — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-84243 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Arbitrary code execution via directory traversal in LANGUAGE environment variable — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) |
| LOW | CVE-2024-56433 | login.defs | 1:4.17.4-2ubuntu3 | shadow-utils: Default subordinate ID configuration in /etc/login.defs could lead to compromise — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| LOW | CVE-2026-40228 | libudev1 | 259.5-0ubuntu3.4 | systemd: systemd-journald: Unintended output to user terminals via logger command — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| LOW | CVE-2026-105712 | gpgv | 2.4.8-4ubuntu3.1 | gnupg2: gnupg: Arbitrary file overwrite via symlink traversal in gpgtar — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| LOW | CVE-2026-40228 | libsystemd0 | 259.5-0ubuntu3.4 | systemd: systemd-journald: Unintended output to user terminals via logger command — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| LOW | CVE-2024-56433 | passwd | 1:4.17.4-2ubuntu3 | shadow-utils: Default subordinate ID configuration in /etc/login.defs could lead to compromise — ghcr.io/openvoxproject/openvoxagent:latest (ubuntu 26.04) | |
| LOW | CVE-2026-56857 | stdlib | v1.26.7 | 1.26.9, 1.27.2 | os: golang: golang: Directory traversal via Windows junction handling — usr/bin/pebble |
Grype
CRITICAL 1
HIGH 10
MEDIUM 134
LOW 6
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | GO-2026-6612 | stdlib | go1.26.7 | 1.26.9 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. — /usr/bin/pebble |
| HIGH | GO-2026-6613 | stdlib | go1.26.7 | 1.26.9, 1.27.2 | When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP. — /usr/bin/pebble |
| HIGH | GO-2026-6610 | stdlib | go1.26.7 | 1.26.9 | Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling. — /usr/bin/pebble |
| HIGH | GO-2026-6605 | stdlib | go1.26.7 | 1.26.9, 1.27.2 | When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning. — /usr/bin/pebble |
| HIGH | GO-2026-6617 | stdlib | go1.26.7 | 1.26.9 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. — /usr/bin/pebble |
| HIGH | GO-2026-6608 | stdlib | go1.26.7 | 1.26.9, 1.27.2 | Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes. — /usr/bin/pebble |
| HIGH | GO-2026-6607 | stdlib | go1.26.7 | 1.26.9, 1.27.2 | Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result. — /usr/bin/pebble |
| HIGH | GO-2026-6611 | stdlib | go1.26.7 | 1.26.9 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. — /usr/bin/pebble |
| HIGH | GO-2026-6603 | stdlib | go1.26.7 | 1.26.9 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. — /usr/bin/pebble |
| HIGH | CVE-2026-109518 | libapt-pkg7.0 | 3.2.0 | 3.2.1ubuntu0.1 | /var/lib/dpkg/status |
| HIGH | CVE-2026-109518 | apt | 3.2.0 | 3.2.1ubuntu0.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-76642 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107493 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91094 | dpkg | 1.23.7ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-89158 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-78408 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18508 | tar | 1.35+dfsg-4ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-56391 | coreutils | 9.5-1ubuntu2+0.0.0~ubuntu25 | 9.7-3ubuntu2.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-35371 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-15649 | perl-base | 5.40.1-7ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-89161 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-102474 | dash | 0.5.12-12ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35370 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18477 | tar | 1.35+dfsg-4ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-102473 | dash | 0.5.12-12ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95818 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-95818 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-95818 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-86805 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-86805 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-86805 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-54370 | libacl1 | 2.3.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121876 | libsystemd0 | 259.5-0ubuntu3.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121876 | libudev1 | 259.5-0ubuntu3.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-89162 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-54369 | libacl1 | 2.3.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18374 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-18374 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-18374 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-107493 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107493 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-82560 | perl-base | 5.40.1-7ubuntu0.3 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-121758 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121758 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-7017 | perl-base | 5.40.1-7ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-89157 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-107496 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107496 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107496 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-8674 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-8674 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-8674 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-97399 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-48959 | perl-base | 5.40.1-7ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-9538 | perl-base | 5.40.1-7ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-85091 | zlib1g | 1:1.3.dfsg+really1.3.1-1ubuntu3.1 | 1:1.3.dfsg+really1.3.1-1ubuntu3.2 | /var/lib/dpkg/status |
| MEDIUM | GO-2026-6809 | stdlib | go1.26.7 | 1.26.10, 1.27.3 | On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy. — /usr/bin/pebble |
| MEDIUM | CVE-2026-124024 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124024 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124024 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48962 | perl-base | 5.40.1-7ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-86145 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | /var/lib/dpkg/status |
| MEDIUM | GO-2026-6859 | stdlib | go1.26.7 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/bin/pebble |
| MEDIUM | CVE-2026-121758 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-97399 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-97399 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-103111 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-89160 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-88823 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88823 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88823 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48961 | perl-base | 5.40.1-7ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84243 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-84243 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-84243 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-89156 | libpcre2-8-0 | 10.46-1build1 | 10.46-1ubuntu0.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-107494 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107494 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107494 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95691 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95691 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95691 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| LOW | CVE-2026-105712 | gpgv | 2.4.8-4ubuntu3.1 | /var/lib/dpkg/status | |
| LOW | CVE-2024-56433 | login.defs | 1:4.17.4-2ubuntu3 | /var/lib/dpkg/status | |
| LOW | CVE-2024-56433 | passwd | 1:4.17.4-2ubuntu3 | /var/lib/dpkg/status | |
| LOW | CVE-2025-5278 | coreutils | 9.5-1ubuntu2+0.0.0~ubuntu25 | 9.7-3ubuntu2.1 | /var/lib/dpkg/status |
| LOW | CVE-2026-40228 | libudev1 | 259.5-0ubuntu3.4 | /var/lib/dpkg/status | |
| LOW | CVE-2026-40228 | libsystemd0 | 259.5-0ubuntu3.4 | /var/lib/dpkg/status |
ghcr.io/openvoxproject/openvoxdb
Downloads
ghcr.io/openvoxproject/openvoxdb:latest (2026-11-11)
Trivy
HIGH 2
MEDIUM 88
LOW 12
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2022-41404 | org.ini4j:ini4j | 0.5.4 | org.ini4j: unspecified DoS — Java | |
| HIGH | CVE-2026-114938 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | OpenJDK: OpenJDK: remote code execution via memory corruption on x86-64 systems with AVX-512 VBMI — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-97054 | stdlib | v1.27.3 | 1.26.11, 1.27.4 | net/http: golang: net/http: Denial of Service via race condition when handling oversized HTTP/1 requests — usr/bin/pebble |
| MEDIUM | CVE-2026-114941 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | OpenJDK: OpenJDK: Improve integer compression — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-114940 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | OpenJDK: OpenJDK: Improve TLS client connections — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-114939 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | OpenJDK: OpenJDK: The acceptor does not properly implement RFC 4120 requirements for handling cross-realm tickets. — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-78410 | mount | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | mount | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | mount | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | libuuid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libuuid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libuuid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-121876 | libudev1 | 259.9-0ubuntu0.1 | sandboxed-containers: kernel: systemd-gpt-auto-generator: Guest Data Leakage in Confidential Computing (Sandboxed Containers) — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-121876 | libsystemd0 | 259.9-0ubuntu0.1 | sandboxed-containers: kernel: systemd-gpt-auto-generator: Guest Data Leakage in Confidential Computing (Sandboxed Containers) — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | libsmartcols1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libsmartcols1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libsmartcols1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107161 | libsasl2-modules-db | 2.1.28+dfsg1-9ubuntu3 | cyrus-sasl: Heap buffer overflow in cyrus-sasl add_to_challenge() allows malicious server to crash or compromise DIGEST-MD5 clients — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107161 | libsasl2-2 | 2.1.28+dfsg1-9ubuntu3 | cyrus-sasl: Heap buffer overflow in cyrus-sasl add_to_challenge() allows malicious server to crash or compromise DIGEST-MD5 clients — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2025-10990 | libruby3.3 | 3.3.8-2ubuntu3.1 | rexml: REXML: Denial of Service via inefficient regex parsing — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-9538 | libperl5.40 | 5.40.1-7ubuntu0.4 | perl-Archive-Tar: perl-Archive-Tar: Denial of Service via crafted tar header with large entry size — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | util-linux | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | util-linux | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | util-linux | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-18508 | tar | 1.35+dfsg-4ubuntu0.4 | tar: tar: --one-top-level hardlink targets not confined to top-level directory enabling arbitrary file overwrite — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-18477 | tar | 1.35+dfsg-4ubuntu0.4 | tar: tar: TOCTOU in incremental dumpdir 'X' rename handling allows restore path escape — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-35371 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | The id utility in uutils coreutils exhibits incorrect behavior in its ... — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-35370 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | The id utility in uutils coreutils miscalculates the groups= section o ... — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2025-10990 | ruby3.3 | 3.3.8-2ubuntu3.1 | rexml: REXML: Denial of Service via inefficient regex parsing — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-9538 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | perl-Archive-Tar: perl-Archive-Tar: Denial of Service via crafted tar header with large entry size — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-48962 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | perl-IO-Compress: perl-IO-Compress: Arbitrary code execution via attacker-controlled output glob — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-9538 | perl-base | 5.40.1-7ubuntu0.4 | perl-Archive-Tar: perl-Archive-Tar: Denial of Service via crafted tar header with large entry size — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-48962 | perl-base | 5.40.1-7ubuntu0.4 | perl-IO-Compress: perl-IO-Compress: Arbitrary code execution via attacker-controlled output glob — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-9538 | perl | 5.40.1-7ubuntu0.4 | perl-Archive-Tar: perl-Archive-Tar: Denial of Service via crafted tar header with large entry size — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-48962 | perl | 5.40.1-7ubuntu0.4 | perl-IO-Compress: perl-IO-Compress: Arbitrary code execution via attacker-controlled output glob — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-83408 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | Vulnerability in the Oracle GraalVM for JDK, Oracle GraalVM produ ... — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-83368 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | Vulnerability in the Oracle GraalVM for JDK, Oracle GraalVM Enter ... — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-83357 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | Vulnerability in the Oracle GraalVM for JDK, Oracle GraalVM produ ... — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-114946 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | OpenJDK: OpenJDK: Enhance loop handling — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-114945 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | OpenJDK: OpenJDK: Enhance StringBuilder checks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-114944 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | OpenJDK: OpenJDK: Enhance JMX Connections — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-114943 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | OpenJDK: OpenJDK: Enhance JFR Events — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-114942 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | OpenJDK: OpenJDK: Enhance vector masks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-48962 | libperl5.40 | 5.40.1-7ubuntu0.4 | perl-IO-Compress: perl-IO-Compress: Arbitrary code execution via attacker-controlled output glob — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-95818 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Local attacker can cause denial of service and information disclosure via stack-based buffer overflow. — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-86805 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Privilege escalation and arbitrary code execution via TOCTOU race condition in dynamic loader — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-8674 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc DNS stub resolver: Denial of Service via long search domain in configuration — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-84243 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Arbitrary code execution via directory traversal in LANGUAGE environment variable — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-18374 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-97399 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Denial of Service via out-of-bounds read in strncasecmp — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-95818 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Local attacker can cause denial of service and information disclosure via stack-based buffer overflow. — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-86805 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Privilege escalation and arbitrary code execution via TOCTOU race condition in dynamic loader — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-8674 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc DNS stub resolver: Denial of Service via long search domain in configuration — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-84243 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Arbitrary code execution via directory traversal in LANGUAGE environment variable — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-18374 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-97399 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Denial of Service via out-of-bounds read in strncasecmp — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-95818 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Local attacker can cause denial of service and information disclosure via stack-based buffer overflow. — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-86805 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Privilege escalation and arbitrary code execution via TOCTOU race condition in dynamic loader — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-8674 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc DNS stub resolver: Denial of Service via long search domain in configuration — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-84243 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Arbitrary code execution via directory traversal in LANGUAGE environment variable — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-18374 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-78410 | libblkid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libblkid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libblkid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-102474 | dash | 0.5.12-12ubuntu3 | dash: dash: Heap out-of-bounds write in conv_escape via undersized Unicode escape reservation — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-102473 | dash | 0.5.12-12ubuntu3 | dash: dash: Super-polynomial backtracking in pmatch when libc fnmatch is disabled — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | bsdutils | 1:2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | bsdutils | 1:2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | bsdutils | 1:2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-13757 | libp11-kit0 | 0.26.2-2 | p11-kit: Stack exhaustion via unbounded recursion in RPC attribute parsing — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | libmount1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libmount1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libmount1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107778 | libkrb5support0 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via crafted forwarded credentials — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107708 | libkrb5support0 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via malformed PAC in S4U2Proxy requests — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107778 | libkrb5-3 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via crafted forwarded credentials — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107708 | libkrb5-3 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via malformed PAC in S4U2Proxy requests — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107778 | libk5crypto3 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via crafted forwarded credentials — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-97399 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | glibc: glibc: Denial of Service via out-of-bounds read in strncasecmp — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
| MEDIUM | CVE-2026-67693 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: Information disclosure via contradictory Key Usage and Extended Key Usage extensions — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-88647 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: Information disclosure via hostname verification bypass — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-88648 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: Cross-domain certificate restriction bypass via incomplete X.509 validation — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-95184 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: legitimate user certificates incorrectly rejected causing denial of service — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-95210 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: certificates with invalid extensions incorrectly accepted — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107708 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via malformed PAC in S4U2Proxy requests — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107778 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via crafted forwarded credentials — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107708 | libk5crypto3 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via malformed PAC in S4U2Proxy requests — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2026-40228 | libsystemd0 | 259.9-0ubuntu0.1 | systemd: systemd-journald: Unintended output to user terminals via logger command — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2024-56433 | login.defs | 1:4.17.4-2ubuntu3 | shadow-utils: Default subordinate ID configuration in /etc/login.defs could lead to compromise — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2025-43857 | ruby3.3 | 3.3.8-2ubuntu3.1 | net-imap: net-imap rubygem vulnerable to possible DoS by memory exhaustion — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2025-58767 | ruby3.3 | 3.3.8-2ubuntu3.1 | rexml: REXML denial of service — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2025-61594 | ruby3.3 | 3.3.8-2ubuntu3.1 | uri: URI module: Credential exposure via URI + operator — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2026-40228 | libudev1 | 259.9-0ubuntu0.1 | systemd: systemd-journald: Unintended output to user terminals via logger command — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2018-10126 | libjpeg-turbo8 | 2.1.5-4ubuntu4 | libtiff: NULL pointer dereference in the jpeg_fdct_16x16 function in jfdctint.c — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2026-105712 | gpgv | 2.4.8-4ubuntu3.1 | gnupg2: gnupg: Arbitrary file overwrite via symlink traversal in gpgtar — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2025-61594 | libruby3.3 | 3.3.8-2ubuntu3.1 | uri: URI module: Credential exposure via URI + operator — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2025-58767 | libruby3.3 | 3.3.8-2ubuntu3.1 | rexml: REXML denial of service — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2025-43857 | libruby3.3 | 3.3.8-2ubuntu3.1 | net-imap: net-imap rubygem vulnerable to possible DoS by memory exhaustion — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) | |
| LOW | CVE-2024-56433 | passwd | 1:4.17.4-2ubuntu3 | shadow-utils: Default subordinate ID configuration in /etc/login.defs could lead to compromise — ghcr.io/openvoxproject/openvoxdb:latest (ubuntu 26.04) |
Grype
HIGH 3
MEDIUM 402
LOW 16
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | GHSA-jr6h-r7vg-f9mc | ini4j | 0.5.4 | org.ini4j allows attackers to cause a Denial of Service (DoS) — /opt/puppetlabs/server/apps/puppetdb/puppetdb.jar | |
| HIGH | GHSA-q339-8rmv-2mhv | erb | 4.0.3 | 4.0.3.1 | ERB has an @_init deserialization guard bypass via def_module / def_method / def_class — /usr/lib/ruby/gems/3.3.0/specifications/default/erb-4.0.3.gemspec |
| HIGH | CVE-2026-114938 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-76642 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47241 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114943 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-88647 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91094 | dpkg | 1.23.7ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119378 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116312 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116312 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91395 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120146 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120146 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-127039 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48961 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48961 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48961 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48961 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-60589 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116303 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116303 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112061 | librtmp1 | 2.4+20151223.gitfa8646d.1-3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116327 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116327 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-127231 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119374 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116311 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116311 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91381 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-105111 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47241 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116308 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116321 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116310 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116321 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116310 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84243 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-84243 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-84243 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-114940 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-114939 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-121757 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91417 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-87255 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-8674 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-8674 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-8674 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-91396 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91411 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88823 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88823 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88823 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-94114 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-16240 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-16240 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-16237 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-16237 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-83368 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119379 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-97399 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-97399 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-97399 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-95691 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95691 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95691 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107494 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107494 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107494 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120154 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120152 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120154 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120152 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116308 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71200 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-86805 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-86805 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-95818 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-95818 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-95818 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-102473 | dash | 0.5.12-12ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18477 | tar | 1.35+dfsg-4ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18938 | libp11-kit0 | 0.26.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91484 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35370 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-102474 | dash | 0.5.12-12ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-15649 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-15649 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-15649 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-15649 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35371 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119377 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-56391 | coreutils | 9.5-1ubuntu2+0.0.0~ubuntu25 | 9.7-3ubuntu2.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-47242 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47242 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18508 | tar | 1.35+dfsg-4ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | GHSA-46q3-7gv7-qmgg | net-imap | 0.4.19 | 0.5.15 | Net::IMAP: Command Injection via ID command argument — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| MEDIUM | CVE-2026-107493 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107493 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107493 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71199 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-118380 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-111423 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107884 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107364 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71200 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71199 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-118380 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-111423 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107884 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107364 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71200 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71199 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-118380 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-111423 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107884 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107364 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71200 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71199 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-118380 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-111423 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107884 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107364 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-54370 | libacl1 | 2.3.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-86805 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-132825 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119371 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119375 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95210 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88648 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95184 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114946 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-87293 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114945 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-114942 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-114941 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-114944 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-76642 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18374 | libc6 | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-18374 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-18374 | libc-bin | 2.43-2ubuntu2.4 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-119372 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-54369 | libacl1 | 2.3.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-13757 | libp11-kit0 | 0.26.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119373 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121876 | libudev1 | 259.9-0ubuntu0.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121876 | libsystemd0 | 259.9-0ubuntu0.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-67693 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119591 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112060 | librtmp1 | 2.4+20151223.gitfa8646d.1-3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119376 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-132825 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116307 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120144 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120139 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116335 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116307 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120151 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120141 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116309 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120151 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120141 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116309 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116319 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116319 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120149 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116317 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116315 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120149 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116317 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116315 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6467 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6467 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116336 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116336 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116326 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116326 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | GHSA-g857-hhfv-j68w | zlib | 3.1.1 | 3.1.2 | Buffer Overflow in Zlib::GzipReader ungetc via large input leads to memory corruption — /usr/lib/ruby/gems/3.3.0/specifications/default/zlib-3.1.1.gemspec |
| MEDIUM | CVE-2026-129483 | libsasl2-modules-db | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116328 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116323 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18447 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116304 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18447 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116304 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120147 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120142 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116320 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116306 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120147 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120142 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116320 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116306 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6460 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120143 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116332 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116331 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6460 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120143 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116332 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116331 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120144 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120139 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116335 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112316 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112320 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112320 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112320 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112320 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112319 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112319 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112319 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112319 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112322 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112322 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112322 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112322 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-41316 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-41316 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112321 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112321 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112321 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112321 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112314 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112314 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112314 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112314 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-110264 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-110264 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119586 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112318 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112318 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112318 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112318 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-42258 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-42258 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112317 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112317 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112317 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112317 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | GHSA-75xq-5h9v-w6px | net-imap | 0.4.19 | 0.4.24 | net-imap vulnerable to command Injection via unvalidated Symbol inputs — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| MEDIUM | CVE-2026-119079 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112323 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119079 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112323 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119079 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112323 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119079 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112323 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112315 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112315 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112315 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112315 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112316 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112316 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112316 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-129483 | libsasl2-2 | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-54696 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-54696 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | GO-2026-6859 | stdlib | go1.27.3 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/bin/pebble |
| MEDIUM | CVE-2026-83408 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116318 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116318 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-14661 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-14661 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48962 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48962 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48962 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48962 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107778 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107778 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107778 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107778 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-63435 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-63435 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-83357 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124024 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107496 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107496 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107496 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-127040 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-7017 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-7017 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-7017 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-7017 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116322 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116322 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116333 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116333 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121758 | libc6 | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121758 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121758 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116330 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116330 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116325 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116325 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107161 | libsasl2-modules-db | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107161 | libsasl2-2 | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91382 | openjdk-21-jre-headless | 21.0.13.0.3+1-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120145 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120145 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | GHSA-j3g3-5qv5-52mj | net-imap | 0.4.19 | 0.4.20 | net-imap rubygem vulnerable to possible DoS by memory exhaustion — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| MEDIUM | CVE-2025-10990 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-10990 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107708 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107708 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107708 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107708 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120153 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120153 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48959 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48959 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48959 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48959 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-132138 | libsasl2-modules-db | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-132138 | libsasl2-2 | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120150 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120150 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-27820 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-27820 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116329 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116328 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116323 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116329 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120148 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-120148 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116316 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47240 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47240 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116313 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116316 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116313 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-9538 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-9538 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-46727 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-46727 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124024 | libc-bin | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-9538 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-9538 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116314 | postgresql-client-18 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-116314 | libpq5 | 18.6-0ubuntu0.26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | GHSA-8p34-64r3-mwg8 | net-imap | 0.4.19 | 0.5.15 | Net::IMAP: Command Injection via non-synchronizing literal in "raw" argument — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| MEDIUM | CVE-2026-124024 | libc-gconv-modules-extra | 2.43-2ubuntu2.4 | /var/lib/dpkg/status | |
| LOW | GHSA-j4pr-3wm6-xx2r | uri | 0.13.2 | 0.13.3 | URI Credential Leakage Bypass over CVE-2025-27221 — /usr/lib/ruby/gems/3.3.0/specifications/default/uri-0.13.2.gemspec |
| LOW | CVE-2025-61594 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| LOW | CVE-2025-61594 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| LOW | CVE-2025-58767 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| LOW | CVE-2025-58767 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| LOW | CVE-2018-10126 | libjpeg-turbo8 | 2.1.5-4ubuntu4 | /var/lib/dpkg/status | |
| LOW | CVE-2025-5278 | coreutils | 9.5-1ubuntu2+0.0.0~ubuntu25 | 9.7-3ubuntu2.1 | /var/lib/dpkg/status |
| LOW | CVE-2024-56433 | login.defs | 1:4.17.4-2ubuntu3 | /var/lib/dpkg/status | |
| LOW | CVE-2024-56433 | passwd | 1:4.17.4-2ubuntu3 | /var/lib/dpkg/status | |
| LOW | CVE-2025-43857 | libruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| LOW | CVE-2026-105712 | gpgv | 2.4.8-4ubuntu3.1 | /var/lib/dpkg/status | |
| LOW | CVE-2025-43857 | ruby3.3 | 3.3.8-2ubuntu3.1 | /var/lib/dpkg/status | |
| LOW | GHSA-c4fp-cxrr-mj66 | net-imap | 0.4.19 | 0.5.15 | Net::IMAP: Denial of Service via incomplete raw argument validation — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| LOW | CVE-2026-40228 | libsystemd0 | 259.9-0ubuntu0.1 | /var/lib/dpkg/status | |
| LOW | CVE-2026-40228 | libudev1 | 259.9-0ubuntu0.1 | /var/lib/dpkg/status | |
| LOW | GHSA-c2f4-jgmc-q2r5 | rexml | 3.3.9 | 3.4.2 | REXML has DoS condition when parsing malformed XML file — /usr/lib/ruby/gems/3.3.0/specifications/rexml-3.3.9.gemspec |
ghcr.io/openvoxproject/openvoxdb:latest-alpine (2026-11-11)
Trivy
CRITICAL 1
HIGH 81
MEDIUM 37
LOW 10
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-114938 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | OpenJDK: OpenJDK: remote code execution via memory corruption on x86-64 systems with AVX-512 VBMI — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116329 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: arbitrary code execution via nested SET DATA TYPE during statistics import — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116328 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via integer wraparound in memory contexts — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116326 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via uncaught exceptions in PL/Perl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116325 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary SQL execution in reindexdb via crafted index name — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116323 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in PL/Tcl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116320 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in PL/Perl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116319 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in plperl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116318 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary SQL execution via improper constraint quoting in pg_dump — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116317 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via heap-based buffer overflow in ts_rank_cd() — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116316 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: PostgreSQL: Privilege escalation via unqualified type resolution in temporary schema — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116315 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via heap-based buffer overflow in tsvector_delete() — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116314 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via crafted archive in pg_restore — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116313 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Privilege escalation via untrusted search path in vacuumdb — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116309 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in PL/Perl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116307 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in plperl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116306 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via composite-value field assignment type confusion — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116304 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in parallel worker coordination — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-114942 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | OpenJDK: OpenJDK: Enhance vector masks — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-114941 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | OpenJDK: OpenJDK: Improve integer compression — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-114940 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | OpenJDK: OpenJDK: Improve TLS client connections — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-114939 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | OpenJDK: OpenJDK: The acceptor does not properly implement RFC 4120 requirements for handling cross-realm tickets. — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2022-41404 | org.ini4j:ini4j | 0.5.4 | org.ini4j: unspecified DoS — Java | |
| HIGH | CVE-2026-6467 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Privilege escalation via uncontrolled search path in extension management — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-6460 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in data definition commands — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-18447 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in SQL-language functions — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-14661 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Persistent Denial of Service via arbitrary file append in sslkeylogfile parameter — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120153 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: arbitrary code execution via SQL injection in extension-script substitutions — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120151 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via PL/pgSQL type confusion — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120150 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in expanded-record domain checks — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120149 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via foreign batch inserts — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120148 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in extended statistics — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120147 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in dblink extension — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120145 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via system catalog replication target — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120144 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: PostgreSQL: Arbitrary code execution via incomplete type-cache invalidation — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120143 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in trigger functions — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120142 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in anonymous RECORD types — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120141 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in materialized set-returning functions — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120139 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via integer wraparound in tuple-size calculations — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116336 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via dropped index in REINDEX CONCURRENTLY — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116335 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: PostgreSQL: Arbitrary code execution via operator link type confusion — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116332 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free during portal setup — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116331 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via aggregate optimization type confusion — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116330 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Arbitrary code execution via predictable restriction key in pg_dump restore script — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116304 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in parallel worker coordination — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116317 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via heap-based buffer overflow in ts_rank_cd() — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116318 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary SQL execution via improper constraint quoting in pg_dump — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116319 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in plperl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116320 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in PL/Perl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116323 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in PL/Tcl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120153 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: arbitrary code execution via SQL injection in extension-script substitutions — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120151 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via PL/pgSQL type confusion — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120150 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in expanded-record domain checks — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120149 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via foreign batch inserts — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120148 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in extended statistics — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120147 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in dblink extension — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120145 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via system catalog replication target — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120144 | libpq | 18.6-r0 | 18.7-r0 | postgresql: PostgreSQL: Arbitrary code execution via incomplete type-cache invalidation — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120143 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in trigger functions — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120142 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in anonymous RECORD types — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120141 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in materialized set-returning functions — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-120139 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via integer wraparound in tuple-size calculations — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116336 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via dropped index in REINDEX CONCURRENTLY — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116335 | libpq | 18.6-r0 | 18.7-r0 | postgresql: PostgreSQL: Arbitrary code execution via operator link type confusion — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116332 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free during portal setup — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116331 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via aggregate optimization type confusion — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116330 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via predictable restriction key in pg_dump restore script — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116329 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: arbitrary code execution via nested SET DATA TYPE during statistics import — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116328 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via integer wraparound in memory contexts — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116326 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via uncaught exceptions in PL/Perl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116325 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary SQL execution in reindexdb via crafted index name — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116306 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via composite-value field assignment type confusion — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116307 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via use-after-free in plperl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116309 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in PL/Perl — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-6467 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Privilege escalation via uncontrolled search path in extension management — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-6460 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in data definition commands — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-18447 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via type confusion in SQL-language functions — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-14661 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Persistent Denial of Service via arbitrary file append in sslkeylogfile parameter — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116313 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Privilege escalation via untrusted search path in vacuumdb — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116314 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via crafted archive in pg_restore — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116315 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Arbitrary code execution via heap-based buffer overflow in tsvector_delete() — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| HIGH | CVE-2026-116316 | libpq | 18.6-r0 | 18.7-r0 | postgresql: PostgreSQL: Privilege escalation via unqualified type resolution in temporary schema — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-107496 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-16237 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Security restriction bypass via INSERT ON CONFLICT on auto-updatable views — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-120154 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: PostgreSQL: Row-level security bypass via INSERT ON CONFLICT DO UPDATE — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-120152 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Information disclosure via use-after-free in pg_show_all_settings() — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-120146 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: PostgreSQL: Authorization bypass via REASSIGN OWNED command — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116333 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Information disclosure via buffer over-read in parallel B-tree scans — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116327 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Information disclosure via security barrier view bypass — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116322 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Denial of Service via improper locking during startup processing — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116321 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: server memory disclosure via improper null termination in array element assignment — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116312 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Incorrect trigger row processing via partitioned table MERGE — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116311 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: row-level security bypass via DROP OWNED — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116310 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Information disclosure via use-after-free in COPY FROM error reporting — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116308 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Information disclosure via zero-length token in dict_int — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-95691 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-95692 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116310 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Information disclosure via use-after-free in COPY FROM error reporting — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116311 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: row-level security bypass via DROP OWNED — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116312 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Incorrect trigger row processing via partitioned table MERGE — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116321 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: server memory disclosure via improper null termination in array element assignment — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116322 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Denial of Service via improper locking during startup processing — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116327 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Information disclosure via security barrier view bypass — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116333 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Information disclosure via buffer over-read in parallel B-tree scans — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-120146 | libpq | 18.6-r0 | 18.7-r0 | postgresql: PostgreSQL: Authorization bypass via REASSIGN OWNED command — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-120152 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Information disclosure via use-after-free in pg_show_all_settings() — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-120154 | libpq | 18.6-r0 | 18.7-r0 | postgresql: PostgreSQL: Row-level security bypass via INSERT ON CONFLICT DO UPDATE — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-16237 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Security restriction bypass via INSERT ON CONFLICT on auto-updatable views — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-107496 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-95691 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-95692 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-95692 | openssl | 3.5.9-r0 | 3.5.9-r1 | openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-95691 | openssl | 3.5.9-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-116308 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Information disclosure via zero-length token in dict_int — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-114943 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | OpenJDK: OpenJDK: Enhance JFR Events — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-114944 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | OpenJDK: OpenJDK: Enhance JMX Connections — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-114945 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | OpenJDK: OpenJDK: Enhance StringBuilder checks — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-114946 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | OpenJDK: OpenJDK: Enhance loop handling — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| MEDIUM | CVE-2026-107496 | openssl | 3.5.9-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-88823 | openssl | 3.5.9-r0 | 3.5.9-r1 | openssl: OpenSSL: Message authentication bypass via zero-length AAD update — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-16240 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: postgresql: Information disclosure in pg_basebackup via crafted backup manifest — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-116303 | postgresql17-client | 17.11-r0 | 17.12-r0 | postgresql: PostgreSQL: Unauthorized execution of restricted cast functions via type conversion operations — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-88822 | openssl | 3.5.9-r0 | 3.5.9-r1 | openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-88823 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | openssl: OpenSSL: Message authentication bypass via zero-length AAD update — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-116303 | libpq | 18.6-r0 | 18.7-r0 | postgresql: PostgreSQL: Unauthorized execution of restricted cast functions via type conversion operations — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-16240 | libpq | 18.6-r0 | 18.7-r0 | postgresql: postgresql: Information disclosure in pg_basebackup via crafted backup manifest — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-88822 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-88822 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
| LOW | CVE-2026-88823 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | openssl: OpenSSL: Message authentication bypass via zero-length AAD update — ghcr.io/openvoxproject/openvoxdb:latest-alpine (alpine 3.24.4) |
Grype
HIGH 94
MEDIUM 31
LOW 5
NVD/CPE filtered 41
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-114942 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116313 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116313 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120148 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120148 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116316 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116316 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120153 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120153 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116314 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116314 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120145 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120145 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-6467 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-6467 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120150 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120150 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116329 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116328 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116323 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116329 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116328 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116323 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-18447 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-114941 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-88823 | openssl | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-88823 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-88823 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95691 | openssl | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95691 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95691 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-114940 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-114939 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107496 | openssl | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-107496 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-107496 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-116325 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116325 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116330 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116330 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-95692 | openssl | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95692 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95692 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-14661 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-14661 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116318 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116318 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116304 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120139 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116335 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116307 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120151 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120141 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116309 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120151 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120141 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116309 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116319 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116319 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120149 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116317 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116315 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120149 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116317 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116315 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116336 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116336 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116326 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116326 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-114938 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | /lib/apk/db/installed |
| HIGH | GHSA-jr6h-r7vg-f9mc | ini4j | 0.5.4 | org.ini4j allows attackers to cause a Denial of Service (DoS) — /opt/puppetlabs/server/apps/puppetdb/puppetdb.jar | |
| HIGH | CVE-2026-18447 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116304 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120147 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120142 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116320 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116306 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120147 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120142 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116320 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116306 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-6460 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120144 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116307 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116335 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120139 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120144 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116331 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116332 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120143 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-6460 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116331 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-116332 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-120143 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116308 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-120152 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-120154 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-120152 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-120154 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116312 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116312 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116311 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116311 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-120146 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-120146 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114944 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114945 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116327 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116327 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114946 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116333 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116333 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116322 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116322 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-88822 | libcrypto3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-88822 | libssl3 | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-88822 | openssl | 3.5.9-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-16237 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-16237 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114943 | openjdk21-jre-headless | 21.0.13.0.3_p1-r0 | 21.0.13.1_p2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116310 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116321 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116310 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116321 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-116308 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| LOW | GHSA-x2f5-4prf-w687 | json | 2.9.1 | 2.19.9 | Ruby json: JSON generator heap buffer overflow when streaming to an IO — /usr/lib/ruby/gems/3.4.0/specifications/default/json-2.9.1.gemspec |
| LOW | CVE-2026-16240 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-16240 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-116303 | libpq | 18.6-r0 | 18.7-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-116303 | postgresql17-client | 17.11-r0 | 17.12-r0 | /lib/apk/db/installed |
Filtered NVD/CPE matches (41)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-107493 | openssl | 3.5.9-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libssl3 | 3.5.9-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.9-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | openssl | 3.5.9-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.9-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.9-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-132825 | ruby-libs | 3.4.12-r0 | Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. — /lib/apk/db/installed | |
| HIGH | CVE-2026-132825 | ruby | 3.4.12-r0 | Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | openssl | 3.5.9-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.9-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.9-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.9-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.9-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | openssl | 3.5.9-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.9-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.9-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | openssl | 3.5.9-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.9-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | openssl | 3.5.9-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56392 | coreutils | 9.11-r0 | GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write. When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout. This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56392 | coreutils-env | 9.11-r0 | GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write. When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout. This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56392 | coreutils-fmt | 9.11-r0 | GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write. When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout. This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56392 | coreutils-sha512sum | 9.11-r0 | GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write. When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout. This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56391 | coreutils | 9.11-r0 | GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input. When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure. This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56391 | coreutils-env | 9.11-r0 | GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input. When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure. This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56391 | coreutils-fmt | 9.11-r0 | GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input. When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure. This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56391 | coreutils-sha512sum | 9.11-r0 | GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input. When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure. This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-18508 | tar | 1.35-r5 | A flaw was found in GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside that boundary during a single extraction. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-18477 | tar | 1.35-r5 | A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.9-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-5704 | tar | 1.35-r5 | A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection. — /lib/apk/db/installed | |
| MEDIUM | CVE-2016-2781 | coreutils | 9.11-r0 | chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | openssl | 3.5.9-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.9-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.9-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2016-2781 | coreutils-env | 9.11-r0 | chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. — /lib/apk/db/installed | |
| MEDIUM | CVE-2016-2781 | coreutils-fmt | 9.11-r0 | chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. — /lib/apk/db/installed | |
| MEDIUM | CVE-2016-2781 | coreutils-sha512sum | 9.11-r0 | chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. — /lib/apk/db/installed |
ghcr.io/openvoxproject/openvoxserver
Downloads
ghcr.io/openvoxproject/openvoxserver:latest (2026-11-21)
Trivy
CRITICAL 3
HIGH 28
MEDIUM 152
LOW 72
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-99287 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: xen-netback: Denial of Service via double unmapping of shared data rings — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| CRITICAL | CVE-2026-99306 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: ceph: Denial of Service via crafted MDS map — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| CRITICAL | CVE-2026-99310 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via use-after-free in nfsd — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2022-50240 | linux-libc-dev | 7.0.0-44.44 | kernel: binder: fix UAF of alloc->vma in race with munmap() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2025-40190 | linux-libc-dev | 7.0.0-44.44 | kernel: ext4: guard against EA inode refcount underflow in xattr update — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-100081 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: xen-netback: Denial of Service via race condition during interface disconnect — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-68103 | linux-libc-dev | 7.0.0-44.44 | kernel: drm/amdgpu: reject mapping a reserved doorbell to a new queue — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-72198 | linux-libc-dev | 7.0.0-44.44 | kernel: ntfs: reject non-resident records for resident-only attributes — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-74578 | linux-libc-dev | 7.0.0-44.44 | kernel: crypto: algif_skcipher - force synchronous processing on trees without ctx->state — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-89805 | linux-libc-dev | 7.0.0-44.44 | kernel: drm/pagemap: Fix folio allocation fallback and use-after-put — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-98376 | linux-libc-dev | 7.0.0-44.44 | kernel: bpf: Use array_map_meta_equal for percpu array inner map replacement — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-98420 | linux-libc-dev | 7.0.0-44.44 | kernel: ksmbd: follow SMB2 session expiration semantics — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-98869 | linux-libc-dev | 7.0.0-44.44 | kernel: bpf: Infer zext_dst based on static register liveness analysis — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-98890 | linux-libc-dev | 7.0.0-44.44 | kernel: wifi: libertas: reject short monitor TX frames — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99239 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Privilege escalation via race condition in Bluetooth L2CAP — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99260 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via improper attribute conversion in NTFS — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99270 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via use-after-free in TCP socket migration — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99272 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: out-of-bounds read in SMB client via crafted read response — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99274 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of service via empty truncated responses in SMB client — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99275 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Information disclosure via crafted SMB session setup responses — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99282 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via use-after-free in sch_teql — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99288 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via race condition in TCP socket lookup — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99290 | linux-libc-dev | 7.0.0-44.44 | kernel: ksmbd: Denial of Service via use-after-free during durable handle reconnect — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99292 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via out-of-bounds write in SMB client — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99295 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of service via use-after-free during SMB read error handling — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99302 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via truncated RDMA connection requests — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99304 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via integer overflow in Ceph snap trace bounds check — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99311 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via corrupted UDF filesystem symlink — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99312 | linux-libc-dev | 7.0.0-44.44 | kernel: KVM: SVM: use-after-free of nested page table pointer on AMD INIT reset — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2026-99317 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via race condition in ALSA hwdep DSP loader — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| HIGH | CVE-2022-41404 | org.ini4j:ini4j | 0.5.4 | org.ini4j: unspecified DoS — Java | |
| MEDIUM | CVE-2023-0030 | linux-libc-dev | 7.0.0-44.44 | kernel: Use after Free in nvkm_vmm_pfn_map — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-50551 | linux-libc-dev | 7.0.0-44.44 | kernel: wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2023-0160 | linux-libc-dev | 7.0.0-44.44 | kernel: possibility of deadlock in libbpf function sock_hash_delete_elem — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2023-1193 | linux-libc-dev | 7.0.0-44.44 | kernel: use-after-free in setup_async_work() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-50380 | linux-libc-dev | 7.0.0-44.44 | kernel: mm: /proc/pid/smaps_rollup: fix no vma's null-deref — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-50090 | linux-libc-dev | 7.0.0-44.44 | kernel: btrfs: replace BTRFS_MAX_EXTENT_SIZE with fs_info->max_extent_size — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-49940 | linux-libc-dev | 7.0.0-44.44 | kernel: tty: n_gsm: add sanity check for gsm->receive in gsm_receive_buf() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2023-26242 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: fpga: dfl-afu: integer overflow in afu_mmio_region_get_by_offset() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2023-31082 | linux-libc-dev | 7.0.0-44.44 | kernel: sleeping function called from an invalid context in gsmld_write — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2023-53642 | linux-libc-dev | 7.0.0-44.44 | kernel: x86: fix clear_user_rep_good() exception handling annotation — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2023-54187 | linux-libc-dev | 7.0.0-44.44 | kernel: Linux kernel (F2FS): Data corruption and denial of service when moving a directory — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2024-35895 | linux-libc-dev | 7.0.0-44.44 | kernel: bpf, sockmap: Prevent lock inversion deadlock in map delete elem — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2024-53216 | linux-libc-dev | 7.0.0-44.44 | kernel: nfsd: release svc_expkey/svc_export with rcu_work — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-100080 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: xen-netback: Denial of Service via use-after-free during queue teardown — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-4543 | linux-libc-dev | 7.0.0-44.44 | kernel: KASLR Prefetch Bypass Breaks KPTI — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-3238 | linux-libc-dev | 7.0.0-44.44 | kernel: ntfs3 local privledge escalation if NTFS character set and remount and umount called simultaneously — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-2961 | linux-libc-dev | 7.0.0-44.44 | kernel: race condition in rose_bind() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-25836 | linux-libc-dev | 7.0.0-44.44 | Bluetooth® Low Energy Pairing in Bluetooth Core Specification v4. ... — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-1247 | linux-libc-dev | 7.0.0-44.44 | kernel: A race condition bug in rose_connect() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-0480 | linux-libc-dev | 7.0.0-44.44 | kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2022-0400 | linux-libc-dev | 7.0.0-44.44 | kernel: Out of bounds read in the smc protocol stack — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2021-3864 | linux-libc-dev | 7.0.0-44.44 | kernel: descendant's dumpable setting with certain SUID binaries — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2021-3714 | linux-libc-dev | 7.0.0-44.44 | kernel: Remote Page Deduplication Attacks — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2019-15794 | linux-libc-dev | 7.0.0-44.44 | kernel: Overlayfs in the Linux kernel and shiftfs not restoring original value on error leading to a refcount underflow — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2018-17977 | linux-libc-dev | 7.0.0-44.44 | kernel: Mishandled interactions among XFRM Netlink messages, IPPROTO_AH packets, and IPPROTO_IP packets resulting in a denial of service — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2016-8660 | linux-libc-dev | 7.0.0-44.44 | kernel: xfs: local DoS due to a page lock order bug in the XFS seek hole/data implementation — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2015-7837 | linux-libc-dev | 7.0.0-44.44 | kernel: securelevel disabled after kexec — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99315 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via NULL pointer dereference in ALSA US122L driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99316 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via null pointer dereference in ALSA usx2y driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | mount | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | mount | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | mount | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-83357 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | Vulnerability in the Oracle GraalVM for JDK, Oracle GraalVM produ ... — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-83368 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | Vulnerability in the Oracle GraalVM for JDK, Oracle GraalVM Enter ... — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-83408 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | Vulnerability in the Oracle GraalVM for JDK, Oracle GraalVM produ ... — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-110928 | openssh-client | 1:10.2p1-2ubuntu3.8 | openssh: openssh: authorized_keys restrict does not apply to tunnel forwarding — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-48962 | perl | 5.40.1-7ubuntu0.4 | perl-IO-Compress: perl-IO-Compress: Arbitrary code execution via attacker-controlled output glob — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-9538 | perl | 5.40.1-7ubuntu0.4 | perl-Archive-Tar: perl-Archive-Tar: Denial of Service via crafted tar header with large entry size — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-48962 | perl-base | 5.40.1-7ubuntu0.4 | perl-IO-Compress: perl-IO-Compress: Arbitrary code execution via attacker-controlled output glob — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-9538 | perl-base | 5.40.1-7ubuntu0.4 | perl-Archive-Tar: perl-Archive-Tar: Denial of Service via crafted tar header with large entry size — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-48962 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | perl-IO-Compress: perl-IO-Compress: Arbitrary code execution via attacker-controlled output glob — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-9538 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | perl-Archive-Tar: perl-Archive-Tar: Denial of Service via crafted tar header with large entry size — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2025-10990 | ruby3.3 | 3.3.8-2ubuntu3.2 | rexml: REXML: Denial of Service via inefficient regex parsing — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2025-10990 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | rexml: REXML: Denial of Service via inefficient regex parsing — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-35370 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | The id utility in uutils coreutils miscalculates the groups= section o ... — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-35371 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | The id utility in uutils coreutils exhibits incorrect behavior in its ... — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-18477 | tar | 1.35+dfsg-4ubuntu0.4 | tar: tar: TOCTOU in incremental dumpdir 'X' rename handling allows restore path escape — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-18508 | tar | 1.35+dfsg-4ubuntu0.4 | tar: tar: --one-top-level hardlink targets not confined to top-level directory enabling arbitrary file overwrite — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | util-linux | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | util-linux | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | util-linux | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-97054 | stdlib | v1.27.3 | 1.26.11, 1.27.4 | net/http: golang: net/http: Denial of Service via race condition when handling oversized HTTP/1 requests — usr/bin/pebble |
| MEDIUM | CVE-2026-64190 | linux-libc-dev | 7.0.0-44.44 | kernel: net: team: fix NULL pointer dereference in team_xmit during mode change — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-72094 | linux-libc-dev | 7.0.0-44.44 | kernel: dma-buf: dma-fence: Fix potential NULL pointer dereference — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-72200 | linux-libc-dev | 7.0.0-44.44 | kernel: ntfs: detect mapping-pairs LCN accumulator overflow — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-72203 | linux-libc-dev | 7.0.0-44.44 | kernel: ntfs: skip extent mft records in writeback to prevent deadlock — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-74342 | linux-libc-dev | 7.0.0-44.44 | kernel: kernfs: link kn to its parent before the LSM init hook — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-89517 | linux-libc-dev | 7.0.0-44.44 | kernel: sched_ext: Fix rq->core_pick corruption under core scheduling — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-89518 | linux-libc-dev | 7.0.0-44.44 | kernel: sched_ext: Fix this_rq() assumptions in dispatch kfuncs — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-89519 | linux-libc-dev | 7.0.0-44.44 | kernel: sched_ext: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-90098 | linux-libc-dev | 7.0.0-44.44 | kernel: net: sparx5: fix sleep in atomic context in MAC table access — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-93180 | linux-libc-dev | 7.0.0-44.44 | kernel: drm/panthor: Fix NPD issue on partial unmap of an evicted BO — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-98144 | linux-libc-dev | 7.0.0-44.44 | kernel: accel/amdxdna: put the chained BO when its mapping fails — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99101 | linux-libc-dev | 7.0.0-44.44 | kernel: ntfs: move attribute payload before shrinking its record — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99271 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of service via use-after-free in ALSA Line 6 audio driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99273 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: ksmbd: Denial of Service via out-of-bounds write in get_file_stream_info() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99281 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Unauthorized network device access via missing permission checks on ownerless TUN/TAP devices — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99283 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via premature connection tracking expiration on TCP RST packets — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99293 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via copy buffer exhaustion in FUSE — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99296 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via truncated monitor replies in libceph — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99297 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via double-free in em28xx media driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99298 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via division by zero in IPv4 route metrics — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99299 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: em28xx: Denial of Service via zero-sized audio endpoint — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99300 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via null pointer dereference in go7007 driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99303 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via null pointer dereference in Speakup driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99305 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via use-after-free in udlfb driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99307 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: ceph: Denial of Service via out-of-bounds read during lease parsing — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99308 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Buffer overflow in xHCI driver via crafted USB endpoint descriptors — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99309 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: ksmbd: out-of-bounds read via DACL offset integer overflow — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-99314 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via NULL pointer dereference in ALSA US122L driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-3441 | binutils | 2.46-3ubuntu2 | binutils: GNU Binutils: Information disclosure via specially crafted XCOFF object file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libblkid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | libblkid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-3441 | libctf-nobfd0 | 2.46-3ubuntu2 | binutils: GNU Binutils: Information disclosure via specially crafted XCOFF object file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-4647 | libctf-nobfd0 | 2.46-3ubuntu2 | binutils: Out-of-Bounds Read in XCOFF Relocation Processing in GNU Binutils BFD Library — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-6845 | libctf-nobfd0 | 2.46-3ubuntu2 | binutils: Binutils: Denial of Service via crafted ELF file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-3441 | libctf0 | 2.46-3ubuntu2 | binutils: GNU Binutils: Information disclosure via specially crafted XCOFF object file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-4647 | libctf0 | 2.46-3ubuntu2 | binutils: Out-of-Bounds Read in XCOFF Relocation Processing in GNU Binutils BFD Library — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-6845 | libctf0 | 2.46-3ubuntu2 | binutils: Binutils: Denial of Service via crafted ELF file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2025-66382 | libexpat1 | 2.7.4-1ubuntu0.2 | libexpat: libexpat: Denial of service via crafted file processing — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-102633 | libexpat1 | 2.7.4-1ubuntu0.2 | expat: expat: Denial of Service via integer overflow in expat_realloc — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-77214 | libexpat1 | 2.7.4-1ubuntu0.2 | expat: expat: Information disclosure via heap buffer over-read in XML_ParseBuffer — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-93990 | libexpat1 | 2.7.4-1ubuntu0.2 | expat: Expat: XML Injection via Malformed UTF-16 Input — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-67693 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: Information disclosure via contradictory Key Usage and Extended Key Usage extensions — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-88647 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: Information disclosure via hostname verification bypass — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-88648 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: Cross-domain certificate restriction bypass via incomplete X.509 validation — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-95184 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: legitimate user certificates incorrectly rejected causing denial of service — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-95210 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | gnutls: gnutls: certificates with invalid extensions incorrectly accepted — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-3441 | libgprofng0 | 2.46-3ubuntu2 | binutils: GNU Binutils: Information disclosure via specially crafted XCOFF object file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-4647 | libgprofng0 | 2.46-3ubuntu2 | binutils: Out-of-Bounds Read in XCOFF Relocation Processing in GNU Binutils BFD Library — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-4647 | binutils | 2.46-3ubuntu2 | binutils: Out-of-Bounds Read in XCOFF Relocation Processing in GNU Binutils BFD Library — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-6845 | binutils | 2.46-3ubuntu2 | binutils: Binutils: Denial of Service via crafted ELF file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-3441 | binutils-common | 2.46-3ubuntu2 | binutils: GNU Binutils: Information disclosure via specially crafted XCOFF object file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-4647 | binutils-common | 2.46-3ubuntu2 | binutils: Out-of-Bounds Read in XCOFF Relocation Processing in GNU Binutils BFD Library — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-6845 | binutils-common | 2.46-3ubuntu2 | binutils: Binutils: Denial of Service via crafted ELF file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-3441 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | binutils: GNU Binutils: Information disclosure via specially crafted XCOFF object file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-4647 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | binutils: Out-of-Bounds Read in XCOFF Relocation Processing in GNU Binutils BFD Library — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-6845 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | binutils: Binutils: Denial of Service via crafted ELF file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | bsdutils | 1:2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | bsdutils | 1:2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | bsdutils | 1:2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-102473 | dash | 0.5.12-12ubuntu3 | dash: dash: Super-polynomial backtracking in pmatch when libc fnmatch is disabled — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-102474 | dash | 0.5.12-12ubuntu3 | dash: dash: Heap out-of-bounds write in conv_escape via undersized Unicode escape reservation — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2024-52005 | git | 1:2.53.0-1ubuntu1.1 | git: The sideband payload is passed unfiltered to the terminal in git — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2024-52005 | git-man | 1:2.53.0-1ubuntu1.1 | git: The sideband payload is passed unfiltered to the terminal in git — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-3441 | libbinutils | 2.46-3ubuntu2 | binutils: GNU Binutils: Information disclosure via specially crafted XCOFF object file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-4647 | libbinutils | 2.46-3ubuntu2 | binutils: Out-of-Bounds Read in XCOFF Relocation Processing in GNU Binutils BFD Library — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-6845 | libbinutils | 2.46-3ubuntu2 | binutils: Binutils: Denial of Service via crafted ELF file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libblkid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-48962 | libperl5.40 | 5.40.1-7ubuntu0.4 | perl-IO-Compress: perl-IO-Compress: Arbitrary code execution via attacker-controlled output glob — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-9538 | libperl5.40 | 5.40.1-7ubuntu0.4 | perl-Archive-Tar: perl-Archive-Tar: Denial of Service via crafted tar header with large entry size — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2025-10990 | libruby3.3 | 3.3.8-2ubuntu3.2 | rexml: REXML: Denial of Service via inefficient regex parsing — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107161 | libsasl2-2 | 2.1.28+dfsg1-9ubuntu3 | cyrus-sasl: Heap buffer overflow in cyrus-sasl add_to_challenge() allows malicious server to crash or compromise DIGEST-MD5 clients — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107161 | libsasl2-modules-db | 2.1.28+dfsg1-9ubuntu3 | cyrus-sasl: Heap buffer overflow in cyrus-sasl add_to_challenge() allows malicious server to crash or compromise DIGEST-MD5 clients — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-3441 | libsframe3 | 2.46-3ubuntu2 | binutils: GNU Binutils: Information disclosure via specially crafted XCOFF object file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-4647 | libsframe3 | 2.46-3ubuntu2 | binutils: Out-of-Bounds Read in XCOFF Relocation Processing in GNU Binutils BFD Library — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-6845 | libsframe3 | 2.46-3ubuntu2 | binutils: Binutils: Denial of Service via crafted ELF file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libsmartcols1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libsmartcols1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | libsmartcols1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-121876 | libsystemd0 | 259.9-0ubuntu0.1 | sandboxed-containers: kernel: systemd-gpt-auto-generator: Guest Data Leakage in Confidential Computing (Sandboxed Containers) — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-121876 | libudev1 | 259.9-0ubuntu0.1 | sandboxed-containers: kernel: systemd-gpt-auto-generator: Guest Data Leakage in Confidential Computing (Sandboxed Containers) — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libuuid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libuuid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | libuuid1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2013-7445 | linux-libc-dev | 7.0.0-44.44 | kernel: memory exhaustion via crafted Graphics Execution Manager (GEM) objects — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-6845 | libgprofng0 | 2.46-3ubuntu2 | binutils: Binutils: Denial of Service via crafted ELF file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107708 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via malformed PAC in S4U2Proxy requests — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107778 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via crafted forwarded credentials — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107708 | libk5crypto3 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via malformed PAC in S4U2Proxy requests — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107778 | libk5crypto3 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via crafted forwarded credentials — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107708 | libkrb5-3 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via malformed PAC in S4U2Proxy requests — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107778 | libkrb5-3 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via crafted forwarded credentials — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107708 | libkrb5support0 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via malformed PAC in S4U2Proxy requests — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-107778 | libkrb5support0 | 1.22.1-2ubuntu4.1 | krb5: krb5: Denial of Service via crafted forwarded credentials — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-76642 | libmount1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78408 | libmount1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-13757 | libp11-kit0 | 0.26.2-2 | p11-kit: Stack exhaustion via unbounded recursion in RPC attribute parsing — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| MEDIUM | CVE-2026-78410 | libmount1 | 2.41.3-3ubuntu2.2 | util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-66863 | libgprofng0 | 2.46-3ubuntu2 | binutils: BinUtils: Denial of Service via crafted PE file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-66863 | libsframe3 | 2.46-3ubuntu2 | binutils: BinUtils: Denial of Service via crafted PE file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2018-12929 | linux-libc-dev | 7.0.0-44.44 | kernel: use-after-free in ntfs_read_locked_inode in the ntfs.ko — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2018-12930 | linux-libc-dev | 7.0.0-44.44 | kernel: stack-based out-of-bounds write in ntfs_end_buffer_async_read in the ntfs.ko — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-56289 | patch | 2.8-2build1 | patch: GNU patch: Denial of Service via crafted unified-diff input — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-56288 | patch | 2.8-2build1 | patch: GNU patch: Denial of Service via specially crafted patch file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2021-45261 | patch | 2.8-2build1 | patch: Invalid Pointer via another_hunk function — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2024-56433 | passwd | 1:4.17.4-2ubuntu3 | shadow-utils: Default subordinate ID configuration in /etc/login.defs could lead to compromise — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-66863 | libctf0 | 2.46-3ubuntu2 | binutils: BinUtils: Denial of Service via crafted PE file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2018-12931 | linux-libc-dev | 7.0.0-44.44 | kernel: stack-based out-of-bounds write in ntfs_attr_find in the ntfs.ko — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-105712 | gpgv | 2.4.8-4ubuntu3.1 | gnupg2: gnupg: Arbitrary file overwrite via symlink traversal in gpgtar — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2019-14899 | linux-libc-dev | 7.0.0-44.44 | VPN: an attacker can inject data into the TCP stream which allows a hijack of active connections inside the VPN tunnel — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-61594 | libruby3.3 | 3.3.8-2ubuntu3.2 | uri: URI module: Credential exposure via URI + operator — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-58767 | libruby3.3 | 3.3.8-2ubuntu3.2 | rexml: REXML denial of service — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-66863 | libbinutils | 2.46-3ubuntu2 | binutils: BinUtils: Denial of Service via crafted PE file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2024-56433 | login.defs | 1:4.17.4-2ubuntu3 | shadow-utils: Default subordinate ID configuration in /etc/login.defs could lead to compromise — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-43857 | libruby3.3 | 3.3.8-2ubuntu3.2 | net-imap: net-imap rubygem vulnerable to possible DoS by memory exhaustion — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2019-15213 | linux-libc-dev | 7.0.0-44.44 | kernel: use-after-free caused by malicious USB device in drivers/media/usb/dvb-usb/dvb-usb-init.c — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-66863 | binutils | 2.46-3ubuntu2 | binutils: BinUtils: Denial of Service via crafted PE file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2017-0537 | linux-libc-dev | 7.0.0-44.44 | ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-40228 | libudev1 | 259.9-0ubuntu0.1 | systemd: systemd-journald: Unintended output to user terminals via logger command — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2017-13165 | linux-libc-dev | 7.0.0-44.44 | ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-66863 | binutils-common | 2.46-3ubuntu2 | binutils: BinUtils: Denial of Service via crafted PE file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-40228 | libsystemd0 | 259.9-0ubuntu0.1 | systemd: systemd-journald: Unintended output to user terminals via logger command — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-61594 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | uri: URI module: Credential exposure via URI + operator — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-58767 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | rexml: REXML denial of service — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-43857 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | net-imap: net-imap rubygem vulnerable to possible DoS by memory exhaustion — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2018-10126 | libjpeg-turbo8 | 2.1.5-4ubuntu4 | libtiff: NULL pointer dereference in the jpeg_fdct_16x16 function in jfdctint.c — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-61594 | ruby3.3 | 3.3.8-2ubuntu3.2 | uri: URI module: Credential exposure via URI + operator — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-58767 | ruby3.3 | 3.3.8-2ubuntu3.2 | rexml: REXML denial of service — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-43857 | ruby3.3 | 3.3.8-2ubuntu3.2 | net-imap: net-imap rubygem vulnerable to possible DoS by memory exhaustion — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2017-13693 | linux-libc-dev | 7.0.0-44.44 | kernel: ACPI operand cache leak in dsutils.c — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-66863 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | binutils: BinUtils: Denial of Service via crafted PE file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2018-1121 | linux-libc-dev | 7.0.0-44.44 | procps: process hiding through race condition enumerating /proc — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2018-12928 | linux-libc-dev | 7.0.0-44.44 | kernel: NULL pointer dereference in hfs_ext_read_extent in hfs.ko — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2025-66863 | libctf-nobfd0 | 2.46-3ubuntu2 | binutils: BinUtils: Denial of Service via crafted PE file — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2023-6238 | linux-libc-dev | 7.0.0-44.44 | kernel: nvme: memory corruption via unprivileged user passthrough — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2023-54190 | linux-libc-dev | 7.0.0-44.44 | kernel: Kernel: Denial of Service via reference count leak in LED core — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2023-54105 | linux-libc-dev | 7.0.0-44.44 | kernel: can: isotp: check CAN address family in isotp_bind() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2023-52879 | linux-libc-dev | 7.0.0-44.44 | kernel: tracing: Have trace_event_file have ref counters — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2023-33053 | linux-libc-dev | 7.0.0-44.44 | ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2022-50232 | linux-libc-dev | 7.0.0-44.44 | kernel: arm64: set UXN on swapper page tables — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2022-50230 | linux-libc-dev | 7.0.0-44.44 | kernel: arm64: set UXN on swapper page tables — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2022-48929 | linux-libc-dev | 7.0.0-44.44 | kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2022-48846 | linux-libc-dev | 7.0.0-44.44 | kernel: block: release rq qos structures for queue without disk — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2022-45885 | linux-libc-dev | 7.0.0-44.44 | kernel: use-after-free due to race condition occurring in dvb_frontend.c — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2022-44034 | linux-libc-dev | 7.0.0-44.44 | Kernel: A use-after-free due to race between scr24x_open() and scr24x_remove() — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2022-41848 | linux-libc-dev | 7.0.0-44.44 | kernel: Race condition between mgslpc_ioctl and mgslpc_detach — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2021-26934 | linux-libc-dev | 7.0.0-44.44 | An issue was discovered in the Linux kernel 4.18 through 5.10.16, as u ... — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2020-35501 | linux-libc-dev | 7.0.0-44.44 | kernel: audit not logging access to syscall open_by_handle_at for users with CAP_DAC_READ_SEARCH capability — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2020-14304 | linux-libc-dev | 7.0.0-44.44 | kernel: ethtool when reading eeprom of device could lead to memory leak — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2019-20426 | linux-libc-dev | 7.0.0-44.44 | ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2019-19814 | linux-libc-dev | 7.0.0-44.44 | kernel: out-of-bounds write in __remove_dirty_segment in fs/f2fs/segment.c — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2019-19378 | linux-libc-dev | 7.0.0-44.44 | kernel: out-of-bounds write in index_rbio_pages in fs/btrfs/raid56.c — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-99319 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of service via retried DSP firmware load in ALSA usx2y driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-99318 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via use-after-free in ALSA BCD2000 driver — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-99301 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: virtio_net: Denial of Service via use-after-free race condition — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-99240 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via division by zero in DAMON subsystem — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-98941 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via large folios on encrypted ext4 files — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-98938 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: Denial of Service via uninitialized memory read in Rust IRQ registration — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-98815 | linux-libc-dev | 7.0.0-44.44 | kernel: nvme: fix cdev lifetime — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-97949 | linux-libc-dev | 7.0.0-44.44 | kernel: configfs: unhash the dentry before dropping the item in rmdir — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-89772 | linux-libc-dev | 7.0.0-44.44 | kernel: btrfs: write-protect folios during data writeback — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-80608 | linux-libc-dev | 7.0.0-44.44 | kernel: accel/amdxdna: Fix iommu domain lifetime race during device removal — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-72344 | linux-libc-dev | 7.0.0-44.44 | kernel: net/mlx5e: TC, skip peer flow cleanup when LAG seq is unavailable — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-68102 | linux-libc-dev | 7.0.0-44.44 | kernel: drm/amdgpu: fix aperture mapping leak — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-68086 | linux-libc-dev | 7.0.0-44.44 | kernel: mm/khugepaged: write all dirty file folios when collapsing — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-46055 | linux-libc-dev | 7.0.0-44.44 | kernel: apparmor: Fix string overrun due to missing termination — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2026-100082 | linux-libc-dev | 7.0.0-44.44 | kernel: kernel: xen-blkback: Denial of Service via race condition reading I/O statistics — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2024-56568 | linux-libc-dev | 7.0.0-44.44 | kernel: iommu/arm-smmu: Defer probe of clients after smmu device bound — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2024-35995 | linux-libc-dev | 7.0.0-44.44 | kernel: ACPI: CPPC: Use access_width over bit_width for system memory accesses — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) | |
| LOW | CVE-2024-0564 | linux-libc-dev | 7.0.0-44.44 | kernel: max page sharing of Kernel Samepage Merging (KSM) may cause memory deduplication — ghcr.io/openvoxproject/openvoxserver:latest (ubuntu 26.04) |
Grype
HIGH 2
MEDIUM 518
LOW 69
UNKNOWN 4
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | GHSA-jr6h-r7vg-f9mc | ini4j | 0.5.4 | org.ini4j allows attackers to cause a Denial of Service (DoS) — /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar | |
| HIGH | GHSA-q339-8rmv-2mhv | erb | 4.0.3 | 4.0.3.1 | ERB has an @_init deserialization guard bypass via def_module / def_method / def_class — /usr/lib/ruby/gems/3.3.0/specifications/default/erb-4.0.3.gemspec |
| MEDIUM | CVE-2026-78409 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115207 | patch | 2.8-2build1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90802 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90802 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90802 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90802 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90802 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90802 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90802 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90802 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119376 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6846 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6846 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6846 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6846 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6846 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-4647 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-4647 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-4647 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-4647 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-4647 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-4647 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-4647 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119371 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-132825 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-132825 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-132825 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78409 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91781 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91781 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91781 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91780 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91780 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91780 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91780 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91780 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91780 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91780 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91780 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-84786 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119591 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90828 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6846 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6846 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6846 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112060 | librtmp1 | 2.4+20151223.gitfa8646d.1-3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91782 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91782 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91782 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91782 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91782 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91782 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91782 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91782 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91781 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91781 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91781 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91781 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91781 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-87293 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-3441 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-3441 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-3441 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-3441 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-3441 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-3441 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-3441 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-3441 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95184 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90801 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90801 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90801 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90801 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90801 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90801 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114466 | git | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114466 | git-man | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119374 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-127231 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112061 | librtmp1 | 2.4+20151223.gitfa8646d.1-3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114467 | git | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114467 | git-man | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-66382 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-76642 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | mount | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | util-linux | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90804 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90804 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90804 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90804 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90804 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90804 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90804 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90804 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119375 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-4647 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90801 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90801 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35190 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88648 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90803 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90803 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90803 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90803 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90803 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90803 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90803 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90803 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95210 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78410 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119377 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35371 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-15649 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-15649 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-15649 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-15649 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100407 | git | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100408 | git | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100407 | git-man | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100408 | git-man | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-102474 | dash | 0.5.12-12ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-128241 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-35370 | rust-coreutils | 0.10.0-1ubuntu2~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91484 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18938 | libp11-kit0 | 0.26.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6844 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6844 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6845 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6845 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119372 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107493 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107493 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107493 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107493 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | GHSA-46q3-7gv7-qmgg | net-imap | 0.4.19 | 0.5.15 | Net::IMAP: Command Injection via ID command argument — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| MEDIUM | CVE-2026-18508 | tar | 1.35+dfsg-4ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114690 | cpp | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114690 | cpp-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114690 | gcc | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114690 | gcc-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47242 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47242 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47242 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-56391 | coreutils | 9.5-1ubuntu2+0.0.0~ubuntu25 | 9.7-3ubuntu2.1 | /var/lib/dpkg/status |
| MEDIUM | CVE-2026-111423 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-118380 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71199 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71200 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107364 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107884 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-111423 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-118380 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71199 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71200 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107364 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107884 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-111423 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-118380 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71199 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71200 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-110928 | openssh-client | 1:10.2p1-2ubuntu3.8 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6844 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6844 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6844 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6844 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6844 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6844 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-18477 | tar | 1.35+dfsg-4ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-102473 | dash | 0.5.12-12ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-54370 | libacl1 | 2.3.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107364 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107884 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-111423 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-118380 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71199 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-71200 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107364 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107884 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90831 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90831 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90831 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90831 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90831 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90831 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-19548 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-19548 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-19548 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-19548 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-19548 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-19548 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-19548 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-19548 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-67693 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90829 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90829 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90828 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90828 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90828 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90828 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90828 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90828 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90828 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91779 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91779 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91779 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91779 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91779 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91779 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91779 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91779 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90831 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90831 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-13757 | libp11-kit0 | 0.26.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-17591 | libarchive13t64 | 3.8.5-1ubuntu2.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-54369 | libacl1 | 2.3.2-2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-15003 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-15003 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-15003 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-15003 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-15003 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-15003 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-15003 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-15003 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6845 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6845 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6845 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6845 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6845 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-6845 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90829 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90829 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90829 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90829 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90829 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90829 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121876 | libsystemd0 | 259.9-0ubuntu0.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121876 | libudev1 | 259.9-0ubuntu0.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90830 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90830 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90830 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90830 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90830 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90830 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90830 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-90830 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119373 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2024-52005 | git-man | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-113351 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47240 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47240 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47240 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95619 | cpp | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95619 | cpp-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95619 | gcc | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95619 | gcc-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-46727 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-46727 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-46727 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115506 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124024 | libc-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124024 | libc-dev-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124024 | libc-gconv-modules-extra | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124024 | libc6 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-102010 | cpp-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124709 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107708 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107708 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107708 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107708 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-10990 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-10990 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2025-10990 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | GHSA-j3g3-5qv5-52mj | net-imap | 0.4.19 | 0.4.20 | net-imap rubygem vulnerable to possible DoS by memory exhaustion — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| MEDIUM | GHSA-8p34-64r3-mwg8 | net-imap | 0.4.19 | 0.5.15 | Net::IMAP: Command Injection via non-synchronizing literal in "raw" argument — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| MEDIUM | CVE-2026-9538 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-9538 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-9538 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-9538 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2024-52005 | git | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-102010 | gcc | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-102010 | gcc-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-117610 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-83408 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | GO-2026-6859 | stdlib | go1.27.3 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/bin/pebble |
| MEDIUM | CVE-2026-93990 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-54696 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-54696 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-54696 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-105437 | git | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-105437 | git-man | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115455 | cpp | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115455 | cpp-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115455 | gcc | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115455 | gcc-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-102633 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-118370 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124024 | libc6-dev | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-83357 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95692 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-63435 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-63435 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-63435 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107778 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107778 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107778 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107778 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48962 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48962 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48962 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48962 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-102010 | cpp | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112322 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112319 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112319 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112319 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112319 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112320 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112320 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112320 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112320 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112316 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112316 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112316 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112316 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112315 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112315 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112315 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112315 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112318 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119586 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-110264 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-110264 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-110264 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112314 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112314 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112314 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112314 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112321 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112321 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112321 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112321 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-41316 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-41316 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-41316 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112322 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112322 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112322 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112318 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | GHSA-g857-hhfv-j68w | zlib | 3.1.1 | 3.1.2 | Buffer Overflow in Zlib::GzipReader ungetc via large input leads to memory corruption — /usr/lib/ruby/gems/3.3.0/specifications/default/zlib-3.1.1.gemspec |
| MEDIUM | CVE-2026-111760 | git | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-111760 | git-man | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114691 | cpp | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114691 | cpp-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114691 | gcc | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114691 | gcc-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-27820 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-27820 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-27820 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-132138 | libsasl2-2 | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-132138 | libsasl2-modules-db | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48959 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48959 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48959 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48959 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112323 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119079 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112323 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119079 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112323 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119079 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112323 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119079 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | GHSA-75xq-5h9v-w6px | net-imap | 0.4.19 | 0.4.24 | net-imap vulnerable to command Injection via unvalidated Symbol inputs — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| MEDIUM | CVE-2026-112317 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112317 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112317 | libkrb5-3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112317 | libkrb5support0 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-42258 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-42258 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-42258 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112318 | libgssapi-krb5-2 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-112318 | libk5crypto3 | 1.22.1-2ubuntu4.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-83368 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-94114 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88823 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88823 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88823 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88823 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91411 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-60589 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc-dev-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc-gconv-modules-extra | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc6 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115819 | libc6-dev | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119378 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107496 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91417 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc-dev-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc-gconv-modules-extra | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc6 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121757 | libc6-dev | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107494 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107494 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107494 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107494 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95691 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95691 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95691 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95691 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-119379 | libsqlite3-0 | 3.46.1-9ubuntu0.3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91094 | dpkg | 1.23.7ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-124317 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114469 | git | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-114469 | git-man | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88647 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47241 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47241 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-47241 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-105111 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91381 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | bsdutils | 1:2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libblkid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libmount1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libsmartcols1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | libuuid1 | 2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-78408 | login | 1:4.16.0-2+really2.41.3-3ubuntu2.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121482 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48961 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48961 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48961 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-48961 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-88822 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-127039 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-113408 | git | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-113408 | git-man | 1:2.53.0-1ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91395 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-125709 | cpp | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-125709 | cpp-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-125709 | gcc | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-125709 | gcc-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107496 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-127040 | libgnutls30t64 | 3.8.12-2ubuntu1.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-95690 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-7017 | perl-modules-5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-7017 | perl-base | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-7017 | perl | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-7017 | libperl5.40 | 5.40.1-7ubuntu0.4 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115456 | gcc-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115456 | gcc | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115456 | cpp-x86-64-linux-gnu | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-115456 | cpp | 4:15.2.0-5ubuntu1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121758 | libc6-dev | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121758 | libc6 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121758 | libc-gconv-modules-extra | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121758 | libc-dev-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121758 | libc-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107161 | libsasl2-modules-db | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107161 | libsasl2-2 | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91382 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-129483 | libsasl2-modules-db | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-129483 | libsasl2-2 | 2.1.28+dfsg1-9ubuntu3 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | libssl3t64 | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc-gconv-modules-extra | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc-dev-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc-bin | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107496 | openssl-provider-legacy | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-107496 | openssl | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc6 | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-100290 | libc6-dev | 2.43-2ubuntu2.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-121481 | libssl-dev | 3.5.5-1ubuntu3.7 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-87255 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-77214 | libexpat1 | 2.7.4-1ubuntu0.2 | /var/lib/dpkg/status | |
| MEDIUM | CVE-2026-91396 | openjdk-21-jre-headless | 21.0.13.1+2-1~26.04.1 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1150 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66865 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66863 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1151 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1150 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2026-56289 | patch | 2.8-2build1 | /var/lib/dpkg/status | |
| LOW | CVE-2026-56288 | patch | 2.8-2build1 | /var/lib/dpkg/status | |
| LOW | CVE-2026-105712 | gpgv | 2.4.8-4ubuntu3.1 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66861 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66861 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66861 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66861 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66861 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66861 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66861 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1151 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1151 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1150 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1150 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1150 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66863 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66865 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66863 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66865 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66863 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66865 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66863 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66865 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66863 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2018-10126 | libjpeg-turbo8 | 2.1.5-4ubuntu4 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66865 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66863 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66865 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66863 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66865 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-61594 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-43857 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-43857 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| LOW | GHSA-c4fp-cxrr-mj66 | net-imap | 0.4.19 | 0.5.15 | Net::IMAP: Denial of Service via incomplete raw argument validation — /usr/lib/ruby/gems/3.3.0/specifications/net-imap-0.4.19.gemspec |
| LOW | CVE-2025-43857 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-61594 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-58767 | libruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-58767 | ruby3.3 | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-58767 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66866 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66866 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-5278 | coreutils | 9.5-1ubuntu2+0.0.0~ubuntu25 | 9.7-3ubuntu2.1 | /var/lib/dpkg/status |
| LOW | CVE-2025-66866 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66866 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66866 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66866 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66866 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | GHSA-j4pr-3wm6-xx2r | uri | 0.13.2 | 0.13.3 | URI Credential Leakage Bypass over CVE-2025-27221 — /usr/lib/ruby/gems/3.3.0/specifications/default/uri-0.13.2.gemspec |
| LOW | CVE-2025-66866 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-66861 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1150 | binutils-x86-64-linux-gnu | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1150 | binutils-common | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1150 | binutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | GHSA-c2f4-jgmc-q2r5 | rexml | 3.3.9 | 3.4.2 | REXML has DoS condition when parsing malformed XML file — /usr/lib/ruby/gems/3.3.0/specifications/rexml-3.3.9.gemspec |
| LOW | CVE-2025-1151 | libbinutils | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1151 | libctf-nobfd0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1151 | libctf0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1151 | libgprofng0 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2025-1151 | libsframe3 | 2.46-3ubuntu2 | /var/lib/dpkg/status | |
| LOW | CVE-2026-40228 | libudev1 | 259.9-0ubuntu0.1 | /var/lib/dpkg/status | |
| LOW | CVE-2026-40228 | libsystemd0 | 259.9-0ubuntu0.1 | /var/lib/dpkg/status | |
| LOW | CVE-2024-56433 | passwd | 1:4.17.4-2ubuntu3 | /var/lib/dpkg/status | |
| LOW | CVE-2024-56433 | login.defs | 1:4.17.4-2ubuntu3 | /var/lib/dpkg/status | |
| LOW | CVE-2025-61594 | ruby3.3-dev | 3.3.8-2ubuntu3.2 | /var/lib/dpkg/status | |
| UNKNOWN | CVE-2025-9301 | cmake | 4.2.3-2ubuntu2 | /var/lib/dpkg/status | |
| UNKNOWN | CVE-2021-45261 | patch | 2.8-2build1 | /var/lib/dpkg/status | |
| UNKNOWN | CVE-2025-9301 | cmake-data | 4.2.3-2ubuntu2 | /var/lib/dpkg/status | |
| UNKNOWN | CVE-2026-11979 | libxml2-16 | 2.15.2+dfsg-0.1ubuntu0.3 | /var/lib/dpkg/status |
ghcr.io/openvoxproject/openvoxserver:latest-alpine (2026-11-21)
Trivy
HIGH 1
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2022-41404 | org.ini4j:ini4j | 0.5.4 | org.ini4j: unspecified DoS — Java |
Grype
HIGH 1
LOW 1
NVD/CPE filtered 55
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | GHSA-jr6h-r7vg-f9mc | ini4j | 0.5.4 | org.ini4j allows attackers to cause a Denial of Service (DoS) — /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar | |
| LOW | GHSA-x2f5-4prf-w687 | json | 2.9.1 | 2.19.9 | Ruby json: JSON generator heap buffer overflow when streaming to an IO — /usr/lib/ruby/gems/3.4.0/specifications/default/json-2.9.1.gemspec |
Filtered NVD/CPE matches (55)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.9-r1 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | openssl-dev | 3.5.9-r1 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | openssl | 3.5.9-r1 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.9-r1 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.9-r1 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.9-r1 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | openssl | 3.5.9-r1 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | openssl-dev | 3.5.9-r1 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.9-r1 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | openssl-dev | 3.5.9-r1 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | openssl | 3.5.9-r1 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.9-r1 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.9-r1 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-59850 | libssh2 | 1.11.1-r4 | A flaw was found in libssh. If data packets are processed after a channel is closed, channel data callbacks can be invoked after the associated data has already been freed, leading to crashes or possible use-after-free conditions. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libssl3 | 3.5.9-r1 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | openssl | 3.5.9-r1 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | openssl-dev | 3.5.9-r1 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | openssl-dev | 3.5.9-r1 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | openssl | 3.5.9-r1 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.9-r1 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.9-r1 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | openssl-dev | 3.5.9-r1 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | openssl | 3.5.9-r1 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56392 | coreutils | 9.11-r0 | GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write. When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout. This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.9-r1 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2013-0256 | ruby-rdoc | 3.4.13-r0 | darkfish.js in RDoc 2.3.0 through 3.12 and 4.x before 4.0.0.preview2.1, as used in Ruby, does not properly generate documents, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted URL. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56392 | coreutils-env | 9.11-r0 | GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write. When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout. This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56392 | coreutils-fmt | 9.11-r0 | GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write. When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout. This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56392 | coreutils-sha512sum | 9.11-r0 | GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write. When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout. This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56391 | coreutils | 9.11-r0 | GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input. When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure. This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56391 | coreutils-env | 9.11-r0 | GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input. When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure. This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56391 | coreutils-fmt | 9.11-r0 | GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input. When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure. This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-56391 | coreutils-sha512sum | 9.11-r0 | GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input. When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure. This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-18508 | tar | 1.35-r5 | A flaw was found in GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside that boundary during a single extraction. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59845 | libssh2 | 1.11.1-r4 | A flaw was found in libssh. When ProxyCommand is used, an unchecked fork() failure can be stored as process ID -1; during cleanup, signals may then be sent across the caller's accessible process tree, leading to local denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100407 | git | 2.54.1-r0 | Git for Windows is the Windows port of Git. From 2.44.0.windows.1 until 2.55.0.windows.3, the git-credential-wincred store operation in contrib/credential/wincred/git-credential-wincred.c uses _scwprintf() to size a formatted wide-character credential buffer without space for the terminating NUL when both password and oauth_refresh_token are present. The operation also passes a byte count to _snwprintf_s() where a wide-character count is required, allowing the terminator to be written one WCHAR past the heap allocation before CredWriteW() persists the credential. The resulting fixed two-byte NUL overwrite can terminate the helper with Windows heap-corruption status and can cause git credential approve to report success even though the OAuth credential was not stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100408 | git | 2.54.1-r0 | Git for Windows is the Windows port of Git. From 2.43.0.windows.1 until 2.55.0.windows.3, when a matching git:* credential exists in Windows Credential Manager and a git-credential-wincred erase input includes a password field, the operation in contrib/credential/wincred/git-credential-wincred.c allocates a buffer of exactly CredentialBlobSize bytes in match_cred_password() and then uses wcsncpy_s() to copy the corresponding number of wide characters plus a terminating NUL. The destination capacity is also supplied in bytes instead of WCHAR elements, allowing a fixed two-byte NUL write past the allocation before the password comparison determines whether CredDeleteW() should remove the credential; erase without a password field does not enter this comparison path. The helper can terminate with Windows heap-corruption status, and git credential reject can appear successful while the rejected credential remains stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-18477 | tar | 1.35-r5 | A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59843 | libssh2 | 1.11.1-r4 | A flaw was found in libssh. A remote authenticated peer can advertise a zero maximum packet size in SSH_MSG_CHANNEL_OPEN, causing later channel writes to loop indefinitely and consume CPU, leading to denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59844 | libssh2 | 1.11.1-r4 | A flaw was found in libssh. A remote authenticated client can issue SSH_FXP_READ requests with an arbitrarily large length, causing a libssh SFTP server to allocate excessive memory and potentially exhaust it through repeated requests. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-5704 | tar | 1.35-r5 | A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection. — /lib/apk/db/installed | |
| MEDIUM | CVE-2016-2781 | coreutils | 9.11-r0 | chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. — /lib/apk/db/installed | |
| MEDIUM | CVE-2016-2781 | coreutils-env | 9.11-r0 | chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. — /lib/apk/db/installed | |
| MEDIUM | CVE-2016-2781 | coreutils-fmt | 9.11-r0 | chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. — /lib/apk/db/installed | |
| MEDIUM | CVE-2016-2781 | coreutils-sha512sum | 9.11-r0 | chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.9-r1 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.9-r1 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | openssl | 3.5.9-r1 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | openssl-dev | 3.5.9-r1 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59848 | libssh2 | 1.11.1-r4 | A flaw was found in libssh. A malicious SFTP server can send responses for unknown request IDs that libssh clients keep queued indefinitely, causing unbounded memory growth and client-side denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.9-r1 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| LOW | CVE-2026-59846 | libssh2 | 1.11.1-r4 | A flaw was found in libssh. A malicious username expanded through %r in ProxyCommand handling can inject shell metacharacters, exposing environment variables and causing unintended shell behavior. — /lib/apk/db/installed |
ghcr.io/voxpupuli/commitlint
Downloads
ghcr.io/voxpupuli/commitlint:latest (2026-08-27)
Trivy
CRITICAL 1
HIGH 51
MEDIUM 52
LOW 38
UNKNOWN 1
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r1 | 1.2.1-r0 | brotli: Out-of-Bounds Write in Google Brotli Decoder — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-84292 | fast-uri | 3.1.6 | 2.4.6, 3.1.7, 4.1.4 | fast-uri: fast-uri: Authority Injection via Unvalidated Port Serialization — Node.js |
| HIGH | CVE-2026-69152 | brace-expansion | 5.0.7 | 1.1.18, 2.1.4, 3.0.6, 5.0.9 | brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation — Node.js |
| HIGH | CVE-2026-14257 | brace-expansion | 5.0.7 | 5.0.8, 3.0.3, 2.1.3, 1.1.17 | brace-expansion: Brace-expansion: Denial of Service via memory exhaustion in expand() function — Node.js |
| HIGH | CVE-2026-102278 | brace-expansion | 5.0.7 | 5.0.11, 3.0.8, 2.1.6, 1.1.20 | brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns — Node.js |
| HIGH | CVE-2026-102276 | brace-expansion | 5.0.7 | 5.0.10, 3.0.7, 2.1.5, 1.1.19 | brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns — Node.js |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | zlib: zlib: Heap buffer overflow in gz_vacate() allows arbitrary code execution — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-89161 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-89157 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Out-of-bounds write via large pattern input — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-86145 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-103111 | pcre2 | 10.47-r1 | 10.49-r0 | pcre2: pcre2: Out-of-bounds write via crafted regular expression — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.6-r2 | 1.2.6-r3 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-107891 | musl | 1.2.6-r2 | 1.2.6-r3 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-93990 | libexpat | 2.8.3-r0 | 2.8.5-r0 | expat: Expat: XML Injection via Malformed UTF-16 Input — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-77214 | libexpat | 2.8.3-r0 | 2.9.0-r0 | expat: expat: Information disclosure via heap buffer over-read in XML_ParseBuffer — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-76957 | libexpat | 2.8.3-r0 | 2.8.4-r0 | libexpat: libexpat: Memory corruption vulnerability allows arbitrary code execution or denial of service — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-76956 | libexpat | 2.8.3-r0 | 2.8.4-r0 | libexpat: libexpat: Denial of Service via hash flooding attack with crafted XML — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-76641 | libexpat | 2.8.3-r0 | 2.8.4-r0 | expat: Expat: Denial of Service via XML external entity parsing — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-66046 | libexpat | 2.8.3-r0 | 2.8.4-r0 | expat: Expat: Denial of Service via quadratic complexity in attribute processing — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-118370 | libexpat | 2.8.3-r0 | 2.10.0-r0 | expat: expat: Denial of Service via integer overflow during XML attribute parsing — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-117610 | libexpat | 2.8.3-r0 | 2.10.0-r0 | expat: expat: Denial of Service via NULL pointer dereference in external entity parsing — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-115506 | libexpat | 2.8.3-r0 | 2.10.0-r0 | expat: expat: Denial of Service via delayed entity amplification detection — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-113351 | libexpat | 2.8.3-r0 | 2.10.0-r0 | expat: expat: Denial of Service via improper memory tracking in XML_ParserReset — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-97031 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-78669 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-78667 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang: golang: Denial of Service via crafted HTTP Range headers — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56862 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | crypto/tls: golang: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56860 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | net/url: golang: golang net/url: Denial of Service from quadratic complexity in path resolution — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56859 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | encoding/xml: golang: Go: Denial of Service via XML decoding recursion depth issue — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56858 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | html/template: golang: Go html/template: Cross-Site Scripting via pathological input — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56853 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | net/http: golang: Go net/http: Unencrypted HTTP/2 connections vulnerable to Denial of Service — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-46600 | stdlib | v1.26.4 | 1.26.6, 1.27.0-rc.3 | golang.org/x/net/dns/dnsmessage: golang.org/x/net/dns/dnsmessage: Denial of Service via invalid DNS record parsing — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-39822 | stdlib | v1.26.4 | 1.25.12, 1.26.5, 1.27.0-rc.2 | golang: Go os.Root: Symlink following vulnerability allows directory traversal — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-39821 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-33818 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-111943 | stdlib | v1.26.4 | 1.26.10, 1.27.3 | crypto/x509: golang: crypto/x509: Man-in-the-middle attacks via untrusted intermediate certificates — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56852 | golang.org/x/text | v0.38.0 | 0.39.0 | golang.org/x/text: golang.org/x/text: Denial of Service via invalid UTF-8 input — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56851 | golang.org/x/text | v0.38.0 | 0.41.0 | golang.org/x/text: golang.org/x/text: Denial of Service via out-of-bounds slice error in Nickname profile — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-87018 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via TLS renegotiation with mismatched certificate — Node.js |
| HIGH | CVE-2026-19534 | undici | 6.27.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: Denial of Service via unrequested WebSocket subprotocol — Node.js |
| HIGH | CVE-2026-109869 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unhandled stream error on excessive content encodings — Node.js |
| HIGH | CVE-2026-109383 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Certificate validation bypass via dropped TLS options in Agent — Node.js |
| HIGH | CVE-2026-73566 | tar | 7.5.19 | 7.5.21 | tar: node-tar: Denial of Service via crafted long-path tar archive — Node.js |
| HIGH | CVE-2026-69192 | ip-address | 10.2.0 | 10.3.1 | ip-address: ip-address: Inconsistent IP address parsing leads to Server-Side Request Forgery (SSRF) and trust-boundary bypass — Node.js |
| HIGH | CVE-2026-84394 | fast-uri | 3.1.6 | 2.4.6, 3.1.7, 4.1.4 | fast-uri: fast-uri: Host confusion via unbalanced URI brackets can bypass security policies — Node.js |
| HIGH | CVE-2026-92392 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: HTTP/2 upload Use-After-Free — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-114466 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-111760 | git | 2.54.0-r0 | 2.54.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-105437 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-114466 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-111760 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| HIGH | CVE-2026-105437 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-110306 | fast-uri | 3.1.6 | 2.4.8, 3.1.9, 4.2.3 | fast-uri: fast-uri: Cross-Site Scripting via improper URI scheme decoding — Node.js |
| MEDIUM | CVE-2026-110180 | fast-uri | 3.1.6 | 2.4.8, 3.1.9, 4.2.3 | fast-uri: fast-uri: Security policy bypass via improper host canonicalization — Node.js |
| MEDIUM | CVE-2026-109932 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unbounded WebSocket PONG buffering — Node.js |
| MEDIUM | CVE-2026-15157 | undici | 6.27.0 | 6.28.0, 7.29.0, 8.9.0 | undici: undici: HTTP header injection via unvalidated blob-like body type property — Node.js |
| MEDIUM | CVE-2026-102277 | brace-expansion | 5.0.7 | 5.0.12, 3.0.9, 2.1.7, 1.1.21 | brace-expansion: brace-expansion: Denial of Service via crafted brace patterns — Node.js |
| MEDIUM | CVE-2026-16728 | undici | 6.27.0 | 6.28.0, 7.29.0, 8.9.0 | undici: undici: Response desynchronization via retry interceptor with mismatched Content-Length — Node.js |
| MEDIUM | CVE-2026-16729 | undici | 6.27.0 | 6.28.0, 7.29.0, 8.9.0 | undici: Undici: Cookie attribute injection allows bypassing security protections — Node.js |
| MEDIUM | CVE-2026-85024 | undici | 6.27.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: Denial of Service via unhandled error in WebSocket permessage-deflate decompression — Node.js |
| MEDIUM | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | Improper Restriction of Operations within the Bounds of a Memory Buffe ... — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-95692 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-95691 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-86472 | fast-uri | 3.1.6 | 2.4.7, 3.1.8, 4.1.5 | fast-uri: fast-uri: Security bypass due to inconsistent host case normalization — Node.js |
| MEDIUM | CVE-2026-109924 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via memory exhaustion in EventSource client — Node.js |
| MEDIUM | CVE-2026-19931 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via incorrect connection reuse with Negotiate authentication — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-118773 | glob | 13.0.6 | 14.0.2 | glob: glob: Denial of Service (DoS) via incomplete traversal cancellation — Node.js |
| MEDIUM | CVE-2026-92388 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: FTP wildcard write callback mixup — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-101910 | ip-address | 10.2.0 | 10.5.1 | ip-address: ip-address: Security boundary bypass via unclassified NAT64 local-use address range — Node.js |
| MEDIUM | CVE-2026-101911 | ip-address | 10.2.0 | 10.7.1 | ip-address: ip-address: Denial of Service via unbounded IPv6 address parsing — Node.js |
| MEDIUM | CVE-2026-101912 | ip-address | 10.2.0 | 10.7.1 | ip-address: ip-address: Access control bypass via cross-family subnet comparison — Node.js |
| MEDIUM | CVE-2026-101913 | ip-address | 10.2.0 | 10.5.1 | ip-address: ip-address: Security bypass via incomplete IPv6 link-local address validation — Node.js |
| MEDIUM | CVE-2026-111997 | ip-address | 10.2.0 | 10.7.4 | ip-address: ip-address: Denial of Service via excessive percent characters in IPv6 address input — Node.js |
| MEDIUM | CVE-2026-54272 | ip-address | 10.2.0 | 10.2.1 | ip-address: ip-address: Server-Side Request Forgery via IPv4-mapped/NAT64 IPv6 address misclassification — Node.js |
| MEDIUM | CVE-2026-69198 | ip-address | 10.2.0 | 10.2.2 | ip-address: ip-address: Server-Side Request Forgery (SSRF) and trust-boundary bypass — Node.js |
| MEDIUM | CVE-2026-118764 | minimatch | 10.2.5 | 11.0.1 | minimatch: minimatch: Denial of Service via crafted glob pattern expansion — Node.js |
| MEDIUM | CVE-2026-104844 | postcss-selector-parser | 7.1.4 | 7.1.6, 6.1.5 | postcss-selector-parser: postcss-selector-parser: Denial of Service via crafted CSS selectors — Node.js |
| MEDIUM | CVE-2026-82208 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Improper certificate validation when using wolfSSL CA cache — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-97054 | stdlib | v1.26.4 | 1.26.11, 1.27.4 | net/http: golang: net/http: Denial of Service via race condition when handling oversized HTTP/1 requests — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-97032 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: net/http: Denial of Service via concurrent HPACK encoder modification — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-97030 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | html/template: golang: html/template: Cross-site scripting via improper escaping of yield keyword — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-94448 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | html/template: golang: golang: cross-site scripting via consecutive expressions in JavaScript template literals — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-94440 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/textproto: mime/multipart: golang: golang: Denial of Service via memory limit bypass in multipart form parsing — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-94439 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang: net/http: HTTP request smuggling via improper handling of HTTP/1 CONNECT responses — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-78663 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: golang: flow control limit bypass via double refund in HTTP/2 server — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-78660 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang: golang.org/x/net/http2: net/http: HTTP response smuggling via malformed HTTP/2 framing headers — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-78659 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang.org/x/net/http2: golang: net/http: Denial of Service via HTTP/2 trailer header memory exhaustion — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-56866 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang: golang: Cross-user response poisoning via desynchronized HTTP CONNECT connections — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-42505 | stdlib | v1.26.4 | 1.25.12, 1.26.5, 1.27.0-rc.2 | crypto/tls: golang: Go crypto/tls: Information disclosure in Encrypted Client Hello — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-113408 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-114467 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-102633 | libexpat | 2.8.3-r0 | 2.9.0-r0 | expat: expat: Denial of Service via integer overflow in expat_realloc — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-107496 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-95691 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-95692 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-114469 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-58055 | nghttp2-libs | 1.69.0-r0 | 1.70.0-r0 | nghttp2: nghttp2: HTTP Request/Response Smuggling and Response-Queue Poisoning via ambiguous HTTP/1.1 Upgrade requests — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-113408 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-114467 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-107496 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-89156 | pcre2 | 10.47-r1 | 10.48-r0 | PCRE2: PCRE2: Out-of-bounds read via invalid UTF data during JIT fallback — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-89158 | pcre2 | 10.47-r1 | 10.48-r0 | PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-89160 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Denial of Service via out-of-bounds read during invalid UTF matching — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-88823 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Message authentication bypass via zero-length AAD update — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-88822 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-18540 | undici | 6.27.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: HTTP response splitting via retry interceptor — Node.js |
| LOW | CVE-2026-56857 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | os: golang: golang: Directory traversal via Windows junction handling — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| LOW | CVE-2026-88822 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-86413 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: Negotiate credentials sent to redirected origin — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-86414 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: leaking host credentials to HTTP proxy — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-86415 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: auto client cert connection reuse mixup — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-87861 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: cross-origin reuse of a Negotiate connection — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-87862 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: HSTS cache import drops longer-lived child — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-87863 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: Hsts Response Erases Persisted Entries — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-87864 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: IMAP APPEND plus CRLF conversion command injection — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-87865 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: knownhost callback mismatches key as missing — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-87866 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: wolfSSL public-key pinning bypass — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-92386 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie aborts cookie jar load — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-94266 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: password leak in CURLINFO_EFFECTIVE_URL — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-94265 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: Authorization: Negotiate sent to foreign origin — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-92391 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: curl_mime_free stack overflow by recursion — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-92390 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: -J no-clobber guarantee bypassed with 103 early hints — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-92389 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: TFTP direction confusion — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-92387 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: never-ending loop via server response omission — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-110725 | fast-uri | 3.1.6 | 2.4.8, 3.1.9, 4.2.3 | fast-uri: fast-uri: Cross-site scripting via unescaped colon in relative URI paths — Node.js |
| LOW | CVE-2026-110095 | fast-uri | 3.1.6 | 2.4.8, 3.1.9, 4.2.3 | fast-uri: fast-uri: Path traversal via improper relative URI normalization — Node.js |
| LOW | CVE-2026-107928 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: info leak uploading over WebSockets with GnuTLS — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-107929 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: local interface connection reuse mixup — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-13608 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Authentication bypass in OpenLDAP SASL negotiation via Man-in-the-Middle (MITM) attack — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-18924 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Use-after-free in HTTP/2 Server Push with shared connections — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-80229 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Memory corruption vulnerability via OpenSSL 3 provider use-after-free — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-80230 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Public key pinning bypass allows unauthenticated connections — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-80231 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Incorrect HTTPS connection reuse with Native CA Store — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-89162 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Information disclosure via pcre2_serialize_encode — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-80255 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure due to secure cookie attribute bypass — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-82209 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via improper Public Suffix List boundary check — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-86409 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: stale SigV4 headers sent unintended — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-86410 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: redirect to SFTP or SCP bypasses host verification — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-86411 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: FTP connection reuse inherits client-certificate — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-86412 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie erases cookie jar — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| LOW | CVE-2026-88823 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Message authentication bypass via zero-length AAD update — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
| UNKNOWN | CVE-2026-80256 | libcurl | 8.21.0-r0 | 8.22.0-r0 | Title Not Available — ghcr.io/voxpupuli/commitlint:latest (alpine 3.24.1) |
Grype
CRITICAL 13
HIGH 87
MEDIUM 35
LOW 8
UNKNOWN 1
NVD/CPE filtered 68
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-92388 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86414 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87861 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86413 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87866 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-19931 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-94265 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | GO-2026-6612 | stdlib | go1.26.3 | 1.26.9 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. — /usr/bin/git-lfs |
| CRITICAL | GO-2026-6612 | golang.org/x/net | v0.54.0 | 0.60.0 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. — /usr/bin/git-lfs |
| CRITICAL | CVE-2026-18924 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86411 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r1 | 1.2.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86415 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-102633 | libexpat | 2.8.3-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-118370 | libexpat | 2.8.3-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82208 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-117610 | libexpat | 2.8.3-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-76957 | libexpat | 2.8.3-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86145 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-93990 | libexpat | 2.8.3-r0 | 2.8.5-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-95692 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95692 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | GHSA-6j4f-fj2g-mc7p | brace-expansion | 5.0.7 | 5.0.10 | brace-expansion: DoS via uncontrolled recursion in parseCommaParts causing stack exhaustion — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GHSA-mwp4-54f8-5fhr | ip-address | 10.2.0 | 10.3.1 | ip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and trust-boundary bypass — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| HIGH | GO-2026-5970 | golang.org/x/text | v0.38.0 | 0.39.0 | A norm.Iter can enter an infinite loop when handling input containing invalid UTF-8 bytes. — /npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | GO-2026-5970 | golang.org/x/text | v0.37.0 | 0.39.0 | A norm.Iter can enter an infinite loop when handling input containing invalid UTF-8 bytes. — /usr/bin/git-lfs |
| HIGH | CVE-2026-80255 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-qhr7-859c-m2p7 | brace-expansion | 5.0.7 | 5.0.11 | brace-expansion: DoS via uncontrolled recursion on nested brace groups causing stack exhaustion — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | CVE-2026-113351 | libexpat | 2.8.3-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-13608 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-115506 | libexpat | 2.8.3-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6613 | stdlib | go1.26.3 | 1.26.9, 1.27.2 | When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP. — /usr/bin/git-lfs |
| HIGH | CVE-2026-89161 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| HIGH | GHSA-2m5v-pch6-74hx | undici | 6.27.0 | 6.29.1 | undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | GHSA-qrxm-fqhp-jwvm | undici | 6.27.0 | 6.29.1 | undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | GHSA-qw65-cvwx-89v3 | fast-uri | 3.1.6 | 3.1.7 | fast-uri vulnerable to authority injection via an unvalidated port in serialize — /npm/node_modules/fast-uri/package.json |
| HIGH | CVE-2026-88823 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-88823 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-103111 | pcre2 | 10.47-r1 | 10.49-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-76956 | libexpat | 2.8.3-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-95691 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95691 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-107496 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-107496 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | GHSA-xjj6-f33q-929c | undici | 6.27.0 | 6.29.1 | undici vulnerable to Denial of Service via unhandled error on excessive content-encodings — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | CVE-2026-89157 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-77214 | libexpat | 2.8.3-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80230 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-58mr-gqgx-xq4g | fast-uri | 3.1.6 | 3.1.7 | fast-uri vulnerable to host confusion via an unclosed bracket in the URI authority — /npm/node_modules/fast-uri/package.json |
| HIGH | CVE-2026-76641 | libexpat | 2.8.3-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82209 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-rfgv-xxqx-mfg5 | undici | 6.27.0 | 6.28.1 | undici vulnerable to Denial of Service via unrequested WebSocket subprotocol — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | CVE-2026-105437 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-105437 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6608 | stdlib | go1.26.3 | 1.26.9, 1.27.2 | Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes. — /usr/bin/git-lfs |
| HIGH | GO-2026-6607 | stdlib | go1.26.3 | 1.26.9, 1.27.2 | Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result. — /usr/bin/git-lfs |
| HIGH | CVE-2026-107928 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-5026 | stdlib | go1.26.3 | 1.25.13, 1.26.6, 1.27.0-rc.3 | 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". — /usr/bin/git-lfs |
| HIGH | CVE-2026-111760 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92389 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86410 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6611 | stdlib | go1.26.3 | 1.26.9 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. — /usr/bin/git-lfs |
| HIGH | GO-2026-6611 | golang.org/x/net | v0.54.0 | 0.60.0 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. — /usr/bin/git-lfs |
| HIGH | CVE-2026-92386 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87863 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86412 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87864 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6603 | stdlib | go1.26.3 | 1.26.9 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. — /usr/bin/git-lfs |
| HIGH | GO-2026-6603 | golang.org/x/net | v0.54.0 | 0.60.0 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. — /usr/bin/git-lfs |
| HIGH | CVE-2026-92392 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-66046 | libexpat | 2.8.3-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87862 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92387 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92391 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86409 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-r292-9mhp-454m | tar | 7.5.19 | 7.5.21 | node-tar: Uncontrolled recursion in mapHas/filesFilter allows uncatchable stack-overflow DoS via crafted long-path tar with member selection — /usr/local/lib/node_modules/npm/node_modules/tar/package.json |
| HIGH | GO-2026-6610 | stdlib | go1.26.3 | 1.26.9 | Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling. — /usr/bin/git-lfs |
| HIGH | GO-2026-6610 | golang.org/x/net | v0.54.0 | 0.60.0 | Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling. — /usr/bin/git-lfs |
| HIGH | GO-2026-5942 | stdlib | go1.26.3 | 1.26.6, 1.27.0-rc.3 | Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer. — /usr/bin/git-lfs |
| HIGH | GO-2026-5942 | golang.org/x/net | v0.54.0 | 0.56.0 | Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer. — /usr/bin/git-lfs |
| HIGH | CVE-2026-94266 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80231 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80229 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6090 | stdlib | go1.26.3 | 1.25.13, 1.26.6, 1.27.0-rc.3 | Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely. — /usr/bin/git-lfs |
| HIGH | GO-2026-5972 | stdlib | go1.26.3 | 1.25.13, 1.26.6, 1.27.0-rc.3 | Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures. — /usr/bin/git-lfs |
| HIGH | CVE-2026-107929 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-5026 | golang.org/x/net | v0.54.0 | 0.55.0 | 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". — /usr/bin/git-lfs |
| HIGH | GO-2026-6617 | golang.org/x/net | v0.54.0 | 0.60.0 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. — /usr/bin/git-lfs |
| HIGH | GO-2026-6617 | stdlib | go1.26.3 | 1.26.9 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. — /usr/bin/git-lfs |
| HIGH | GHSA-rgw5-rvv9-x895 | brace-expansion | 5.0.7 | 5.0.9 | brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GHSA-mh99-v99m-4gvg | brace-expansion | 5.0.7 | 5.0.8 | brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GO-2026-6605 | stdlib | go1.26.3 | 1.26.9, 1.27.2 | When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning. — /usr/bin/git-lfs |
| HIGH | CVE-2026-87865 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.6-r2 | 1.2.6-r3 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl | 1.2.6-r2 | 1.2.6-r3 | /lib/apk/db/installed |
| HIGH | CVE-2026-92390 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-5037 | stdlib | go1.26.3 | 1.25.11, 1.26.4 | (*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, ".") to execute repeatedly on the same input hostname. With a large DNS SAN list, verification costs scaled quadratically based on the number of SAN entries multiplied by the hostname's label count. Because x509.Verify validates hostnames before building the certificate chain, this overhead occurred even for untrusted certificates. — /usr/bin/git-lfs |
| MEDIUM | GO-2026-6218 | stdlib | go1.26.3 | 1.25.13, 1.26.6, 1.27.0-rc.3 | Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte buffer using index-based backtracking for '..' segments, eliminating the quadratic time complexity and significantly reducing memory allocations. — /usr/bin/git-lfs |
| MEDIUM | CVE-2026-89160 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-88822 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-88822 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-58055 | nghttp2-libs | 1.69.0-r0 | 1.70.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-89158 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-8xcm-r25x-g524 | undici | 6.27.0 | 6.28.0 | undici vulnerable to downstream response desynchronization via retry interceptor — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-m8rv-5g2x-5cg5 | undici | 6.27.0 | 6.28.0 | undici vulnerable to CRLF Injection via blob-like body 'type' property — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-hrr3-gc8f-f4qj | fast-uri | 3.1.6 | 3.1.8 | fast-uri vulnerable to inconsistent host case normalization via percent-encoded octets — /npm/node_modules/fast-uri/package.json |
| MEDIUM | CVE-2026-114466 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-w74x-v6f9-j3xg | fast-uri | 3.1.6 | 3.1.9 | fast-uri vulnerable to URI scheme spoofing via percent-encoded scheme decoding — /npm/node_modules/fast-uri/package.json |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-v3r7-h72x-cjcm | undici | 6.27.0 | 6.28.0 | undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | CVE-2026-114469 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-wjr9-j795-jxcr | fast-uri | 3.1.6 | 3.1.9 | fast-uri vulnerable to host confusion via unchecked WHATWG host canonicalization — /npm/node_modules/fast-uri/package.json |
| MEDIUM | GHSA-4xrf-jv44-h6hh | ip-address | 10.2.0 | 10.2.2 | ip-address: a CIDR suffix on the parsed address suppresses special-use classification and can bypass SSRF and trust-boundary checks — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-22jq-vg5j-6vgg | ip-address | 10.2.0 | 10.2.1 | ip-address: misclassification of IPv4-mapped/NAT64 IPv6 addresses can bypass SSRF and trust-boundary checks — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GO-2026-6809 | stdlib | go1.26.3 | 1.26.10, 1.27.3 | On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy. — /usr/bin/git-lfs |
| MEDIUM | GHSA-2vr4-cq9g-pvrc | ip-address | 10.2.0 | 10.5.1 | ip-address: no classifier recognizes the NAT64 local-use range 64:ff9b:1::/48, allowing SSRF and trust-boundary bypass — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-3wwx-pv8p-q78v | undici | 6.27.0 | 6.28.1 | undici vulnerable to Denial of Service via unhandled error in WebSocket permessage-deflate decompression — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-q2hr-2g5m-vwhr | brace-expansion | 5.0.7 | 5.0.12 | brace-expansion: Quadratic-time expansion of the `{a},b}` rewrite causes CPU denial of service — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| MEDIUM | GHSA-rpw4-54j3-4h4q | ip-address | 10.2.0 | 10.5.1 | ip-address: Address6.isLinkLocal() recognizes fe80::/64 rather than fe80::/10, allowing SSRF and trust-boundary bypass to on-link hosts — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-h3mg-xc3c-68pw | ip-address | 10.2.0 | 10.7.1 | ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-rj75-hqrm-r3gf | postcss-selector-parser | 7.1.4 | 7.1.6 | PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion — /usr/local/lib/node_modules/npm/node_modules/postcss-selector-parser/package.json |
| MEDIUM | GHSA-j6r3-76f7-8jcv | ip-address | 10.2.0 | 10.7.1 | ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit an address outside its range — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GO-2026-6859 | stdlib | go1.26.3 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/bin/git-lfs |
| MEDIUM | GHSA-3g3m-2fjr-6pw4 | glob | 13.0.6 | 14.0.2 | Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal — /usr/local/lib/node_modules/npm/node_modules/glob/package.json |
| MEDIUM | GO-2026-5856 | stdlib | go1.26.3 | 1.25.12, 1.26.5, 1.27.0-rc.2 | Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of pre-shared key identities in the unencrypted client hello. — /usr/bin/git-lfs |
| MEDIUM | GO-2026-5039 | stdlib | go1.26.3 | 1.25.11, 1.26.4 | When returning errors, functions in the net/textproto package would include its input as part of the error. This might allow an attacker to inject misleading content to errors that are printed or logged. — /usr/bin/git-lfs |
| MEDIUM | GHSA-g3hv-75wg-m249 | minimatch | 10.2.5 | 11.0.1 | minimatch has potential denial of service via globparts amplification — /usr/local/lib/node_modules/npm/node_modules/minimatch/package.json |
| MEDIUM | GHSA-rxp7-6hxx-x8q5 | ip-address | 10.2.0 | 10.7.4 | ip-address: Address6 matches a zone identifier in quadratic time ahead of its length limit, allowing a single long string to stall the process — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-4qv8-2p9j-2685 | undici | 6.27.0 | 6.29.1 | undici vulnerable to Denial of Service via unbounded memory in the EventSource parser — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-9fm3-97px-rjf6 | undici | 6.27.0 | 6.29.1 | undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | CVE-2026-89156 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-89162 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-113408 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-113408 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | GHSA-xhq7-xmqj-769h | fast-uri | 3.1.6 | 3.1.9 | fast-uri vulnerable to improper path equivalence in relative reference normalization — /npm/node_modules/fast-uri/package.json |
| LOW | GHSA-333x-w4r6-6crp | fast-uri | 3.1.6 | 3.1.9 | fast-uri vulnerable to scheme injection via an unescaped first-segment colon in suffix references — /npm/node_modules/fast-uri/package.json |
| LOW | GHSA-r53p-7pc4-xj5r | undici | 6.27.0 | 6.28.1 | undici vulnerable to downstream response splitting via retry interceptor — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| UNKNOWN | CVE-2026-80256 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
Filtered NVD/CPE matches (68)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-111497 | node | 24.19.0 | 11.0.0, 22.23.4, 24.22.1, 26.12.1 | A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1.2.1. — /usr/local/bin/node |
| HIGH | CVE-2026-107493 | libssl3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-106069 | node | 24.19.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`. `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| HIGH | CVE-2026-105483 | node | 24.19.0 | 24.22.1, 26.12.1 | A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`). `tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618. This vulnerability affects Node.js **26.x** and **24.x**. — /usr/local/bin/node |
| HIGH | CVE-2026-123864 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the request body. Triggering it requires a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and reading the leaked memory requires any ordinary route that echoes or stores a request body. Cleartext node:http is not affected. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-72897 | libssl3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libcrypto3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-123872 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only client-cert auth on one host and ordinary client-cert auth on another, a client that authenticates for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to the protected host, bypassing the stricter policy. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-105482 | node | 24.19.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). This is an incomplete fix of CVE-2026-48930, which only covered dns.lookup() and the net/tls host options. Because the name is passed to c-ares as a C string, resolving attacker.example\0.trusted.example queries attacker.example and returns its records without any error. Applications that validate a hostname, for example against a domain allowlist, and then resolve it with dns.resolve*() can act on records for a different name than the one they validated. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-54873 | libcrypto3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-54873 | libssl3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-123863 | node | 24.19.0 | 24.22.3, 26.13.1 | A reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. A client can arrange for an Http2Stream that still holds nghttp2-allocated header buffers to outlive its session: the stream is removed from the session's stream set but never detached, so when ~Http2Session() runs the memory accounting is nonzero and the CHECK_EQ(current_nghttp2_memory_, 0) assertion fails, terminating the process. The trigger needs only a default http2 server whose handler responds before the request body has ended, which is typical. It is a variant of CVE-2024-27983 that the earlier fix did not cover, because that fix only detached streams still tracked in the session. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0). — /usr/local/bin/node |
| HIGH | CVE-2026-123874 | node | 24.19.0 | 24.22.3, 26.13.1 | A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respondWithFile() or respondWithFD(). A client can make the server free an Http2Stream while a write request that points to it is still queued on the socket; when that write completes, the code dereferences and makes a virtual call through the freed object. The only precondition is that the application serves a file with stream.respondWithFile() or stream.respondWithFD(), with default settings otherwise. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0). — /usr/local/bin/node |
| HIGH | CVE-2026-123866 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer `RST_STREAM` or by the server's own per-stream timeout destroying the stream, the stream's response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libcrypto3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libssl3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-123865 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js's HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-84782 | libcrypto3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libssl3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-126051 | node | 24.19.0 | 24.22.3, 26.13.1 | A deferred-callback use-after-destroy in Node.js TLS server handshake handling allows a remote, unauthenticated attacker to terminate the server process. When a TLS server uses any of the SNICallback, OCSPRequest, newSession, or resumeSession hooks, or server.addContext(), the corresponding OpenSSL callbacks are deferred, and the deferred code does not handle the underlying socket being destroyed between scheduling and execution. By sending a client hello that reaches the vulnerable path (for example, no SNI together with an OCSP request) followed by padding and a socket FIN, an attacker makes OpenSSL deliver the client hello and the end-of-file in the same tick, so the socket is destroyed before the deferred callback runs and the process raises an uncaught exception instead of emitting an 'error' event. This vulnerability affects Node.js 26.x and 24.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-123877 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-106074 | node | 24.19.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt()` to be saved into user-land startup snapshots (`--build-snapshot`) and single executable applications built with `useSnapshot`. If any of these functions, or an API that relies on them such as `URL.createObjectURL()`, is called while the snapshot is built, every process started from that snapshot returns the same values until the cache is refilled: up to 127 UUIDs and about 1,000 `randomInt()` values. Identifiers expected to be unique can collide across processes, and values issued by one process can be predicted by observing another. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-123828 | node | 24.19.0 | 24.22.3, 26.13.1 | A one-byte heap buffer overflow in Node.js HTTP/2 Alt-Svc handling lets a remote, unauthenticated attacker corrupt process memory. When an application passes an attacker-controlled value such as a request's :authority header to Http2Session.altsvc(), the AltSvc implementation in src/node_http2.cc allocates a buffer sized to the origin length and then writes it with a null terminator, placing one byte past the end of the allocation. A single request carrying a long but syntactically valid :authority triggers the out-of-bounds write, which aborts the process and serves as a remote heap-corruption primitive. This vulnerability affects Node.js 26.x and 24.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-75806 | libcrypto3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-123871 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | Node.js discloses proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. CVE-2026-48615 established that a proxy credential must not appear in a Node.js error message and redacted the username and password from ProxyConfig.href, but that fix missed four error paths in the same subsystem, one of them inside the same constructor, which interpolate the raw proxy URL, credentials included, into an ERR_PROXY_INVALID_CONFIG message. The proxy URL comes from the environment, but the defect is the sink: a secret that Node.js redacts everywhere else is emitted verbatim into a much wider audience than the process environment, such as stderr, container logs, log aggregation, and crash reporting services. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-123867 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })` but no server certificate in that SNI context, the per-host client CA is never installed and the handshake falls back to the default client CA. In `src/crypto/crypto_tls.cc`, `CertCbDone` installs the SNI context's CA only when `setSniContext` succeeds, but `setSniContext` returns `false` for a context with no server certificate, so a CA-only SNI context silently keeps the default CA. A client holding a certificate trusted by the default CA, but not the protected CA, can therefore complete mTLS to the protected hostname and read its response even with `requestCert` and `rejectUnauthorized` enabled, while a client certified by the protected CA is rejected. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-100407 | git | 2.54.0-r0 | Git for Windows is the Windows port of Git. From 2.44.0.windows.1 until 2.55.0.windows.3, the git-credential-wincred store operation in contrib/credential/wincred/git-credential-wincred.c uses _scwprintf() to size a formatted wide-character credential buffer without space for the terminating NUL when both password and oauth_refresh_token are present. The operation also passes a byte count to _snwprintf_s() where a wide-character count is required, allowing the terminator to be written one WCHAR past the heap allocation before CredWriteW() persists the credential. The resulting fixed two-byte NUL overwrite can terminate the helper with Windows heap-corruption status and can cause git credential approve to report success even though the OAuth credential was not stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100408 | git | 2.54.0-r0 | Git for Windows is the Windows port of Git. From 2.43.0.windows.1 until 2.55.0.windows.3, when a matching git:* credential exists in Windows Credential Manager and a git-credential-wincred erase input includes a password field, the operation in contrib/credential/wincred/git-credential-wincred.c allocates a buffer of exactly CredentialBlobSize bytes in match_cred_password() and then uses wcsncpy_s() to copy the corresponding number of wide characters plus a terminating NUL. The destination capacity is also supplied in bytes instead of WCHAR elements, allowing a fixed two-byte NUL write past the allocation before the password comparison determines whether CredDeleteW() should remove the credential; erase without a password field does not enter this comparison path. The helper can terminate with Windows heap-corruption status, and git credential reject can appear successful while the rejected credential remains stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-106072 | node | 24.19.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`. `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| MEDIUM | CVE-2026-75804 | libcrypto3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libssl3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-123868 | node | 24.19.0 | 24.22.3, 26.13.1 | An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-42772 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-123875 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | A NULL pointer dereference in Node.js HTTP/2 lets an unauthenticated client crash the server, over both TLS and cleartext, by cancelling file downloads. When the server serves a file with stream.respondWithFile() or stream.respondWithFD() and the client cancels the request, a StreamPipe used for the transfer is torn down in an order that leaves a NULL pointer which is then dereferenced, aborting the process. No crafted frames are needed, and a handful of cancelled requests against a default file-serving handler is enough. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-75806 | libssl3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libcrypto3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libssl3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libcrypto3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-105481 | node | 24.19.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. This is an incomplete fix of CVE-2026-48931. The guard that destroys idle keep-alive sockets when unexpected data arrives only runs when the event loop polls for I/O. If an unsolicited response has already reached the socket but has not been read yet when the socket is handed to a new request, for example because the event loop was busy with synchronous work, the guard is removed without seeing it and the data is parsed as the response to the new request. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| MEDIUM | CVE-2026-75805 | libssl3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| LOW | CVE-2026-123829 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | A Permission Model bypass in Node.js recursive file watching discloses the names of files and directories the process is not permitted to read. On macOS and Windows, fs.watch() and fs.promises.watch() in recursive mode are backed by the native libuv watcher: FSEventWrap::Start checks kFileSystemRead only once, on the watched root, and FSEventWrap::OnEvent then forwards every filename libuv reports (relative paths at any depth) to the JavaScript callback without checking that each path is covered by the read grant. Code running under --permission with an exact read grant on a directory can therefore learn names such as sub/secret.txt even though readdir on that subdirectory is denied. The flaw exposes names and timing metadata, not file contents, and requires macOS or Windows plus files created under the watched directory by another actor. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| LOW | CVE-2026-123862 | node | 24.19.0 | 22.23.5, 24.22.3, 26.13.1 | An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write's callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream's error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| LOW | CVE-2026-106073 | node | 24.19.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks. This is an incomplete fix of CVE-2026-21715, which only covered `fs.realpathSync.native()`. As a result, code running under `--permission` with restricted `--allow-fs-read` can still use `fs.realpathSync()` to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| LOW | CVE-2026-54875 | libcrypto3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libssl3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libcrypto3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libssl3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libcrypto3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libssl3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libssl3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libcrypto3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed |
ghcr.io/voxpupuli/onceover
Downloads
ghcr.io/voxpupuli/onceover:latest (2026-09-02)
Trivy
CRITICAL 5
HIGH 53
MEDIUM 80
LOW 65
UNKNOWN 2
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-42257 | net-imap | 0.3.9 | ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | net-imap: Net::IMAP: Arbitrary IMAP command injection via CRLF sequences in unvalidated input — Ruby |
| CRITICAL | CVE-2026-123158 | openssh-keygen | 10.2_p1-r0 | 10.2_p1-r1 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-123158 | openssh-client-default | 10.2_p1-r0 | 10.2_p1-r1 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-123158 | openssh-client-common | 10.2_p1-r0 | 10.2_p1-r1 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r0 | 1.2.1-r0 | brotli: Out-of-Bounds Write in Google Brotli Decoder — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8925 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Double-free vulnerability in SASL authentication — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8458 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Unauthorized connection reuse due to a logical error — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8286 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Insecure connection establishment due to TLS configuration mismatch — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-12064 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: SSH host verification bypass when using schemeless URLs with SFTP/SCP — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-11586 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Denial of Service via WebSocket PING flood — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-11352 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: curl/libcurl: Remote denial of service via QUIC UDP receive function vulnerability — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-114466 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-111760 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-105437 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-19445 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | python: Use-after-free of a server-side SSLContext when sni_callback switches contexts — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-82049 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: File modification and content disclosure via crafted archives — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-19553 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | python: python: Certificate verification bypass via missing server_hostname validation in SSLContext.wrap_bio() — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-19445 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | python: Use-after-free of a server-side SSLContext when sni_callback switches contexts — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-19553 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | python: python: Certificate verification bypass via missing server_hostname validation in SSLContext.wrap_bio() — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-82049 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: File modification and content disclosure via crafted archives — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-114466 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-111760 | git | 2.52.0-r0 | 2.52.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-105437 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-113351 | libexpat | 2.8.4-r0 | 2.10.0-r0 | expat: expat: Denial of Service via improper memory tracking in XML_ParserReset — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-115506 | libexpat | 2.8.4-r0 | 2.10.0-r0 | expat: expat: Denial of Service via delayed entity amplification detection — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-117610 | libexpat | 2.8.4-r0 | 2.10.0-r0 | expat: expat: Denial of Service via NULL pointer dereference in external entity parsing — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-118370 | libexpat | 2.8.4-r0 | 2.10.0-r0 | expat: expat: Denial of Service via integer overflow during XML attribute parsing — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-77214 | libexpat | 2.8.4-r0 | 2.9.0-r0 | expat: expat: Information disclosure via heap buffer over-read in XML_ParseBuffer — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-93990 | libexpat | 2.8.4-r0 | 2.8.5-r0 | expat: Expat: XML Injection via Malformed UTF-16 Input — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-107891 | musl | 1.2.5-r23 | 1.2.5-r24 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.5-r23 | 1.2.5-r24 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-103111 | pcre2 | 10.48-r0 | 10.49-r0 | pcre2: pcre2: Out-of-bounds write via crafted regular expression — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-19445 | pyc | 3.12.14-r0 | 3.12.15-r0 | python: Use-after-free of a server-side SSLContext when sni_callback switches contexts — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-19553 | pyc | 3.12.14-r0 | 3.12.15-r0 | python: python: Certificate verification bypass via missing server_hostname validation in SSLContext.wrap_bio() — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-82049 | pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: File modification and content disclosure via crafted archives — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-19445 | python3 | 3.12.14-r0 | 3.12.15-r0 | python: Use-after-free of a server-side SSLContext when sni_callback switches contexts — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-19553 | python3 | 3.12.14-r0 | 3.12.15-r0 | python: python: Certificate verification bypass via missing server_hostname validation in SSLContext.wrap_bio() — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-82049 | python3 | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: File modification and content disclosure via crafted archives — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-9547 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Man-in-the-middle attack via SSH host key bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-92392 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: HTTP/2 upload Use-After-Free — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8927 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: Information disclosure due to uncleared proxy authentication state — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-41316 | erb | 4.0.2 | ~> 4.0.3.1, ~> 4.0.4.1, ~> 6.0.1.1, >= 6.0.4 | erb: ERB: Arbitrary code execution via deserialization bypass — Ruby |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | zlib: zlib: Heap buffer overflow in gz_vacate() allows arbitrary code execution — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-42246 | net-imap | 0.3.9 | ~> 0.3.10, ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | net-imap: ruby: Net::IMAP: Information disclosure via man-in-the-middle attack bypassing TLS — Ruby |
| HIGH | CVE-2026-42258 | net-imap | 0.3.9 | ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | ruby/net-imap: ruby: Net::IMAP: IMAP Command Injection via Symbol Arguments — Ruby |
| HIGH | CVE-2026-42245 | net-imap | 0.3.9 | ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | ruby: net-imap: Net::IMAP: Denial of Service via crafted IMAP responses — Ruby |
| HIGH | CVE-2026-126080 | activesupport | 8.1.3.1 | 8.1.4.1, 8.0.5.2 | activesupport: Active Support: Denial of Service via unescaped regular expressions in safe_constantize — Ruby |
| HIGH | CVE-2026-80212 | resolv | 0.2.3 | ~> 0.3.2, >= 0.7.2 | resolv: resolv gem: Denial of Service via uncontrolled memory growth from crafted DNS responses — Ruby |
| HIGH | GHSA-8474-xrp6-wh69 | activesupport | 8.1.3.1 | ~> 8.0.5, >= 8.0.5.2, >= 8.1.4.1 | Possible DoS vulnerability in Active Support safe_constantize — Ruby |
| HIGH | CVE-2026-9547 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Man-in-the-middle attack via SSH host key bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-92392 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: HTTP/2 upload Use-After-Free — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8927 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: Information disclosure due to uncleared proxy authentication state — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8925 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Double-free vulnerability in SASL authentication — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8458 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Unauthorized connection reuse due to a logical error — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8286 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Insecure connection establishment due to TLS configuration mismatch — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-12064 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: SSH host verification bypass when using schemeless URLs with SFTP/SCP — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-11586 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Denial of Service via WebSocket PING flood — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| HIGH | CVE-2026-11352 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: curl/libcurl: Remote denial of service via QUIC UDP receive function vulnerability — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | GHSA-r6vf-943r-2wvw | minitar | 1.1.0 | ~> 1.1.1, >= 1.2.0 | minitar path traversal vulnerability on Windows with a maliciously crafted tarball — Ruby |
| MEDIUM | CVE-2026-87910 | pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: Security filter bypass allows arbitrary file write — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-19672 | pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: Directory traversal allows creation of empty directories outside extraction destination — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-17084 | pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python stringprep module: Incorrect domain name processing breaks IDNA interoperability — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114583 | python3 | 3.12.14-r0 | 3.12.16-r0 | python: python: Arbitrary file write via tarfile extraction filter bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-115557 | python3 | 3.12.14-r0 | 3.12.16-r0 | python: Distrust compromised eMudhra intermediate certificates in Python ssl module — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-12345 | python3 | 3.12.14-r0 | 3.12.16-r0 | python: python: Arbitrary file deletion via race condition during temporary directory cleanup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-15310 | python3 | 3.12.14-r0 | 3.12.15-r0 | python: Python: Denial of Service via crafted zip file memory pre-allocation — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-15806 | pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python: Information disclosure due to incorrect URL scheme matching — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-15310 | pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python: Denial of Service via crafted zip file memory pre-allocation — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-12345 | pyc | 3.12.14-r0 | 3.12.16-r0 | python: python: Arbitrary file deletion via race condition during temporary directory cleanup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-115557 | pyc | 3.12.14-r0 | 3.12.16-r0 | python: Distrust compromised eMudhra intermediate certificates in Python ssl module — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114583 | pyc | 3.12.14-r0 | 3.12.16-r0 | python: python: Arbitrary file write via tarfile extraction filter bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-47240 | net-imap | 0.3.9 | ~> 0.5.15, >= 0.6.4.1 | net-imap: Net::IMAP: Command injection via non-synchronizing literals — Ruby |
| MEDIUM | CVE-2026-47242 | net-imap | 0.3.9 | ~> 0.5.15, >= 0.6.4.1 | net-imap: Net::IMAP: Arbitrary IMAP command injection due to improper input validation — Ruby |
| MEDIUM | CVE-2026-80213 | resolv | 0.2.3 | ~> 0.3.2, >= 0.7.2 | resolv: Resolv gem: DNS allowlist and egress bypass, and cache poisoning via crafted hostnames — Ruby |
| MEDIUM | CVE-2026-102633 | libexpat | 2.8.4-r0 | 2.9.0-r0 | expat: expat: Denial of Service via integer overflow in expat_realloc — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114583 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.16-r0 | python: python: Arbitrary file write via tarfile extraction filter bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-115557 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.16-r0 | python: Distrust compromised eMudhra intermediate certificates in Python ssl module — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-12345 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.16-r0 | python: python: Arbitrary file deletion via race condition during temporary directory cleanup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-15310 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | python: Python: Denial of Service via crafted zip file memory pre-allocation — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-87910 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: Security filter bypass allows arbitrary file write — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-19672 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: Directory traversal allows creation of empty directories outside extraction destination — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-17084 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python stringprep module: Incorrect domain name processing breaks IDNA interoperability — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-15806 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python: Information disclosure due to incorrect URL scheme matching — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-15310 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | python: Python: Denial of Service via crafted zip file memory pre-allocation — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-12345 | python3-pyc | 3.12.14-r0 | 3.12.16-r0 | python: python: Arbitrary file deletion via race condition during temporary directory cleanup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-115557 | python3-pyc | 3.12.14-r0 | 3.12.16-r0 | python: Distrust compromised eMudhra intermediate certificates in Python ssl module — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114583 | python3-pyc | 3.12.14-r0 | 3.12.16-r0 | python: python: Arbitrary file write via tarfile extraction filter bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-15806 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | python: Python: Information disclosure due to incorrect URL scheme matching — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-17084 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | python: Python stringprep module: Incorrect domain name processing breaks IDNA interoperability — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-19672 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: Directory traversal allows creation of empty directories outside extraction destination — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-87910 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: Security filter bypass allows arbitrary file write — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | Improper Restriction of Operations within the Bounds of a Memory Buffe ... — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-126075 | activesupport | 8.1.3.1 | 8.1.4.1 | activesupport: Active Support: Cross-site scripting via MessagePack deserialization — Ruby |
| MEDIUM | CVE-2026-87910 | python3 | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: Security filter bypass allows arbitrary file write — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-19672 | python3 | 3.12.14-r0 | 3.12.15-r0 | python: Python tarfile module: Directory traversal allows creation of empty directories outside extraction destination — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-17084 | python3 | 3.12.14-r0 | 3.12.15-r0 | python: Python stringprep module: Incorrect domain name processing breaks IDNA interoperability — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | GHSA-2w9f-fxwj-w2qf | activesupport | 8.1.3.1 | >= 8.1.4.1 | Possible XSS vulnerability in Active Support MessagePack serializer — Ruby |
| MEDIUM | CVE-2026-126348 | addressable | 2.9.0 | 2.9.1 | CVE-2026-126348 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| MEDIUM | CVE-2026-126350 | addressable | 2.9.0 | >= 2.9.1 | CVE-2026-126350 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| MEDIUM | CVE-2026-126351 | addressable | 2.9.0 | >= 2.9.1 | CVE-2026-126351 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| MEDIUM | CVE-2026-126352 | addressable | 2.9.0 | >= 2.9.1 | CVE-2026-126352 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| MEDIUM | CVE-2026-126354 | addressable | 2.9.0 | 2.9.1 | CVE-2026-126354 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| MEDIUM | GHSA-4w5q-wg7v-w6gp | addressable | 2.9.0 | >= 2.9.1 | Regular Expression Denial of Service in Addressable templates with several exploded variables — Ruby |
| MEDIUM | GHSA-8gmh-2hhj-2hv9 | addressable | 2.9.0 | >= 2.9.1 | Addressable URI normalization resolves some dotted path segments to the wrong path — Ruby |
| MEDIUM | GHSA-9crm-g4mf-wc5j | addressable | 2.9.0 | >= 2.9.1 | Addressable display_uri can show misleading hosts with invalid Punycode A-labels — Ruby |
| MEDIUM | CVE-2026-15806 | python3 | 3.12.14-r0 | 3.12.15-r0 | python: Python: Information disclosure due to incorrect URL scheme matching — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9545 | libcurl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure via cached SSL session and early data — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-92388 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: FTP wildcard write callback mixup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9080 | libcurl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Use-after-free via curl_easy_pause() in CURLMOPT_SOCKETFUNCTION callback — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9079 | libcurl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure due to failure to clear proxy authentication credentials — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8932 | libcurl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Security feature bypass due to improper mTLS connection reuse — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8926 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure via incorrect .netrc password lookup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8924 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Cookie injection via malicious HTTP server using super cookies — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-82208 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Improper certificate validation when using wolfSSL CA cache — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-19931 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via incorrect connection reuse with Negotiate authentication — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-11856 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure via incorrect Digest authentication header reuse — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-11564 | libcurl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Certificate validation bypass due to incorrect connection reuse — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-10536 | libcurl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Use-after-free vulnerability leading to Denial of Service — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114467 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-113408 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114469 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114467 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-113408 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9546 | curl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure due to persistent Referer header — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9545 | curl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure via cached SSL session and early data — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-92388 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: FTP wildcard write callback mixup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9080 | curl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Use-after-free via curl_easy_pause() in CURLMOPT_SOCKETFUNCTION callback — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9079 | curl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure due to failure to clear proxy authentication credentials — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8932 | curl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Security feature bypass due to improper mTLS connection reuse — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8926 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure via incorrect .netrc password lookup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8924 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Cookie injection via malicious HTTP server using super cookies — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-82208 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Improper certificate validation when using wolfSSL CA cache — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-19931 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via incorrect connection reuse with Negotiate authentication — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-11856 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure via incorrect Digest authentication header reuse — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-11564 | curl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Certificate validation bypass due to incorrect connection reuse — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-10536 | curl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Use-after-free vulnerability leading to Denial of Service — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9546 | libcurl | 8.20.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure due to persistent Referer header — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87864 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: IMAP APPEND plus CRLF conversion command injection — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-13608 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Authentication bypass in OpenLDAP SASL negotiation via Man-in-the-Middle (MITM) attack — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-18924 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Use-after-free in HTTP/2 Server Push with shared connections — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-80229 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Memory corruption vulnerability via OpenSSL 3 provider use-after-free — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-80230 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Public key pinning bypass allows unauthenticated connections — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-80231 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Incorrect HTTPS connection reuse with Native CA Store — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-80255 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure due to secure cookie attribute bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-82209 | curl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via improper Public Suffix List boundary check — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86409 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: stale SigV4 headers sent unintended — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86410 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: redirect to SFTP or SCP bypasses host verification — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2024-3220 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.16-r0 | python: Default mimetype known files writeable on Windows — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86411 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: FTP connection reuse inherits client-certificate — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86412 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie erases cookie jar — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86413 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: Negotiate credentials sent to redirected origin — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86414 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: leaking host credentials to HTTP proxy — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86415 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: auto client cert connection reuse mixup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87861 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: cross-origin reuse of a Negotiate connection — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87865 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: knownhost callback mismatches key as missing — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-47241 | net-imap | 0.3.9 | ~> 0.5.15, >= 0.6.4.1 | net-imap: rubygem-net-imap: Net::IMAP: Denial of Service via malformed command input — Ruby |
| LOW | CVE-2026-87866 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: wolfSSL public-key pinning bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92386 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie aborts cookie jar load — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92387 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: never-ending loop via server response omission — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92389 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: TFTP direction confusion — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92390 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: -J no-clobber guarantee bypassed with 103 early hints — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92391 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: curl_mime_free stack overflow by recursion — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-94265 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: Authorization: Negotiate sent to foreign origin — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-94266 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: password leak in CURLINFO_EFFECTIVE_URL — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | GHSA-539f-xcgw-2gjg | addressable | 2.9.0 | >= 2.9.1 | Addressable display_uri can show misleading hosts containing bidi and invisible characters — Ruby |
| LOW | CVE-2026-126349 | addressable | 2.9.0 | 2.9.1 | CVE-2026-126349 affecting package rubygem-addressable for versions less than 2.9.2-1 — Ruby |
| LOW | CVE-2026-87863 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: Hsts Response Erases Persisted Entries — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87862 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: HSTS cache import drops longer-lived child — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-107928 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: info leak uploading over WebSockets with GnuTLS — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-107929 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: local interface connection reuse mixup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87862 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: HSTS cache import drops longer-lived child — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2024-3220 | python3 | 3.12.14-r0 | 3.12.16-r0 | python: Default mimetype known files writeable on Windows — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86413 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: Negotiate credentials sent to redirected origin — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86412 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie erases cookie jar — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86411 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: FTP connection reuse inherits client-certificate — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86410 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: redirect to SFTP or SCP bypasses host verification — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86409 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: stale SigV4 headers sent unintended — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-82209 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via improper Public Suffix List boundary check — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-80255 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure due to secure cookie attribute bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-80231 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Incorrect HTTPS connection reuse with Native CA Store — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-80230 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Public key pinning bypass allows unauthenticated connections — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-80229 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Memory corruption vulnerability via OpenSSL 3 provider use-after-free — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-18924 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: libcurl: Use-after-free in HTTP/2 Server Push with shared connections — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2024-3220 | pyc | 3.12.14-r0 | 3.12.16-r0 | python: Default mimetype known files writeable on Windows — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-13608 | libcurl | 8.20.0-r0 | 8.22.0-r0 | curl: curl: Authentication bypass in OpenLDAP SASL negotiation via Man-in-the-Middle (MITM) attack — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-107929 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: local interface connection reuse mixup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-107928 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: info leak uploading over WebSockets with GnuTLS — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87863 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: Hsts Response Erases Persisted Entries — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87864 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: IMAP APPEND plus CRLF conversion command injection — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87865 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: knownhost callback mismatches key as missing — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87866 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: wolfSSL public-key pinning bypass — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2024-3220 | python3-pyc | 3.12.14-r0 | 3.12.16-r0 | python: Default mimetype known files writeable on Windows — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92386 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie aborts cookie jar load — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92387 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: never-ending loop via server response omission — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92389 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: TFTP direction confusion — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92390 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: -J no-clobber guarantee bypassed with 103 early hints — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-92391 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: curl_mime_free stack overflow by recursion — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-94265 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: Authorization: Negotiate sent to foreign origin — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-94266 | curl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: password leak in CURLINFO_EFFECTIVE_URL — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-87861 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: cross-origin reuse of a Negotiate connection — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86415 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: auto client cert connection reuse mixup — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| LOW | CVE-2026-86414 | libcurl | 8.20.0-r0 | 8.23.0-r0 | curl: curl: leaking host credentials to HTTP proxy — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| UNKNOWN | CVE-2026-80256 | libcurl | 8.20.0-r0 | 8.22.0-r0 | Title Not Available — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
| UNKNOWN | CVE-2026-80256 | curl | 8.20.0-r0 | 8.22.0-r0 | Title Not Available — ghcr.io/voxpupuli/onceover:latest (alpine 3.23.4) |
Grype
CRITICAL 50
HIGH 98
MEDIUM 41
LOW 15
UNKNOWN 2
NVD/CPE filtered 81
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-115557 | python3-pyc | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-115557 | python3 | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-115557 | pyc | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-18924 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-18924 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-11564 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-11564 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-10536 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-10536 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | GHSA-22mf-ggw7-pxfx | ruby | 3.2.11 | 3.3.13 | Integer overflow in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | CVE-2026-8924 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8924 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87861 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86414 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87861 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86414 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-92388 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-92388 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | GHSA-7x2q-68qv-6p8x | ruby | 3.2.11 | 3.3.14 | Double free in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-3p8q-wmhx-vm2w | ruby | 3.2.11 | 3.3.14 | Heap buffer overflow in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-34m4-m9fh-gqp5 | ruby | 3.2.11 | 3.3.14 | Heap buffer overflow in case conversion of strings — /usr/local/bin/ruby |
| CRITICAL | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86411 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86411 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8926 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8926 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8927 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8927 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87866 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87866 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | GHSA-gfj3-8wj9-qx8p | ruby | 3.2.11 | 3.3.13 | Double free in regular expression parsing — /usr/local/bin/ruby |
| CRITICAL | CVE-2026-19445 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-19445 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-19445 | python3 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-19445 | pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-115557 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86413 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-94265 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r0 | 1.2.1-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-19931 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8925 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8925 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | GHSA-qm4g-8pfh-6996 | ruby | 3.2.11 | 3.3.13 | Overflow of internal identifiers in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | CVE-2026-19931 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86413 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-9079 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-11856 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-11856 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-9079 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-94265 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86415 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-117610 | libexpat | 2.8.4-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-93990 | libexpat | 2.8.4-r0 | 2.8.5-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86415 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-12064 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-12064 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-102633 | libexpat | 2.8.4-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-118370 | libexpat | 2.8.4-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82208 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-wpqw-5qxg-m68r | ruby | 3.2.11 | 3.3.14 | Out-of-bounds read in case-insensitive regular expression matching — /usr/local/bin/ruby |
| HIGH | CVE-2026-80255 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80255 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9080 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9080 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-113351 | libexpat | 2.8.4-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-13608 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-13608 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-115506 | libexpat | 2.8.4-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92392 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-19553 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-19553 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92387 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-87fm-7w84-j2px | ruby | 3.2.11 | 3.3.14 | Integer overflow in case conversion of strings — /usr/local/bin/ruby |
| HIGH | GHSA-7whj-cfh7-xgm4 | ruby | 3.2.11 | 3.3.14 | Heap buffer overflow in Regexp#to_s — /usr/local/bin/ruby |
| HIGH | CVE-2026-123158 | openssh-client-common | 10.2_p1-r0 | 10.2_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-client-default | 10.2_p1-r0 | 10.2_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-82049 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82049 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82049 | python3 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82049 | pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-103111 | pcre2 | 10.48-r0 | 10.49-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9545 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9545 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-vcgp-9326-pqcp | net-imap | 0.3.9 | 0.3.10 | net-imap vulnerable to STARTTLS stripping via invalid response timing — /usr/local/lib/ruby/gems/3.2.0/specifications/net-imap-0.3.9.gemspec |
| HIGH | CVE-2026-8286 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-8286 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-77214 | libexpat | 2.8.4-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9547 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9547 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-keygen | 10.2_p1-r0 | 10.2_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-80230 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80230 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82209 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82209 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-8932 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-8932 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-105437 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-105437 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82208 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9546 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9546 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92387 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87862 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87862 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-11352 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107929 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107929 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-11352 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107928 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107928 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92389 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92389 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86410 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86410 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87864 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87864 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86412 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87863 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-8474-xrp6-wh69 | activesupport | 8.1.3.1 | 8.1.4.1 | Active Support: Possible DoS vulnerability in Active Support safe_constantize — /usr/local/bundle/specifications/activesupport-8.1.3.1.gemspec |
| HIGH | CVE-2026-92386 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86412 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-11586 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-11586 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92386 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87863 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80229 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80229 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80231 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.5-r23 | 1.2.5-r24 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl | 1.2.5-r23 | 1.2.5-r24 | /lib/apk/db/installed |
| HIGH | CVE-2026-92390 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92390 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80231 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-94266 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-94266 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87865 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86409 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-19553 | pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-19553 | python3 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86409 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92391 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92391 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-q339-8rmv-2mhv | erb | 4.0.2 | 4.0.3.1 | ERB has an @_init deserialization guard bypass via def_module / def_method / def_class — /usr/local/lib/ruby/gems/3.2.0/specifications/default/erb-4.0.2.gemspec |
| HIGH | CVE-2026-92392 | libcurl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87865 | curl | 8.20.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-17084 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-17084 | python3 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114583 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114583 | python3-pyc | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114583 | python3 | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114583 | pyc | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-2w9f-fxwj-w2qf | activesupport | 8.1.3.1 | 8.1.4.1 | Active Support: Possible XSS vulnerability in Active Support MessagePack serializer — /usr/local/bundle/specifications/activesupport-8.1.3.1.gemspec |
| MEDIUM | CVE-2026-12345 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-15806 | pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-12345 | python3-pyc | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-17084 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-8gmh-2hhj-2hv9 | addressable | 2.9.0 | 2.9.1 | Addressable URI normalization resolves some dotted path segments to the wrong path — /usr/local/bundle/specifications/addressable-2.9.0.gemspec |
| MEDIUM | GHSA-9crm-g4mf-wc5j | addressable | 2.9.0 | 2.9.1 | Addressable display_uri can show misleading hosts with invalid Punycode A-labels — /usr/local/bundle/specifications/addressable-2.9.0.gemspec |
| MEDIUM | CVE-2026-114469 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-46q3-7gv7-qmgg | net-imap | 0.3.9 | 0.5.15 | Net::IMAP: Command Injection via ID command argument — /usr/local/lib/ruby/gems/3.2.0/specifications/net-imap-0.3.9.gemspec |
| MEDIUM | GHSA-75xq-5h9v-w6px | net-imap | 0.3.9 | 0.4.24 | net-imap vulnerable to command Injection via unvalidated Symbol inputs — /usr/local/lib/ruby/gems/3.2.0/specifications/net-imap-0.3.9.gemspec |
| MEDIUM | GHSA-pvgc-g7gj-pv6h | ruby | 3.2.11 | 3.3.14 | Out-of-bounds read in case-insensitive backreference matching — /usr/local/bin/ruby |
| MEDIUM | CVE-2026-15806 | python3 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-15806 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-15806 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-87910 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-87910 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-87910 | python3 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-87910 | pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-19672 | pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-19672 | python3 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-19672 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-19672 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-8p34-64r3-mwg8 | net-imap | 0.3.9 | 0.5.15 | Net::IMAP: Command Injection via non-synchronizing literal in "raw" argument — /usr/local/lib/ruby/gems/3.2.0/specifications/net-imap-0.3.9.gemspec |
| MEDIUM | CVE-2026-12345 | python3 | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-12345 | pyc | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-9f42-57jx-vpp3 | addressable | 2.9.0 | 2.9.1 | Addressable: Regular Expression Denial of Service in templates with multiple variables — /usr/local/bundle/specifications/addressable-2.9.0.gemspec |
| MEDIUM | GHSA-hm49-wcqc-g2xg | net-imap | 0.3.9 | 0.4.24 | net-imap vulnerable to command Injection via "raw" arguments to multiple commands — /usr/local/lib/ruby/gems/3.2.0/specifications/net-imap-0.3.9.gemspec |
| MEDIUM | GHSA-j82w-28jv-3pmj | addressable | 2.9.0 | 2.9.1 | Addressable: Regular Expression Denial of Service in templates with certain exploded expressions — /usr/local/bundle/specifications/addressable-2.9.0.gemspec |
| MEDIUM | GHSA-qq38-m9mg-xjj5 | addressable | 2.9.0 | 2.9.1 | Addressable: Denial of service in URI path normalization — /usr/local/bundle/specifications/addressable-2.9.0.gemspec |
| MEDIUM | CVE-2026-8458 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-17084 | pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-8458 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| LOW | CVE-2024-3220 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| LOW | CVE-2024-3220 | python3-pyc | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| LOW | CVE-2024-3220 | python3 | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| LOW | CVE-2024-3220 | pyc | 3.12.14-r0 | 3.12.16-r0 | /lib/apk/db/installed |
| LOW | GHSA-c4fp-cxrr-mj66 | net-imap | 0.3.9 | 0.5.15 | Net::IMAP: Denial of Service via incomplete raw argument validation — /usr/local/lib/ruby/gems/3.2.0/specifications/net-imap-0.3.9.gemspec |
| LOW | CVE-2026-114467 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | GHSA-539f-xcgw-2gjg | addressable | 2.9.0 | 2.9.1 | Addressable display_uri can show misleading hosts containing bidi and invisible characters — /usr/local/bundle/specifications/addressable-2.9.0.gemspec |
| LOW | CVE-2026-113408 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-113408 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | GHSA-q2mw-fvj9-vvcw | net-imap | 0.3.9 | 0.4.24 | net-imap has quadratic complexity when reading response literals — /usr/local/lib/ruby/gems/3.2.0/specifications/net-imap-0.3.9.gemspec |
| LOW | CVE-2026-15310 | python3-pycache-pyc0 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-15310 | python3-pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-15310 | python3 | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-15310 | pyc | 3.12.14-r0 | 3.12.15-r0 | /lib/apk/db/installed |
| UNKNOWN | CVE-2026-80256 | curl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| UNKNOWN | CVE-2026-80256 | libcurl | 8.20.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
Filtered NVD/CPE matches (81)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-107496 | libcrypto3 | 3.5.8-r0 | Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely. Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service. CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns. The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option. The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected. The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely. FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107496 | libssl3 | 3.5.8-r0 | Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely. Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service. CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns. The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option. The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected. The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely. FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95691 | libcrypto3 | 3.5.8-r0 | Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95691 | libssl3 | 3.5.8-r0 | Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119379 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with the session extension contains a heap buffer overflow vulnerability in sqlite3changeset_apply() that allows attackers to corrupt heap memory by supplying crafted changesets. Attackers can repeat a table name in a second changeset block with a larger column count, causing sessionUpdateFind() to memset past the undersized aUpdateMask allocation. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-88823 | libcrypto3 | 3.5.8-r0 | Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-88823 | libssl3 | 3.5.8-r0 | Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libssl3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119373 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5MergeRowidLists() that undersizes the output buffer when merging detail=none prefix doclists. Attackers who can populate a detail=none FTS5 table with negative rowids and run a prefix MATCH query can write past the allocation, corrupting heap memory and crashing the process. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119374 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5DoSecureDelete() that allows attackers to write past the leaf page buffer via crafted footer key offsets. Attackers can supply a database file with a corrupted FTS5 index that, when deleted from with secure-delete enabled, corrupts heap memory and crashes the application. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-132825 | ruby | 3.2.11 | 3.3.14, 3.4.13, 4.0.10 | Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. — /usr/local/bin/ruby |
| HIGH | CVE-2026-54873 | libcrypto3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-54873 | libssl3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119586 | sqlite-libs | 3.53.4-r0 | SQLite command-line shell through 3.54.1 contains a command injection vulnerability in the .recover command that emits attacker-planted dot-commands stored in sqlite_schema.sql values verbatim. Attackers can craft a database whose schema holds a valid CREATE statement followed by a .shell or .system line, executing OS commands when victims pipe .recover output into sqlite3. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libcrypto3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libssl3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libssl3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libcrypto3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95692 | libssl3 | 3.5.8-r0 | Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected. Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV. CWE: CWE-125: Out-of-bounds Read Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length. The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery. Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application. FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95692 | libcrypto3 | 3.5.8-r0 | Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected. Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV. CWE: CWE-125: Out-of-bounds Read Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length. The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery. Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application. FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libcrypto3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libssl3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100407 | git | 2.52.0-r0 | Git for Windows is the Windows port of Git. From 2.44.0.windows.1 until 2.55.0.windows.3, the git-credential-wincred store operation in contrib/credential/wincred/git-credential-wincred.c uses _scwprintf() to size a formatted wide-character credential buffer without space for the terminating NUL when both password and oauth_refresh_token are present. The operation also passes a byte count to _snwprintf_s() where a wide-character count is required, allowing the terminator to be written one WCHAR past the heap allocation before CredWriteW() persists the credential. The resulting fixed two-byte NUL overwrite can terminate the helper with Windows heap-corruption status and can cause git credential approve to report success even though the OAuth credential was not stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100408 | git | 2.52.0-r0 | Git for Windows is the Windows port of Git. From 2.43.0.windows.1 until 2.55.0.windows.3, when a matching git:* credential exists in Windows Credential Manager and a git-credential-wincred erase input includes a password field, the operation in contrib/credential/wincred/git-credential-wincred.c allocates a buffer of exactly CredentialBlobSize bytes in match_cred_password() and then uses wcsncpy_s() to copy the corresponding number of wide characters plus a terminating NUL. The destination capacity is also supplied in bytes instead of WCHAR elements, allowing a fixed two-byte NUL write past the allocation before the password comparison determines whether CredDeleteW() should remove the credential; erase without a password field does not enter this comparison path. The helper can terminate with Windows heap-corruption status, and git credential reject can appear successful while the rejected credential remains stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-116566 | python3 | 3.12.14-r0 | socket.getaddrinfo() previously accepted null bytes within *host* and *port* parameters which can cause the values to be silently truncated. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-58055 | nghttp2-libs | 1.69.0-r0 | nghttp2's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also carries a Content-Length header and body onto reusable keep-alive backend connections, re-adding the Upgrade and Connection headers while passing Content-Length verbatim. A backend that resolves the resulting ambiguous message in the attacker's favor enables HTTP request/response smuggling and cross-client response-queue poisoning. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119378 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a use-after-free vulnerability in the R-Tree extension that allows attackers to make applications use freed heap memory by manipulating the %_node shadow table. Attackers can supply a database declaring %_node WITHOUT ROWID or with a RAISE(IGNORE) trigger so nodeWrite() hashes nodes as 0, crashing the process after node splits. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-88822 | libssl3 | 3.5.8-r0 | Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-88822 | libcrypto3 | 3.5.8-r0 | Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75806 | libcrypto3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119375 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains an information disclosure vulnerability that allows attackers to read uninitialized page-cache memory by supplying a WAL file with an undersized page size. Attackers can craft a database and WAL file whose oversized record payload makes queries like substr() return stale bytes, disclosing other table rows and internal pointers. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119371 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH nesting limit because common table expressions are not counted against it. Attackers can supply a WITH clause chaining tens of thousands of CTEs, via plain SQL or a view in an untrusted database file, causing unbounded selectExpander() recursion that crashes the process. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119372 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with FTS3/FTS4 and SQLITE_ENABLE_FTS3_PARENTHESIS contains a use-after-free vulnerability in fts3BestSnippet() caused by dangling cached position-list pointers. Attackers can run a full-text MATCH query combining OR and NEAR operators with snippet() to read freed heap memory and crash the process. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-115559 | python3 | 3.12.14-r0 | IMAP4.starttls() wraps the socket in TLS but leaves self._readbuf, imaplib's own read-ahead buffer, untouched. Any plaintext bytes that arrived in the same recv() as the tagged OK to STARTTLS are returned by readline() after the handshake, so the client treats them as the first responses on the protected channel. A network attacker who cannot break TLS can append forged lines after the server's OK, let the handshake complete with the real server and a valid certificate, and have the client accept the forged CAPABILITY and the forged tagged completion of the next command. This is the STARTTLS command/response injection class of CVE-2011-0411. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119376 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH limit by chaining COLLATE postfix operators. Attackers can supply roughly 175,000 chained COLLATE operators in SQL or an untrusted database view to trigger unbounded recursion in sqlite3WalkExprNN() and crash the process. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-115791 | python3 | 3.12.14-r0 | When tarfile or zipfile command line interface (CLI) is used to decompress an archive, a Python script shadowing the stdlib can be created. Then if an error occurs during decompressing the next file, the newly created Python script is executed. This is especially true if the created Python is called traceback.py. The problem is that Python adds the current directory to sys.path when python -m MODULE is run, and the archive is also decompressed in the current directory. The fix removes sys.path[0] in gzip, tarfile and zipfile command line interface to prevent shadowing standard library modules from extracted files. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119591 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a stack exhaustion vulnerability in countOfViewOptimization() that allows attackers to crash the host process via count(*) over a large multi-row VALUES clause. Attackers supplying SQL or a database file with a crafted view can trigger deeply nested TK_PLUS expressions whose recursive freeing in sqlite3ExprDeleteNN() exhausts the C stack, causing denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-6019 | python3 | 3.12.14-r0 | http.cookies.Morsel.js_output() returns an inline <script> snippet and only escapes " for JavaScript string context. It does not neutralize the HTML parser-sensitive sequence </script> inside the generated script element. Mitigation base64-encodes the cookie value to disallow escaping using cookie value. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-3446 | python3 | 3.12.14-r0 | When calling base64.b64decode() or related functions the decoding process would stop after encountering the first padded quad regardless of whether there was more information to be processed. This can lead to data being accepted which may be processed differently by other implementations. Use "validate=True" to enable stricter processing of base64 data. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75806 | libssl3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-12781 | python3 | 3.12.14-r0 | When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues. This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet. The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprecates the behavior which will be replaced with the newly recommended behavior in a future version of Python. Users are recommended to mitigate by verifying user-controlled inputs match the base64 alphabet they are expecting or verify that their application would not be affected if the b64decode() functions accepted "+" or "/" outside of altchars. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libcrypto3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libssl3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-15366 | python3 | 3.12.14-r0 | The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-15367 | python3 | 3.12.14-r0 | The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libcrypto3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libssl3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libcrypto3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libssl3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-124249 | python3 | 3.12.14-r0 | http.cookiejar.CookieJar deleted a stored cookie when a response carried an already expired Set-Cookie header for it, using the Domain and Path attributes from the header without consulting the cookie policy. A server could therefore delete cookies belonging to other domains from a shared cookie jar, such as the one used by urllib's HTTPCookieProcessor. The fix consults the cookie policy before an expired cookie may delete an existing one, as required by RFC 6265 section 5.3. — /lib/apk/db/installed | |
| LOW | CVE-2026-119377 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains an authorization bypass vulnerability in lookupName() that invokes the authorizer only for the first joined table's USING column. Attackers able to submit SQL can query a shared USING column in a RIGHT or FULL JOIN to read columns denied via sqlite3_set_authorizer() SQLITE_READ restrictions. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libcrypto3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-16052 | python3 | 3.12.14-r0 | The http.cookies.Morsel class allows separator semicolons in attribute values and includes them verbatim in all output formats. An attacker who can control these values could use this to relax the cookie's Domain or SameSite restrictions. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libssl3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libssl3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-103995 | python3 | 3.12.14-r0 | Response body and chunk parsing would handle non-hex or negative integers incorrectly which could result in misinterpreting HTTP response contents. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libcrypto3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libssl3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libcrypto3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libcrypto3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libssl3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| UNKNOWN | CVE-2026-19552 | python3 | 3.12.14-r0 | When ca_certs parameter was supplied to ssl.get_server_certificate() function, the identity of the certificate is not checked. — /lib/apk/db/installed | |
| UNKNOWN | CVE-2026-3479 | python3 | 3.12.14-r0 | DISPUTED: The project has clarified that the documentation was incorrect, and that pkgutil.get_data() has the same security model as open(). The documentation has been updated to clarify this point. There is no vulnerability in the function if following the intended security model. pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals. — /lib/apk/db/installed |
ghcr.io/voxpupuli/r10k-webhook
Downloads
ghcr.io/voxpupuli/r10k-webhook:latest (2026-08-27)
Trivy
CRITICAL 13
HIGH 107
MEDIUM 144
LOW 95
UNKNOWN 5
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-97229 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in CI/CD regular expression compiler — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-93577 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in regular expression compiler — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-54906 | concurrent-ruby | 1.3.6 | >= 1.3.7 | concurrent-ruby: rubygem-concurrent-ruby: concurrent-ruby: Synchronization flaw in ReadWriteLock allows unauthorized lock release and denial of service — Ruby |
| CRITICAL | CVE-2026-89078 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | ruby: double free issue in regular expression parser — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-110264 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in regular expression compiler — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-97229 | ruby | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in CI/CD regular expression compiler — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-93577 | ruby | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in regular expression compiler — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-89078 | ruby | 3.4.9-r0 | 3.4.12-r0 | ruby: double free issue in regular expression parser — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-110264 | ruby | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in regular expression compiler — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-123158 | openssh-keygen | 10.2_p1-r0 | 10.2_p1-r1 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-123158 | openssh-client-default | 10.2_p1-r0 | 10.2_p1-r1 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-123158 | openssh-client-common | 10.2_p1-r0 | 10.2_p1-r1 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r0 | 1.2.1-r0 | brotli: Out-of-Bounds Write in Google Brotli Decoder — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-107891 | musl | 1.2.5-r23 | 1.2.5-r24 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.5-r23 | 1.2.5-r24 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-9547 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Man-in-the-middle attack via SSH host key bypass — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-92392 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: HTTP/2 upload Use-After-Free — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8927 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: Information disclosure due to uncleared proxy authentication state — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-103111 | pcre2 | 10.47-r0 | 10.49-r0 | pcre2: pcre2: Out-of-bounds write via crafted regular expression — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-86145 | pcre2 | 10.47-r0 | 10.48-r0 | pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-89157 | pcre2 | 10.47-r0 | 10.48-r0 | pcre2: PCRE2: Out-of-bounds write via large pattern input — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-89161 | pcre2 | 10.47-r0 | 10.48-r0 | pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8925 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Double-free vulnerability in SASL authentication — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8458 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Unauthorized connection reuse due to a logical error — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8286 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Insecure connection establishment due to TLS configuration mismatch — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-6276 | libcurl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Information disclosure due to cookie leak when reusing connections with custom Host headers — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-80212 | ruby | 3.4.9-r0 | 3.4.12-r0 | resolv: resolv gem: Denial of Service via uncontrolled memory growth from crafted DNS responses — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-5773 | libcurl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Wrong file transfer due to incorrect SMB connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-12064 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: SSH host verification bypass when using schemeless URLs with SFTP/SCP — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-11586 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Denial of Service via WebSocket PING flood — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-11352 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: curl/libcurl: Remote denial of service via QUIC UDP receive function vulnerability — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-113351 | libexpat | 2.7.5-r0 | 2.10.0-r0 | expat: expat: Denial of Service via improper memory tracking in XML_ParserReset — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-115506 | libexpat | 2.7.5-r0 | 2.10.0-r0 | expat: expat: Denial of Service via delayed entity amplification detection — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-117610 | libexpat | 2.7.5-r0 | 2.10.0-r0 | expat: expat: Denial of Service via NULL pointer dereference in external entity parsing — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-118370 | libexpat | 2.7.5-r0 | 2.10.0-r0 | expat: expat: Denial of Service via integer overflow during XML attribute parsing — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-45186 | libexpat | 2.7.5-r0 | 2.8.1-r0 | libexpat: denial of service via crafted XML input — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-66046 | libexpat | 2.7.5-r0 | 2.8.4-r0 | expat: Expat: Denial of Service via quadratic complexity in attribute processing — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-76641 | libexpat | 2.7.5-r0 | 2.8.4-r0 | expat: Expat: Denial of Service via XML external entity parsing — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-76956 | libexpat | 2.7.5-r0 | 2.8.4-r0 | libexpat: libexpat: Denial of Service via hash flooding attack with crafted XML — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-76957 | libexpat | 2.7.5-r0 | 2.8.4-r0 | libexpat: libexpat: Memory corruption vulnerability allows arbitrary code execution or denial of service — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-77214 | libexpat | 2.7.5-r0 | 2.9.0-r0 | expat: expat: Information disclosure via heap buffer over-read in XML_ParseBuffer — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-93990 | libexpat | 2.7.5-r0 | 2.8.5-r0 | expat: Expat: XML Injection via Malformed UTF-16 Input — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-53587 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | libgit2: libgit2: Denial of Service due to heap out-of-bounds read from malicious Git server — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-5917 | libgit2 | 1.9.2-r0 | 1.9.7-r0 | libgit2: libgit2: Arbitrary code execution via shell command injection in SSH backend — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-55199 | libssh2 | 1.11.1-r1 | 1.11.1-r3 | libssh2: libssh2: Denial of Service via crafted SSH_MSG_EXT_INFO message — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-55200 | libssh2 | 1.11.1-r1 | 1.11.1-r3 | libssh2: libssh2 - Out-of-Bounds Write via Unchecked packet_length in transport.c — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-58050 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | libssh2: libssh2: Heap buffer overflow via integer overflow in publickey attribute allocation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-7598 | libssh2 | 1.11.1-r1 | 1.11.1-r2 | libssh2: integer overflow via large username or password arguments — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-14456 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-45447 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-97031 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-39828 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Unauthorized command execution via discarded SSH permissions — usr/sbin/webhook-go |
| HIGH | CVE-2026-39829 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted public key with excessive parameters — usr/sbin/webhook-go |
| HIGH | CVE-2026-39830 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via resource leak from unsolicited SSH responses — usr/sbin/webhook-go |
| HIGH | CVE-2026-39831 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Security key bypass due to missing user presence check — usr/sbin/webhook-go |
| HIGH | CVE-2026-39832 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh/agent: golang.org/x/crypto/ssh/agent: Security bypass due to improper handling of key restrictions — usr/sbin/webhook-go |
| HIGH | CVE-2026-39835 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh: golang: golang.org/x/crypto/ssh: Denial of Service via crafted SSH certificate — usr/sbin/webhook-go |
| HIGH | CVE-2026-42508 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh/knownhosts: golang: golang.org/x/crypto/ssh/knownhosts: Revocation bypass via unchecked SignatureKey — usr/sbin/webhook-go |
| HIGH | CVE-2026-46595 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Authorization bypass due to skipped source-address validation — usr/sbin/webhook-go |
| HIGH | CVE-2026-46597 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted AES-GCM packet decoder inputs — usr/sbin/webhook-go |
| HIGH | CVE-2026-56854 | golang.org/x/crypto | v0.48.0 | 0.55.0 | golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Authentication bypass due to unenforced source-address restrictions — usr/sbin/webhook-go |
| HIGH | CVE-2026-25681 | golang.org/x/net | v0.51.0 | 0.55.0 | golang.org/x/net/html: golang.org/x/net/html: Arbitrary code execution via Cross-Site Scripting — usr/sbin/webhook-go |
| HIGH | CVE-2026-27136 | golang.org/x/net | v0.51.0 | 0.55.0 | golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via HTML parsing bypass — usr/sbin/webhook-go |
| HIGH | CVE-2026-33814 | golang.org/x/net | v0.51.0 | 0.53.0 | net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame — usr/sbin/webhook-go |
| HIGH | CVE-2026-39821 | golang.org/x/net | v0.51.0 | 0.55.0 | golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing — usr/sbin/webhook-go |
| HIGH | CVE-2026-46600 | golang.org/x/net | v0.51.0 | 0.56.0 | golang.org/x/net/dns/dnsmessage: golang.org/x/net/dns/dnsmessage: Denial of Service via invalid DNS record parsing — usr/sbin/webhook-go |
| HIGH | CVE-2026-78661 | golang.org/x/net | v0.51.0 | 0.62.0 | golang.org/x/net/html: golang.org/x/net/html: Denial of Service via crafted HTML input — usr/sbin/webhook-go |
| HIGH | CVE-2026-78669 | golang.org/x/net | v0.51.0 | 0.60.0 | net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames — usr/sbin/webhook-go |
| HIGH | CVE-2026-56851 | golang.org/x/text | v0.34.0 | 0.41.0 | golang.org/x/text: golang.org/x/text: Denial of Service via out-of-bounds slice error in Nickname profile — usr/sbin/webhook-go |
| HIGH | CVE-2026-56852 | golang.org/x/text | v0.34.0 | 0.39.0 | golang.org/x/text: golang.org/x/text: Denial of Service via invalid UTF-8 input — usr/sbin/webhook-go |
| HIGH | CVE-2026-111943 | stdlib | v1.27.0 | 1.26.10, 1.27.3 | crypto/x509: golang: crypto/x509: Man-in-the-middle attacks via untrusted intermediate certificates — usr/sbin/webhook-go |
| HIGH | CVE-2026-78667 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | net/http: golang: golang: Denial of Service via crafted HTTP Range headers — usr/sbin/webhook-go |
| HIGH | CVE-2026-78669 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames — usr/sbin/webhook-go |
| HIGH | CVE-2026-97031 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references — usr/sbin/webhook-go |
| HIGH | CVE-2026-80212 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | resolv: resolv gem: Denial of Service via uncontrolled memory growth from crafted DNS responses — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | zlib: zlib: Heap buffer overflow in gz_vacate() allows arbitrary code execution — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-54904 | concurrent-ruby | 1.3.6 | >= 1.3.7 | concurrent-ruby: rubygem-concurrent-ruby: concurrent-ruby: Denial of Service due to infinite loop in AtomicReference#update — Ruby |
| HIGH | CVE-2026-54297 | faraday | 2.14.2 | ~> 1.10.6, >= 2.14.3 | faraday: Faraday: Denial of Service via crafted nested query strings — Ruby |
| HIGH | CVE-2026-45363 | jwt | 2.10.2 | ~> 2.10.3, >= 3.2.0 | ruby-jwt: ruby-jwt: Authentication bypass due to empty key in HMAC verification — Ruby |
| HIGH | CVE-2026-111943 | stdlib | v1.26.2 | 1.26.10, 1.27.3 | crypto/x509: golang: crypto/x509: Man-in-the-middle attacks via untrusted intermediate certificates — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-27145 | stdlib | v1.26.2 | 1.25.11, 1.26.4 | crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-33811 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-33814 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-33818 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-39820 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net/mail: golang: Go net/mail: Denial of Service via crafted email inputs — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-39821 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-39822 | stdlib | v1.26.2 | 1.25.12, 1.26.5, 1.27.0-rc.2 | golang: Go os.Root: Symlink following vulnerability allows directory traversal — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-39836 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net: golang: Go net package: Denial of Service via NUL byte in Dial and LookupPort on Windows — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-42499 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net/mail: golang: net/mail: Denial of Service via pathological email address parsing — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-42504 | stdlib | v1.26.2 | 1.25.11, 1.26.4 | mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-46600 | stdlib | v1.26.2 | 1.26.6, 1.27.0-rc.3 | golang.org/x/net/dns/dnsmessage: golang.org/x/net/dns/dnsmessage: Denial of Service via invalid DNS record parsing — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-56853 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | net/http: golang: Go net/http: Unencrypted HTTP/2 connections vulnerable to Denial of Service — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-56858 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | html/template: golang: Go html/template: Cross-Site Scripting via pathological input — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-56859 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | encoding/xml: golang: Go: Denial of Service via XML decoding recursion depth issue — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-56860 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | net/url: golang: golang net/url: Denial of Service from quadratic complexity in path resolution — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-56862 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | crypto/tls: golang: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-78667 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang: golang: Denial of Service via crafted HTTP Range headers — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-78669 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-14456 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-45447 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-105437 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-111760 | git | 2.52.0-r0 | 2.52.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-114466 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-32316 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: jq: Denial of Service or potential arbitrary code execution due to integer overflow and heap-based buffer overflow — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-40164 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: jq: Denial of Service via crafted JSON object causing hash collisions — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-5773 | curl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Wrong file transfer due to incorrect SMB connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-12064 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: SSH host verification bypass when using schemeless URLs with SFTP/SCP — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-11586 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Denial of Service via WebSocket PING flood — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-11352 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: curl/libcurl: Remote denial of service via QUIC UDP receive function vulnerability — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-33630 | c-ares | 1.34.6-r0 | 1.34.8-r0 | c-ares: c-ares: Use-after-free / double-free in query-completion handling — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-9547 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Man-in-the-middle attack via SSH host key bypass — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-92392 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: HTTP/2 upload Use-After-Free — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8927 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: Information disclosure due to uncleared proxy authentication state — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8925 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Double-free vulnerability in SASL authentication — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8458 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Unauthorized connection reuse due to a logical error — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-8286 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Insecure connection establishment due to TLS configuration mismatch — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-111760 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-105437 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-6276 | curl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Information disclosure due to cookie leak when reusing connections with custom Host headers — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| HIGH | CVE-2026-114466 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-58051 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | libssh2: libssh2: Denial of service or information disclosure via malformed SSH publickey response — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2025-15661 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | libssh2: libssh2: Information disclosure and denial of service via crafted SFTP response — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-47770 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: jq: Denial of Service via deeply nested array comparison — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-66032 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | libssh2: libssh2: Arbitrary code execution via double-free in SFTP session — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-66033 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | libssh2: libssh2: Denial of Service via integer underflow in AES-GCM cipher negotiation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-66034 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | libssh2: libssh2: Information disclosure and potential arbitrary code execution via heap out-of-bounds read — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-66035 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | libssh2: libssh2: Arbitrary code execution via heap buffer overflow during SSH negotiation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-18798 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: QUIC server may trigger double free when processing INITIAL packet — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-34182 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-34183 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56132 | libexpat | 2.7.5-r0 | 2.8.2-r0 | expat: libexpat: Arbitrary Code Execution via Heap-based Buffer Overflow — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56403 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Arbitrary code execution due to integer overflow in storeAtts — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56404 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Arbitrary Code Execution via integer overflow in addBinding — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56405 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Information disclosure and arbitrary code execution via integer overflow — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56406 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Arbitrary code execution via integer overflow in XML_ParseBuffer — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56407 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Arbitrary code execution due to integer overflow — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56408 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Information disclosure and arbitrary code execution via integer overflow — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56409 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Integer overflow in xmlwf may lead to information disclosure or arbitrary code execution — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56410 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Integer overflow in xmlwf can lead to information disclosure and arbitrary code execution. — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56411 | libexpat | 2.7.5-r0 | 2.8.2-r0 | expat: libexpat: Integer Overflow Vulnerability Leading to Information Disclosure or Code Execution — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56412 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Use-after-free vulnerability due to improper handling of XML CDATA sections — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-7168 | curl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Information disclosure via incorrect Proxy-Authorization header reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-53583 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | libgit2: libgit2: Network attacker can intercept HTTPS connections via inverted IP SubjectAltName comparison — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-53585 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | libgit2: libgit2: Denial of Service via Unbounded Memory Allocation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-53586 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | libgit2: libgit2: Information disclosure via HTTP redirect allows credential leakage — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-82208 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Improper certificate validation when using wolfSSL CA cache — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114467 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-113408 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114467 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-113408 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-39825 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net/http/httputil: golang: net/http/httputil: ReverseProxy forwards hidden query parameters, potentially bypassing security controls — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-39823 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | html/template: golang: Go html/template: Cross-Site Scripting via improper URL escaping in meta tag content — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-8924 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Cookie injection via malicious HTTP server using super cookies — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-89156 | pcre2 | 10.47-r0 | 10.48-r0 | PCRE2: PCRE2: Out-of-bounds read via invalid UTF data during JIT fallback — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-89158 | pcre2 | 10.47-r0 | 10.48-r0 | PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-89160 | pcre2 | 10.47-r0 | 10.48-r0 | pcre2: PCRE2: Denial of Service via out-of-bounds read during invalid UTF matching — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8926 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure via incorrect .netrc password lookup — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8932 | curl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Security feature bypass due to improper mTLS connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9079 | curl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure due to failure to clear proxy authentication credentials — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9080 | curl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Use-after-free via curl_easy_pause() in CURLMOPT_SOCKETFUNCTION callback — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-92388 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: FTP wildcard write callback mixup — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9545 | curl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure via cached SSL session and early data — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-80213 | ruby | 3.4.9-r0 | 3.4.12-r0 | resolv: Resolv gem: DNS allowlist and egress bypass, and cache poisoning via crafted hostnames — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9546 | curl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure due to persistent Referer header — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-80213 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | resolv: Resolv gem: DNS allowlist and egress bypass, and cache poisoning via crafted hostnames — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | Improper Restriction of Operations within the Bounds of a Memory Buffe ... — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-54905 | concurrent-ruby | 1.3.6 | >= 1.3.7 | concurrent-ruby: Concurrent-ruby: Incorrect write lock granting leading to broken mutual exclusion — Ruby |
| MEDIUM | GHSA-r6vf-943r-2wvw | minitar | 1.1.0 | ~> 1.1.1, >= 1.2.0 | minitar path traversal vulnerability on Windows with a maliciously crafted tarball — Ruby |
| MEDIUM | CVE-2026-42764 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: NULL pointer dereference in QUIC server initial packet handling — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-45445 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: AES-OCB IV Ignored on EVP_Cipher() Path — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-63072 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: heap buffer overflow in CMS key unwrapping — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-63076 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: invalid pointer dereference in CMP server via crafted protectionAlg — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | GHSA-gxhx-2686-5h9g | github.com/slack-go/slack | v0.18.0 | 0.23.1 | slack-go `SecretsVerifier` accepts empty signing secret without precondition — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-40898 | github.com/quic-go/quic-go | v0.59.0 | 0.59.1 | github.com/quic-go/quic-go: quic-go: Denial of Service via excessive memory allocation in HTTP/3 trailers — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-97054 | stdlib | v1.26.2 | 1.26.11, 1.27.4 | net/http: golang: net/http: Denial of Service via race condition when handling oversized HTTP/1 requests — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-97032 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: net/http: Denial of Service via concurrent HPACK encoder modification — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-97030 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | html/template: golang: html/template: Cross-site scripting via improper escaping of yield keyword — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-94448 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | html/template: golang: golang: cross-site scripting via consecutive expressions in JavaScript template literals — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-94440 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/textproto: mime/multipart: golang: golang: Denial of Service via memory limit bypass in multipart form parsing — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-94439 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang: net/http: HTTP request smuggling via improper handling of HTTP/1 CONNECT responses — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-78663 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: golang: flow control limit bypass via double refund in HTTP/2 server — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-78660 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang: golang.org/x/net/http2: net/http: HTTP response smuggling via malformed HTTP/2 framing headers — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-78659 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang.org/x/net/http2: golang: net/http: Denial of Service via HTTP/2 trailer header memory exhaustion — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-56866 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang: golang: Cross-user response poisoning via desynchronized HTTP CONNECT connections — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-42507 | stdlib | v1.26.2 | 1.25.11, 1.26.4 | net/textproto: golang: Golang net/textproto: Misleading error messages via input injection — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-42505 | stdlib | v1.26.2 | 1.25.12, 1.26.5, 1.27.0-rc.2 | crypto/tls: golang: Go crypto/tls: Information disclosure in Encrypted Client Hello — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-39826 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | html/template: golang: html/template: Cross-site scripting due to incorrect script tag escaping — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-114469 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-10536 | libcurl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Use-after-free vulnerability leading to Denial of Service — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-11564 | libcurl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Certificate validation bypass due to incorrect connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-11856 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure via incorrect Digest authentication header reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-19931 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via incorrect connection reuse with Negotiate authentication — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-4873 | libcurl | 8.19.0-r0 | 8.20.0-r0 | curl: curl: Information disclosure due to incorrect TLS connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-5545 | libcurl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Authentication bypass due to incorrect HTTP Negotiate connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-6253 | libcurl | 8.19.0-r0 | 8.20.0-r0 | curl: curl: Proxy credential disclosure via redirects to unauthenticated proxies — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-6429 | libcurl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Credential leak via reused proxy connection during HTTP redirects — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-7009 | libcurl | 8.19.0-r0 | 8.20.0-r0 | curl: Curl: Certificate validation bypass due to OCSP stapling flaw — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-7168 | libcurl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Information disclosure via incorrect Proxy-Authorization header reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-82208 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Improper certificate validation when using wolfSSL CA cache — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8924 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Cookie injection via malicious HTTP server using super cookies — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8926 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure via incorrect .netrc password lookup — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-8932 | libcurl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Security feature bypass due to improper mTLS connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9079 | libcurl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure due to failure to clear proxy authentication credentials — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9080 | libcurl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Use-after-free via curl_easy_pause() in CURLMOPT_SOCKETFUNCTION callback — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-92388 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: FTP wildcard write callback mixup — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9545 | libcurl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure via cached SSL session and early data — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-63076 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: invalid pointer dereference in CMP server via crafted protectionAlg — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-97054 | stdlib | v1.27.0 | 1.26.11, 1.27.4 | net/http: golang: net/http: Denial of Service via race condition when handling oversized HTTP/1 requests — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-97032 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: net/http: Denial of Service via concurrent HPACK encoder modification — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-97030 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | html/template: golang: html/template: Cross-site scripting via improper escaping of yield keyword — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-94448 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | html/template: golang: golang: cross-site scripting via consecutive expressions in JavaScript template literals — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-94440 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | net/textproto: mime/multipart: golang: golang: Denial of Service via memory limit bypass in multipart form parsing — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-94439 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | net/http: golang: net/http: HTTP request smuggling via improper handling of HTTP/1 CONNECT responses — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-78663 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: golang: flow control limit bypass via double refund in HTTP/2 server — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-78660 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | net/http: golang: golang.org/x/net/http2: net/http: HTTP response smuggling via malformed HTTP/2 framing headers — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-78659 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | net/http: golang.org/x/net/http2: golang: net/http: Denial of Service via HTTP/2 trailer header memory exhaustion — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-56866 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | net/http: golang: golang: Cross-user response poisoning via desynchronized HTTP CONNECT connections — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-63072 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: heap buffer overflow in CMS key unwrapping — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-45445 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: AES-OCB IV Ignored on EVP_Cipher() Path — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-42764 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: NULL pointer dereference in QUIC server initial packet handling — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-34183 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-34182 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-18798 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: QUIC server may trigger double free when processing INITIAL packet — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-54679 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: jq: Denial of Service via integer overflow and buffer overrun on 32-bit systems — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-49839 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: jq: Heap out-of-bounds write via oversized raw file processing — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-9546 | libcurl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Information disclosure due to persistent Referer header — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-4873 | curl | 8.19.0-r0 | 8.20.0-r0 | curl: curl: Information disclosure due to incorrect TLS connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-5545 | curl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Authentication bypass due to incorrect HTTP Negotiate connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-6253 | curl | 8.19.0-r0 | 8.20.0-r0 | curl: curl: Proxy credential disclosure via redirects to unauthenticated proxies — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-6429 | curl | 8.19.0-r0 | 8.20.0-r0 | curl: libcurl: Credential leak via reused proxy connection during HTTP redirects — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-7009 | curl | 8.19.0-r0 | 8.20.0-r0 | curl: Curl: Certificate validation bypass due to OCSP stapling flaw — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-44777 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: stack overflow in module loading on mutual include — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-43896 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: stack overflow in recursive object merge — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-43895 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: embedded NUL in jq import paths causes local redaction-policy bypass and preserves sensitive fields in published artifacts — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-43894 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: jq: Arbitrary Code Execution or Denial of Service via Signed Integer Overflow — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-41257 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: signed-int overflow in stack_reallocate — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-41256 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: embedded NUL truncates top-level jq programs loaded with -f — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-40612 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: stack overflow via unbounded recursion in jv_contains — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-39979 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: out-of-bounds read in jv_parse_sized() on error formatting for non-NUL-terminated buffers — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-39956 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: missing runtime type checks for _strindices lead to crash and limited memory disclosure — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-33948 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: jq: Input validation bypass via embedded NUL bytes allows parser differential attacks — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-33947 | jq | 1.8.1-r0 | 1.8.2-r0 | jq: unbounded Recursion in jv_setpath() / jv_getpath() / delpaths_sorted() — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-102633 | libexpat | 2.7.5-r0 | 2.9.0-r0 | expat: expat: Denial of Service via integer overflow in expat_realloc — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-50219 | libexpat | 2.7.5-r0 | 2.8.2-r0 | expat: libexpat: Use-after-free vulnerability due to improper handler call depth tracking — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-56131 | libexpat | 2.7.5-r0 | 2.8.2-r0 | libexpat: libexpat: Use-after-free vulnerability due to insufficient handler call depth tracking — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-97045 | golang.org/x/net | v0.51.0 | 0.62.0 | golang.org/x/net/html: golang.org/x/net/html: Cross-Site Scripting via improper namespace handling during HTML rendering — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-97032 | golang.org/x/net | v0.51.0 | 0.60.0 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: net/http: Denial of Service via concurrent HPACK encoder modification — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-78663 | golang.org/x/net | v0.51.0 | 0.60.0 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: golang: flow control limit bypass via double refund in HTTP/2 server — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-78660 | golang.org/x/net | v0.51.0 | 0.60.0 | net/http: golang: golang.org/x/net/http2: net/http: HTTP response smuggling via malformed HTTP/2 framing headers — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-78659 | golang.org/x/net | v0.51.0 | 0.60.0 | net/http: golang.org/x/net/http2: golang: net/http: Denial of Service via HTTP/2 trailer header memory exhaustion — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-42506 | golang.org/x/net | v0.51.0 | 0.55.0 | golang.org/x/net/html: golang.org/x/net/html: Cross-Site Scripting (XSS) via arbitrary HTML parsing — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-42502 | golang.org/x/net | v0.51.0 | 0.55.0 | golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via unexpected HTML tree rendering — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-25680 | golang.org/x/net | v0.51.0 | 0.55.0 | golang.org/x/net/html: golang.org/x/net/html: Denial of Service due to excessive HTML parsing — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-10536 | curl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Use-after-free vulnerability leading to Denial of Service — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-78662 | golang.org/x/crypto | v0.48.0 | 0.56.0 | golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via channel request flooding — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-56855 | golang.org/x/crypto | v0.48.0 | 0.56.0 | golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted messages — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-46598 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh/agent: golang: golang.org/x/crypto/ssh/agent: Denial of Service via malformed input — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-39834 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh: golang: golang.org/x/crypto/ssh: Denial of Service due to integer overflow in SSH channel write — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-39833 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh/agent: golang.org/x/crypto/ssh/agent: Security bypass due to unenforced key confirmation — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-39827 | golang.org/x/crypto | v0.48.0 | 0.52.0 | golang.org/x/crypto/ssh: golang: golang.org/x/crypto/ssh: Denial of Service via repeated rejected channel openings — usr/sbin/webhook-go |
| MEDIUM | CVE-2026-11564 | curl | 8.19.0-r0 | 8.22.0-r0 | libcurl: libcurl: Certificate validation bypass due to incorrect connection reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-19931 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via incorrect connection reuse with Negotiate authentication — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-11856 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure via incorrect Digest authentication header reuse — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86410 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: redirect to SFTP or SCP bypasses host verification — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86409 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: stale SigV4 headers sent unintended — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-82209 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via improper Public Suffix List boundary check — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-80255 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure due to secure cookie attribute bypass — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-56857 | stdlib | v1.27.0 | 1.26.9, 1.27.2 | os: golang: golang: Directory traversal via Windows junction handling — usr/sbin/webhook-go |
| LOW | CVE-2026-80231 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Incorrect HTTPS connection reuse with Native CA Store — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-80230 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Public key pinning bypass allows unauthenticated connections — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-80229 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Memory corruption vulnerability via OpenSSL 3 provider use-after-free — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-56857 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | os: golang: golang: Directory traversal via Windows junction handling — usr/local/bin/supercronic-linux-amd64 |
| LOW | CVE-2026-18924 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Use-after-free in HTTP/2 Server Push with shared connections — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-13608 | curl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Authentication bypass in OpenLDAP SASL negotiation via Man-in-the-Middle (MITM) attack — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-107929 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: local interface connection reuse mixup — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-107928 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: info leak uploading over WebSockets with GnuTLS — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-14457 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: RPK server signature algorithm selection can dereference a missing certificate — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-80231 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Incorrect HTTPS connection reuse with Native CA Store — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-80255 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure due to secure cookie attribute bypass — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-82209 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via improper Public Suffix List boundary check — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86409 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: stale SigV4 headers sent unintended — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86410 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: redirect to SFTP or SCP bypasses host verification — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86411 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: FTP connection reuse inherits client-certificate — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86412 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie erases cookie jar — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86413 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: Negotiate credentials sent to redirected origin — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86414 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: leaking host credentials to HTTP proxy — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86415 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: auto client cert connection reuse mixup — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87861 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: cross-origin reuse of a Negotiate connection — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87862 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: HSTS cache import drops longer-lived child — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87863 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: Hsts Response Erases Persisted Entries — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87864 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: IMAP APPEND plus CRLF conversion command injection — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87865 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: knownhost callback mismatches key as missing — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87866 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: wolfSSL public-key pinning bypass — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92386 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie aborts cookie jar load — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92387 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: never-ending loop via server response omission — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92389 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: TFTP direction confusion — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92390 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: -J no-clobber guarantee bypassed with 103 early hints — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-75803 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: openssl: AEAD forgeries possible with empty ciphertext in EVP_Cipher() — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-34180 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information disclosure. — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-34181 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42766 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Possible NULL Dereference in Password-Based CMS Decryption — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42767 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42768 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42769 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42770 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: FFC-DH Peer Validation Uses Attacker-Supplied q — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-45446 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-54874 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: excessive memory use buffering DTLS records for a future epoch — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-63073 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: untrusted sender DN used as format string in CMP response validation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-63074 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: CMP indefinite cache growth of ExtraCerts — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-63075 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: QUIC ACK-only packet retention can cause memory exhaustion — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-7383 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-75803 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | openssl: openssl: AEAD forgeries possible with empty ciphertext in EVP_Cipher() — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-9076 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-107928 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: info leak uploading over WebSockets with GnuTLS — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-107929 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: local interface connection reuse mixup — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-13608 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Authentication bypass in OpenLDAP SASL negotiation via Man-in-the-Middle (MITM) attack — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-18924 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Use-after-free in HTTP/2 Server Push with shared connections — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-80229 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: libcurl: Memory corruption vulnerability via OpenSSL 3 provider use-after-free — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-80230 | libcurl | 8.19.0-r0 | 8.22.0-r0 | curl: curl: Public key pinning bypass allows unauthenticated connections — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-9076 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-94266 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: password leak in CURLINFO_EFFECTIVE_URL — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-94265 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: Authorization: Negotiate sent to foreign origin — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-89162 | pcre2 | 10.47-r0 | 10.48-r0 | pcre2: PCRE2: Information disclosure via pcre2_serialize_encode — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92391 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: curl_mime_free stack overflow by recursion — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92390 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: -J no-clobber guarantee bypassed with 103 early hints — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92389 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: TFTP direction confusion — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92387 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: never-ending loop via server response omission — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92386 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie aborts cookie jar load — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87866 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: wolfSSL public-key pinning bypass — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87865 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: knownhost callback mismatches key as missing — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87864 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: IMAP APPEND plus CRLF conversion command injection — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87863 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: Hsts Response Erases Persisted Entries — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87862 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: HSTS cache import drops longer-lived child — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-87861 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: cross-origin reuse of a Negotiate connection — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86415 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: auto client cert connection reuse mixup — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86414 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: leaking host credentials to HTTP proxy — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86413 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: Negotiate credentials sent to redirected origin — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86412 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie erases cookie jar — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-86411 | curl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: FTP connection reuse inherits client-certificate — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-92391 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: curl_mime_free stack overflow by recursion — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-94265 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: Authorization: Negotiate sent to foreign origin — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-94266 | libcurl | 8.19.0-r0 | 8.23.0-r0 | curl: curl: password leak in CURLINFO_EFFECTIVE_URL — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-41080 | libexpat | 2.7.5-r0 | 2.8.1-r0 | libexpat: expat: libexpat: Denial of Service via hash flooding with crafted XML — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-53584 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | libgit2: libgit2: Submodule path traversal allows arbitrary directory creation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-14457 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: RPK server signature algorithm selection can dereference a missing certificate — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-34180 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information disclosure. — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-34181 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42766 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Possible NULL Dereference in Password-Based CMS Decryption — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42767 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42768 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42769 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-42770 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: FFC-DH Peer Validation Uses Attacker-Supplied q — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-45446 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-54874 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: excessive memory use buffering DTLS records for a future epoch — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-63073 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: untrusted sender DN used as format string in CMP response validation — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-63074 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: CMP indefinite cache growth of ExtraCerts — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-63075 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | openssl: QUIC ACK-only packet retention can cause memory exhaustion — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| LOW | CVE-2026-7383 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| UNKNOWN | GO-2026-5932 | golang.org/x/crypto | v0.48.0 | 0.58.1-0.20261009181718-2f1f834330b2 | The golang.org/x/crypto/openpgp package is unmaintained, unsafe by design, and has known security issues — usr/sbin/webhook-go |
| UNKNOWN | CVE-2026-39824 | golang.org/x/sys | v0.41.0 | 0.44.0 | Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows — usr/sbin/webhook-go |
| UNKNOWN | CVE-2026-80256 | libcurl | 8.19.0-r0 | 8.22.0-r0 | Title Not Available — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| UNKNOWN | CVE-2026-80256 | curl | 8.19.0-r0 | 8.22.0-r0 | Title Not Available — ghcr.io/voxpupuli/r10k-webhook:latest (alpine 3.23.4) |
| UNKNOWN | CVE-2026-39824 | golang.org/x/sys | v0.43.0 | 0.44.0 | Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows — usr/local/bin/supercronic-linux-amd64 |
Grype
CRITICAL 54
HIGH 175
MEDIUM 71
LOW 12
UNKNOWN 2
NVD/CPE filtered 66
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-18924 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-18924 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | GO-2026-6612 | golang.org/x/net | v0.51.0 | 0.60.0 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. — /usr/sbin/webhook-go |
| CRITICAL | GO-2026-6612 | stdlib | go1.26.2 | 1.26.9 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. — /usr/local/bin/supercronic-linux-amd64 |
| CRITICAL | GO-2026-6612 | stdlib | go1.27.0 | 1.27.2 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. — /usr/sbin/webhook-go |
| CRITICAL | CVE-2026-94265 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-94265 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-19931 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-19931 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8926 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-11564 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-11564 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86413 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86413 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-10536 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-10536 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8926 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-11856 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-11856 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86411 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86411 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-93577 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-93577 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8924 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8924 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87861 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86414 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87861 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-92388 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-92388 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86414 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-89078 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-110264 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-110264 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-75803 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-75803 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-89078 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-63073 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-63073 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8925 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8925 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-9079 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-9079 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8927 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-8927 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-97229 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-97229 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r0 | 1.2.1-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-34182 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-34182 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87866 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-7598 | libssh2 | 1.11.1-r1 | 1.11.1-r2 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87866 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-client-common | 10.2_p1-r0 | 10.2_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-13608 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6605 | stdlib | go1.26.2 | 1.26.9, 1.27.2 | When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6613 | stdlib | go1.26.2 | 1.26.9, 1.27.2 | When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6613 | stdlib | go1.27.0 | 1.26.9, 1.27.2 | When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP. — /usr/sbin/webhook-go |
| HIGH | CVE-2026-87865 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87865 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6605 | stdlib | go1.27.0 | 1.26.9, 1.27.2 | When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning. — /usr/sbin/webhook-go |
| HIGH | CVE-2026-13608 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-115506 | libexpat | 2.7.5-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-63075 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl | 1.2.5-r23 | 1.2.5-r24 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.5-r23 | 1.2.5-r24 | /lib/apk/db/installed |
| HIGH | GO-2026-5972 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6089 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-63075 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6090 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-80229 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92390 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80229 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80231 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80231 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-94266 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-94266 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6610 | stdlib | go1.26.2 | 1.26.9 | Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-92390 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-5037 | stdlib | go1.26.2 | 1.25.11, 1.26.4 | (*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, ".") to execute repeatedly on the same input hostname. With a large DNS SAN list, verification costs scaled quadratically based on the number of SAN entries multiplied by the hostname's label count. Because x509.Verify validates hostnames before building the certificate chain, this overhead occurred even for untrusted certificates. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6610 | stdlib | go1.27.0 | 1.27.2 | Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling. — /usr/sbin/webhook-go |
| HIGH | CVE-2026-8932 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-8932 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82209 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82209 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-76641 | libexpat | 2.7.5-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-40164 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-34181 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-34181 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80230 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80230 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-c32j-vqhx-rx3x | jwt | 2.10.2 | 2.10.3 | ruby-jwt: Empty-key HMAC bypass; cross-language sibling of CVE-2026-44351 — /usr/lib/ruby/gems/3.4.0/specifications/jwt-2.10.2.gemspec |
| HIGH | CVE-2026-9547 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9547 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-77214 | libexpat | 2.7.5-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-89157 | pcre2 | 10.47-r0 | 10.48-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-8286 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-8286 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-58051 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-9545 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9545 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-6276 | curl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-6276 | libcurl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-76956 | libexpat | 2.7.5-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-103111 | pcre2 | 10.47-r0 | 10.49-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-49839 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-89161 | pcre2 | 10.47-r0 | 10.48-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-76957 | libexpat | 2.7.5-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-113351 | libexpat | 2.7.5-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9080 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9080 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-45186 | libexpat | 2.7.5-r0 | 2.8.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-66035 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-80255 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80255 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-5970 | golang.org/x/text | v0.34.0 | 0.39.0 | A norm.Iter can enter an infinite loop when handling input containing invalid UTF-8 bytes. — /usr/sbin/webhook-go |
| HIGH | CVE-2026-53587 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-93990 | libexpat | 2.7.5-r0 | 2.8.5-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86145 | pcre2 | 10.47-r0 | 10.48-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-58050 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-117610 | libexpat | 2.7.5-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-66034 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-86415 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86415 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-12064 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-12064 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-102633 | libexpat | 2.7.5-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-118370 | libexpat | 2.7.5-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82208 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82208 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-41080 | libexpat | 2.7.5-r0 | 2.8.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80212 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80212 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-105437 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-105437 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92387 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-34183 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-34183 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87862 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87862 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-34180 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-34180 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-11352 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-11352 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-66046 | libexpat | 2.7.5-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-55199 | libssh2 | 1.11.1-r1 | 1.11.1-r3 | /lib/apk/db/installed |
| HIGH | CVE-2026-63072 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-63072 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6603 | golang.org/x/net | v0.51.0 | 0.60.0 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. — /usr/sbin/webhook-go |
| HIGH | GO-2026-6603 | stdlib | go1.26.2 | 1.26.9 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6603 | stdlib | go1.27.0 | 1.27.2 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. — /usr/sbin/webhook-go |
| HIGH | CVE-2026-87864 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87864 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86412 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87863 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92386 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86412 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87863 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92386 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-client-default | 10.2_p1-r0 | 10.2_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-keygen | 10.2_p1-r0 | 10.2_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-45447 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-45447 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-55200 | libssh2 | 1.11.1-r1 | 1.11.1-r3 | /lib/apk/db/installed |
| HIGH | GO-2026-5026 | golang.org/x/net | v0.51.0 | 0.55.0 | 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". — /usr/sbin/webhook-go |
| HIGH | GO-2026-5026 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | 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". — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-18798 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-18798 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-63076 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-63076 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-5917 | libgit2 | 1.9.2-r0 | 1.9.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92392 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92392 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-14457 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-14457 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | GHSA-q339-8rmv-2mhv | erb | 4.0.4 | 4.0.4.1 | ERB has an @_init deserialization guard bypass via def_module / def_method / def_class — /usr/lib/ruby/gems/3.4.0/specifications/default/erb-4.0.4.gemspec |
| HIGH | CVE-2026-92391 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92391 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-42764 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-42764 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86409 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86409 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92387 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6611 | stdlib | go1.26.2 | 1.26.9 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-107928 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107928 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9076 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9076 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6607 | stdlib | go1.26.2 | 1.26.9, 1.27.2 | Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6607 | stdlib | go1.27.0 | 1.26.9, 1.27.2 | Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result. — /usr/sbin/webhook-go |
| HIGH | GO-2026-6608 | stdlib | go1.26.2 | 1.26.9, 1.27.2 | Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6608 | stdlib | go1.27.0 | 1.26.9, 1.27.2 | Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes. — /usr/sbin/webhook-go |
| HIGH | CVE-2026-45445 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-45445 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-14456 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-5773 | libcurl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-14456 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107929 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-5773 | curl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107929 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-h8w8-99g7-qmvj | concurrent-ruby | 1.3.6 | 1.3.7 | Concurrent Ruby : `AtomicReference#update` livelocks when the stored value is `Float::NAN` — /usr/lib/ruby/gems/3.4.0/specifications/concurrent-ruby-1.3.6.gemspec |
| HIGH | GO-2026-6617 | golang.org/x/net | v0.51.0 | 0.60.0 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. — /usr/sbin/webhook-go |
| HIGH | GO-2026-6617 | stdlib | go1.26.2 | 1.26.9 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6617 | stdlib | go1.27.0 | 1.27.2 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. — /usr/sbin/webhook-go |
| HIGH | CVE-2026-9546 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-9546 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-4971 | stdlib | go1.26.2 | 1.25.10, 1.26.3 | The Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0). — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-66033 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-66032 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-54874 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-54874 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6611 | golang.org/x/net | v0.51.0 | 0.60.0 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. — /usr/sbin/webhook-go |
| HIGH | GO-2026-6611 | stdlib | go1.27.0 | 1.27.2 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. — /usr/sbin/webhook-go |
| HIGH | CVE-2026-33630 | c-ares | 1.34.6-r0 | 1.34.8-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-4918 | stdlib | go1.26.2 | 1.25.10, 1.26.3 | 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. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-11586 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-7383 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-7383 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-32316 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86410 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86410 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-11586 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92389 | libcurl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92389 | curl | 8.19.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-98m9-hrrm-r99r | faraday | 2.14.2 | 2.14.3 | Faraday: Uncontrolled recursion in NestedParamsEncoder allows stack exhaustion DoS via deeply nested query parameters — /usr/lib/ruby/gems/3.4.0/specifications/faraday-2.14.2.gemspec |
| MEDIUM | CVE-2026-53584 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-89158 | pcre2 | 10.47-r0 | 10.48-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56407 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-7009 | curl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-7009 | libcurl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56406 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-33948 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-53583 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114469 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-43895 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-33947 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-80213 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-80213 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-40612 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56411 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-44777 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56405 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56408 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-43894 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-41256 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-43896 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56409 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56410 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56404 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56131 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-47770 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56132 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-39956 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-50219 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56412 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-56403 | libexpat | 2.7.5-r0 | 2.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-54679 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-41257 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-5545 | libcurl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-5545 | curl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-7168 | libcurl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-7168 | curl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-6429 | libcurl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-6429 | curl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-42769 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-42769 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| MEDIUM | GO-2026-6218 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte buffer using index-based backtracking for '..' segments, eliminating the quadratic time complexity and significantly reducing memory allocations. — /usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-42766 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-42766 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-42767 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-42767 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-6253 | curl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-6253 | libcurl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2025-15661 | libssh2 | 1.11.1-r1 | 1.11.1-r4 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-63074 | libssl3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-63074 | libcrypto3 | 3.5.6-r0 | 3.5.8-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-39979 | jq | 1.8.1-r0 | 1.8.2-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-89156 | pcre2 | 10.47-r0 | 10.48-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-53586 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-89160 | pcre2 | 10.47-r0 | 10.48-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-4873 | libcurl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-4873 | curl | 8.19.0-r0 | 8.20.0-r0 | /lib/apk/db/installed |
| MEDIUM | GO-2026-5039 | stdlib | go1.26.2 | 1.25.11, 1.26.4 | When returning errors, functions in the net/textproto package would include its input as part of the error. This might allow an attacker to inject misleading content to errors that are printed or logged. — /usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | GO-2026-5856 | stdlib | go1.26.2 | 1.25.12, 1.26.5, 1.27.0-rc.2 | Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of pre-shared key identities in the unencrypted client hello. — /usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-53585 | libgit2 | 1.9.2-r0 | 1.9.6-r0 | /lib/apk/db/installed |
| MEDIUM | GO-2026-6859 | stdlib | go1.27.0 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/sbin/webhook-go |
| MEDIUM | GO-2026-6859 | stdlib | go1.26.2 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-8458 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-8458 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-45446 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-45446 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| MEDIUM | GO-2026-6809 | stdlib | go1.27.0 | 1.26.10, 1.27.3 | On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy. — /usr/sbin/webhook-go |
| MEDIUM | GO-2026-6809 | stdlib | go1.26.2 | 1.26.10, 1.27.3 | On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy. — /usr/local/bin/supercronic-linux-amd64 |
| LOW | CVE-2026-89162 | pcre2 | 10.47-r0 | 10.48-r0 | /lib/apk/db/installed |
| LOW | GHSA-6wx8-w4f5-wwcr | concurrent-ruby | 1.3.6 | 1.3.7 | Concurrent Ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption — /usr/lib/ruby/gems/3.4.0/specifications/concurrent-ruby-1.3.6.gemspec |
| LOW | GHSA-wv3x-4vxv-whpp | concurrent-ruby | 1.3.6 | 1.3.7 | Concurrent Ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity — /usr/lib/ruby/gems/3.4.0/specifications/concurrent-ruby-1.3.6.gemspec |
| LOW | CVE-2026-114467 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-42770 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| LOW | GHSA-x2f5-4prf-w687 | json | 2.9.1 | 2.19.9 | Ruby json: JSON generator heap buffer overflow when streaming to an IO — /usr/lib/ruby/gems/3.4.0/specifications/default/json-2.9.1.gemspec |
| LOW | CVE-2026-113408 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-113408 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-42770 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-42768 | libcrypto3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-42768 | libssl3 | 3.5.6-r0 | 3.5.7-r0 | /lib/apk/db/installed |
| UNKNOWN | CVE-2026-80256 | curl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| UNKNOWN | CVE-2026-80256 | libcurl | 8.19.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
Filtered NVD/CPE matches (66)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-107496 | libcrypto3 | 3.5.6-r0 | Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely. Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service. CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns. The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option. The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected. The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely. FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107496 | libssl3 | 3.5.6-r0 | Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely. Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service. CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns. The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option. The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected. The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely. FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached. — /lib/apk/db/installed | |
| HIGH | CVE-2026-59850 | libssh2 | 1.11.1-r1 | A flaw was found in libssh. If data packets are processed after a channel is closed, channel data callbacks can be invoked after the associated data has already been freed, leading to crashes or possible use-after-free conditions. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95691 | libcrypto3 | 3.5.6-r0 | Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95691 | libssl3 | 3.5.6-r0 | Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.6-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.6-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-88823 | libcrypto3 | 3.5.6-r0 | Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-88823 | libssl3 | 3.5.6-r0 | Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.6-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.6-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-132825 | ruby | 3.4.9-r0 | Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. — /lib/apk/db/installed | |
| HIGH | CVE-2026-132825 | ruby-libs | 3.4.9-r0 | Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.6-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.6-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.6-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libssl3 | 3.5.6-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libcrypto3 | 3.5.6-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libssl3 | 3.5.6-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-54873 | libcrypto3 | 3.5.6-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libssl3 | 3.5.6-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libcrypto3 | 3.5.6-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.6-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libcrypto3 | 3.5.6-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libssl3 | 3.5.6-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-54873 | libssl3 | 3.5.6-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95692 | libssl3 | 3.5.6-r0 | Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected. Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV. CWE: CWE-125: Out-of-bounds Read Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length. The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery. Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application. FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95692 | libcrypto3 | 3.5.6-r0 | Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected. Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV. CWE: CWE-125: Out-of-bounds Read Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length. The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery. Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application. FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm. — /lib/apk/db/installed | |
| HIGH | CVE-2026-69184 | c-ares | 1.34.6-r0 | c-ares is an asynchronous resolver library. Prior to 1.34.7, ares_dns_name_parse() enforces backward DNS compression pointers but does not bound the total pointer hops or assembled name length. A malicious DNS server can send a response containing a long descending pointer chain and many resource records whose NAME or RDATA fields refer to the chain, causing repeated decompression work that grows quadratically with message size. A single crafted response can stall the single-threaded c-ares event loop and deny DNS resolution, without causing memory corruption or information disclosure. This issue is fixed in version 1.34.7. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.6-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-58055 | nghttp2-libs | 1.69.0-r0 | nghttp2's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also carries a Content-Length header and body onto reusable keep-alive backend connections, re-adding the Upgrade and Connection headers while passing Content-Length verbatim. A backend that resolves the resulting ambiguous message in the attacker's favor enables HTTP request/response smuggling and cross-client response-queue poisoning. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-88822 | libssl3 | 3.5.6-r0 | Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-88822 | libcrypto3 | 3.5.6-r0 | Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59848 | libssh2 | 1.11.1-r1 | A flaw was found in libssh. A malicious SFTP server can send responses for unknown request IDs that libssh clients keep queued indefinitely, causing unbounded memory growth and client-side denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libcrypto3 | 3.5.6-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75806 | libssl3 | 3.5.6-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75806 | libcrypto3 | 3.5.6-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.6-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.6-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59845 | libssh2 | 1.11.1-r1 | A flaw was found in libssh. When ProxyCommand is used, an unchecked fork() failure can be stored as process ID -1; during cleanup, signals may then be sent across the caller's accessible process tree, leading to local denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100407 | git | 2.52.0-r0 | Git for Windows is the Windows port of Git. From 2.44.0.windows.1 until 2.55.0.windows.3, the git-credential-wincred store operation in contrib/credential/wincred/git-credential-wincred.c uses _scwprintf() to size a formatted wide-character credential buffer without space for the terminating NUL when both password and oauth_refresh_token are present. The operation also passes a byte count to _snwprintf_s() where a wide-character count is required, allowing the terminator to be written one WCHAR past the heap allocation before CredWriteW() persists the credential. The resulting fixed two-byte NUL overwrite can terminate the helper with Windows heap-corruption status and can cause git credential approve to report success even though the OAuth credential was not stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100408 | git | 2.52.0-r0 | Git for Windows is the Windows port of Git. From 2.43.0.windows.1 until 2.55.0.windows.3, when a matching git:* credential exists in Windows Credential Manager and a git-credential-wincred erase input includes a password field, the operation in contrib/credential/wincred/git-credential-wincred.c allocates a buffer of exactly CredentialBlobSize bytes in match_cred_password() and then uses wcsncpy_s() to copy the corresponding number of wide characters plus a terminating NUL. The destination capacity is also supplied in bytes instead of WCHAR elements, allowing a fixed two-byte NUL write past the allocation before the password comparison determines whether CredDeleteW() should remove the credential; erase without a password field does not enter this comparison path. The helper can terminate with Windows heap-corruption status, and git credential reject can appear successful while the rejected credential remains stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libssl3 | 3.5.6-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libcrypto3 | 3.5.6-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libssl3 | 3.5.6-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59844 | libssh2 | 1.11.1-r1 | A flaw was found in libssh. A remote authenticated client can issue SSH_FXP_READ requests with an arbitrarily large length, causing a libssh SFTP server to allocate excessive memory and potentially exhaust it through repeated requests. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59843 | libssh2 | 1.11.1-r1 | A flaw was found in libssh. A remote authenticated peer can advertise a zero maximum packet size in SSH_MSG_CHANNEL_OPEN, causing later channel writes to loop indefinitely and consume CPU, leading to denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-69186 | c-ares | 1.34.6-r0 | c-ares is an asynchronous resolver library. Prior to 1.34.7, ares_dns_parse() trusts the attacker-controlled ANCOUNT, NSCOUNT, and ARCOUNT fields before confirming that the DNS response contains enough bytes for the claimed records. Because process_answer() invokes parsing before transaction ID and question validation, a malicious DNS response can cause ares_dns_record_rr_prealloc() and ares_array_set_size() to reserve disproportionate heap memory for a tiny message. Repeated responses create large allocation and release cycles that can degrade or deny name resolution, without causing memory corruption or information disclosure. This issue is fixed in version 1.34.7. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libcrypto3 | 3.5.6-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libssl3 | 3.5.6-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libcrypto3 | 3.5.6-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libssl3 | 3.5.6-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.6-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.6-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libssl3 | 3.5.6-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libcrypto3 | 3.5.6-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libssl3 | 3.5.6-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libcrypto3 | 3.5.6-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libssl3 | 3.5.6-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libssl3 | 3.5.6-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libcrypto3 | 3.5.6-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libcrypto3 | 3.5.6-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-59846 | libssh2 | 1.11.1-r1 | A flaw was found in libssh. A malicious username expanded through %r in ProxyCommand handling can inject shell metacharacters, exposing environment variables and causing unintended shell behavior. — /lib/apk/db/installed |
ghcr.io/voxpupuli/r10k
Downloads
ghcr.io/voxpupuli/r10k:latest (2026-08-27)
Trivy
CRITICAL 15
HIGH 55
MEDIUM 69
LOW 67
UNKNOWN 3
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-123158 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r2 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-60002 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Use-after-free vulnerability during host key re-exchange on the client side — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-123158 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r2 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-60002 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Use-after-free vulnerability during host key re-exchange on the client side — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-123158 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r2 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-60002 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Use-after-free vulnerability during host key re-exchange on the client side — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-110264 | ruby | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in regular expression compiler — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-89078 | ruby | 3.4.9-r0 | 3.4.12-r0 | ruby: double free issue in regular expression parser — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-93577 | ruby | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in regular expression compiler — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-97229 | ruby | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in CI/CD regular expression compiler — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-110264 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in regular expression compiler — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-89078 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | ruby: double free issue in regular expression parser — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-93577 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in regular expression compiler — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-97229 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | ruby: integer overflow issue in CI/CD regular expression compiler — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r1 | 1.2.1-r0 | brotli: Out-of-Bounds Write in Google Brotli Decoder — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | zlib: zlib: Heap buffer overflow in gz_vacate() allows arbitrary code execution — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-80212 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | resolv: resolv gem: Denial of Service via uncontrolled memory growth from crafted DNS responses — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-92392 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: HTTP/2 upload Use-After-Free — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-80212 | ruby | 3.4.9-r0 | 3.4.12-r0 | resolv: resolv gem: Denial of Service via uncontrolled memory growth from crafted DNS responses — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-89161 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-89157 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Out-of-bounds write via large pattern input — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-86145 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-103111 | pcre2 | 10.47-r1 | 10.49-r0 | pcre2: pcre2: Out-of-bounds write via crafted regular expression — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-60000 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Denial of Service via excessive GSSAPI authentication attempts — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-59999 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH sshd: Security bypass due to incorrect handling of forwarding and tunneling options — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-60000 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Denial of Service via excessive GSSAPI authentication attempts — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-59999 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH sshd: Security bypass due to incorrect handling of forwarding and tunneling options — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-113351 | libexpat | 2.8.3-r0 | 2.10.0-r0 | expat: expat: Denial of Service via improper memory tracking in XML_ParserReset — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-115506 | libexpat | 2.8.3-r0 | 2.10.0-r0 | expat: expat: Denial of Service via delayed entity amplification detection — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-117610 | libexpat | 2.8.3-r0 | 2.10.0-r0 | expat: expat: Denial of Service via NULL pointer dereference in external entity parsing — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-118370 | libexpat | 2.8.3-r0 | 2.10.0-r0 | expat: expat: Denial of Service via integer overflow during XML attribute parsing — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-66046 | libexpat | 2.8.3-r0 | 2.8.4-r0 | expat: Expat: Denial of Service via quadratic complexity in attribute processing — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-76641 | libexpat | 2.8.3-r0 | 2.8.4-r0 | expat: Expat: Denial of Service via XML external entity parsing — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-76956 | libexpat | 2.8.3-r0 | 2.8.4-r0 | libexpat: libexpat: Denial of Service via hash flooding attack with crafted XML — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-76957 | libexpat | 2.8.3-r0 | 2.8.4-r0 | libexpat: libexpat: Memory corruption vulnerability allows arbitrary code execution or denial of service — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-77214 | libexpat | 2.8.3-r0 | 2.9.0-r0 | expat: expat: Information disclosure via heap buffer over-read in XML_ParseBuffer — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-93990 | libexpat | 2.8.3-r0 | 2.8.5-r0 | expat: Expat: XML Injection via Malformed UTF-16 Input — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-58050 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | libssh2: libssh2: Heap buffer overflow via integer overflow in publickey attribute allocation — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-60000 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Denial of Service via excessive GSSAPI authentication attempts — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-59999 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH sshd: Security bypass due to incorrect handling of forwarding and tunneling options — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-92392 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: HTTP/2 upload Use-After-Free — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-123864 | llhttp | 9.4.1-r0 | 9.4.4-r0 | nodejs: nodejs: Information disclosure via HTTPS parser re-entrancy — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-107891 | musl | 1.2.6-r2 | 1.2.6-r3 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.6-r2 | 1.2.6-r3 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-56853 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | net/http: golang: Go net/http: Unencrypted HTTP/2 connections vulnerable to Denial of Service — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-56858 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | html/template: golang: Go html/template: Cross-Site Scripting via pathological input — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-56859 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | encoding/xml: golang: Go: Denial of Service via XML decoding recursion depth issue — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-46600 | stdlib | v1.26.2 | 1.26.6, 1.27.0-rc.3 | golang.org/x/net/dns/dnsmessage: golang.org/x/net/dns/dnsmessage: Denial of Service via invalid DNS record parsing — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-56860 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | net/url: golang: golang net/url: Denial of Service from quadratic complexity in path resolution — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-111760 | git | 2.54.0-r0 | 2.54.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-114466 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-27145 | stdlib | v1.26.2 | 1.25.11, 1.26.4 | crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-111943 | stdlib | v1.26.2 | 1.26.10, 1.27.3 | crypto/x509: golang: crypto/x509: Man-in-the-middle attacks via untrusted intermediate certificates — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-42504 | stdlib | v1.26.2 | 1.25.11, 1.26.4 | mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-105437 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-33811 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-42499 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net/mail: golang: net/mail: Denial of Service via pathological email address parsing — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-39836 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net: golang: Go net package: Denial of Service via NUL byte in Dial and LookupPort on Windows — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-39822 | stdlib | v1.26.2 | 1.25.12, 1.26.5, 1.27.0-rc.2 | golang: Go os.Root: Symlink following vulnerability allows directory traversal — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-39821 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-39820 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net/mail: golang: Go net/mail: Denial of Service via crafted email inputs — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-56862 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | crypto/tls: golang: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-105437 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-78667 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang: golang: Denial of Service via crafted HTTP Range headers — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-78669 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-97031 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-33818 | stdlib | v1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-111760 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| HIGH | CVE-2026-33814 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame — usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-114466 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59995 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: sftp client allows attacker to control downloaded file location — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-97032 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: net/http: Denial of Service via concurrent HPACK encoder modification — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-97054 | stdlib | v1.26.2 | 1.26.11, 1.27.4 | net/http: golang: net/http: Denial of Service via race condition when handling oversized HTTP/1 requests — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-73283 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Tunnel forwarding restriction bypass — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-73282 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Information disclosure and data corruption via use-after-free in ssh client — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-60001 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Brute-force attacks facilitated due to insufficient authentication delay — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59998 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Undocumented GSSAPIStrictAcceptorCheck behavior impacts security in Windows Active Directory — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59997 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: SFTP security bypass due to command-line argument parsing flaw — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59996 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: `scp` file misplacement vulnerability during remote copy — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59995 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: sftp client allows attacker to control downloaded file location — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-39823 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | html/template: golang: Go html/template: Cross-Site Scripting via improper URL escaping in meta tag content — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-39825 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | net/http/httputil: golang: net/http/httputil: ReverseProxy forwards hidden query parameters, potentially bypassing security controls — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-39826 | stdlib | v1.26.2 | 1.25.10, 1.26.3 | html/template: golang: html/template: Cross-site scripting due to incorrect script tag escaping — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | Improper Restriction of Operations within the Bounds of a Memory Buffe ... — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-80213 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | resolv: Resolv gem: DNS allowlist and egress bypass, and cache poisoning via crafted hostnames — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-42505 | stdlib | v1.26.2 | 1.25.12, 1.26.5, 1.27.0-rc.2 | crypto/tls: golang: Go crypto/tls: Information disclosure in Encrypted Client Hello — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-42507 | stdlib | v1.26.2 | 1.25.11, 1.26.4 | net/textproto: golang: Golang net/textproto: Misleading error messages via input injection — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-56866 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang: golang: Cross-user response poisoning via desynchronized HTTP CONNECT connections — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-78659 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang.org/x/net/http2: golang: net/http: Denial of Service via HTTP/2 trailer header memory exhaustion — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-80213 | ruby | 3.4.9-r0 | 3.4.12-r0 | resolv: Resolv gem: DNS allowlist and egress bypass, and cache poisoning via crafted hostnames — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | GHSA-r6vf-943r-2wvw | minitar | 1.1.0 | ~> 1.1.1, >= 1.2.0 | minitar path traversal vulnerability on Windows with a maliciously crafted tarball — Ruby |
| MEDIUM | CVE-2026-78660 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang: golang.org/x/net/http2: net/http: HTTP response smuggling via malformed HTTP/2 framing headers — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-78663 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: golang: flow control limit bypass via double refund in HTTP/2 server — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-94439 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/http: golang: net/http: HTTP request smuggling via improper handling of HTTP/1 CONNECT responses — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-94440 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | net/textproto: mime/multipart: golang: golang: Denial of Service via memory limit bypass in multipart form parsing — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-89160 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Denial of Service via out-of-bounds read during invalid UTF matching — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-89158 | pcre2 | 10.47-r1 | 10.48-r0 | PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-89156 | pcre2 | 10.47-r1 | 10.48-r0 | PCRE2: PCRE2: Out-of-bounds read via invalid UTF data during JIT fallback — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-73283 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Tunnel forwarding restriction bypass — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-73282 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Information disclosure and data corruption via use-after-free in ssh client — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-60001 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Brute-force attacks facilitated due to insufficient authentication delay — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59998 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Undocumented GSSAPIStrictAcceptorCheck behavior impacts security in Windows Active Directory — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59997 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: SFTP security bypass due to command-line argument parsing flaw — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59996 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: `scp` file misplacement vulnerability during remote copy — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59995 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: sftp client allows attacker to control downloaded file location — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-94448 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | html/template: golang: golang: cross-site scripting via consecutive expressions in JavaScript template literals — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-97030 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | html/template: golang: html/template: Cross-site scripting via improper escaping of yield keyword — usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-73283 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Tunnel forwarding restriction bypass — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-73282 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Information disclosure and data corruption via use-after-free in ssh client — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-60001 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Brute-force attacks facilitated due to insufficient authentication delay — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59998 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: Undocumented GSSAPIStrictAcceptorCheck behavior impacts security in Windows Active Directory — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59997 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: SFTP security bypass due to command-line argument parsing flaw — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-59996 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: `scp` file misplacement vulnerability during remote copy — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-19931 | curl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via incorrect connection reuse with Negotiate authentication — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-82208 | curl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Improper certificate validation when using wolfSSL CA cache — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-92388 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: FTP wildcard write callback mixup — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-113408 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-114467 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-114469 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-113408 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-114467 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-107496 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-95691 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-95692 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-19931 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via incorrect connection reuse with Negotiate authentication — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-82208 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Improper certificate validation when using wolfSSL CA cache — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-92388 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: FTP wildcard write callback mixup — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-102633 | libexpat | 2.8.3-r0 | 2.9.0-r0 | expat: expat: Denial of Service via integer overflow in expat_realloc — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2025-15661 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | libssh2: libssh2: Information disclosure and denial of service via crafted SFTP response — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-95692 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-95691 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-107496 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-58051 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | libssh2: libssh2: Denial of service or information disclosure via malformed SSH publickey response — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-66032 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | libssh2: libssh2: Arbitrary code execution via double-free in SFTP session — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-66033 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | libssh2: libssh2: Denial of Service via integer underflow in AES-GCM cipher negotiation — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-66034 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | libssh2: libssh2: Information disclosure and potential arbitrary code execution via heap out-of-bounds read — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-58055 | nghttp2-libs | 1.69.0-r0 | 1.70.0-r0 | nghttp2: nghttp2: HTTP Request/Response Smuggling and Response-Queue Poisoning via ambiguous HTTP/1.1 Upgrade requests — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| MEDIUM | CVE-2026-66035 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | libssh2: libssh2: Arbitrary code execution via heap buffer overflow during SSH negotiation — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87863 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: Hsts Response Erases Persisted Entries — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87864 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: IMAP APPEND plus CRLF conversion command injection — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87865 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: knownhost callback mismatches key as missing — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87866 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: wolfSSL public-key pinning bypass — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92386 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie aborts cookie jar load — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92387 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: never-ending loop via server response omission — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92389 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: TFTP direction confusion — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92390 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: -J no-clobber guarantee bypassed with 103 early hints — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92391 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: curl_mime_free stack overflow by recursion — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-94265 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: Authorization: Negotiate sent to foreign origin — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-94266 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: password leak in CURLINFO_EFFECTIVE_URL — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-56857 | stdlib | v1.26.2 | 1.26.9, 1.27.2 | os: golang: golang: Directory traversal via Windows junction handling — usr/local/bin/supercronic-linux-amd64 |
| LOW | CVE-2026-88823 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Message authentication bypass via zero-length AAD update — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-88822 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-107928 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: info leak uploading over WebSockets with GnuTLS — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-107929 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: local interface connection reuse mixup — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-13608 | curl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Authentication bypass in OpenLDAP SASL negotiation via Man-in-the-Middle (MITM) attack — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-18924 | curl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Use-after-free in HTTP/2 Server Push with shared connections — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-80229 | curl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Memory corruption vulnerability via OpenSSL 3 provider use-after-free — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-80230 | curl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Public key pinning bypass allows unauthenticated connections — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-80231 | curl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Incorrect HTTPS connection reuse with Native CA Store — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-80255 | curl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure due to secure cookie attribute bypass — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-82209 | curl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via improper Public Suffix List boundary check — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86409 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: stale SigV4 headers sent unintended — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86410 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: redirect to SFTP or SCP bypasses host verification — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86411 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: FTP connection reuse inherits client-certificate — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86412 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie erases cookie jar — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86413 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: Negotiate credentials sent to redirected origin — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86414 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: leaking host credentials to HTTP proxy — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86415 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: auto client cert connection reuse mixup — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87861 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: cross-origin reuse of a Negotiate connection — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87862 | curl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: HSTS cache import drops longer-lived child — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86411 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: FTP connection reuse inherits client-certificate — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86412 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie erases cookie jar — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86413 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: Negotiate credentials sent to redirected origin — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86414 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: leaking host credentials to HTTP proxy — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86415 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: auto client cert connection reuse mixup — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87861 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: cross-origin reuse of a Negotiate connection — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87862 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: HSTS cache import drops longer-lived child — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87863 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: Hsts Response Erases Persisted Entries — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87864 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: IMAP APPEND plus CRLF conversion command injection — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87865 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: knownhost callback mismatches key as missing — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-73281 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: ssh-agent allows remote execution of local operations — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-87866 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: wolfSSL public-key pinning bypass — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92386 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie aborts cookie jar load — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92387 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: never-ending loop via server response omission — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92389 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: TFTP direction confusion — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92390 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: -J no-clobber guarantee bypassed with 103 early hints — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-92391 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: curl_mime_free stack overflow by recursion — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-94265 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: Authorization: Negotiate sent to foreign origin — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-94266 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: password leak in CURLINFO_EFFECTIVE_URL — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-73281 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: ssh-agent allows remote execution of local operations — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-88822 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-88823 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Message authentication bypass via zero-length AAD update — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-107928 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: info leak uploading over WebSockets with GnuTLS — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-107929 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: local interface connection reuse mixup — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-13608 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Authentication bypass in OpenLDAP SASL negotiation via Man-in-the-Middle (MITM) attack — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-89162 | pcre2 | 10.47-r1 | 10.48-r0 | pcre2: PCRE2: Information disclosure via pcre2_serialize_encode — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-18924 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Use-after-free in HTTP/2 Server Push with shared connections — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-80229 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Memory corruption vulnerability via OpenSSL 3 provider use-after-free — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-80230 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Public key pinning bypass allows unauthenticated connections — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-80231 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Incorrect HTTPS connection reuse with Native CA Store — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-80255 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: curl: Information disclosure due to secure cookie attribute bypass — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-82209 | libcurl | 8.21.0-r0 | 8.22.0-r0 | curl: libcurl: Information disclosure via improper Public Suffix List boundary check — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86409 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: stale SigV4 headers sent unintended — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-73281 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | openssh: OpenSSH: ssh-agent allows remote execution of local operations — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| LOW | CVE-2026-86410 | libcurl | 8.21.0-r0 | 8.23.0-r0 | curl: curl: redirect to SFTP or SCP bypasses host verification — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| UNKNOWN | CVE-2026-80256 | libcurl | 8.21.0-r0 | 8.22.0-r0 | Title Not Available — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| UNKNOWN | CVE-2026-80256 | curl | 8.21.0-r0 | 8.22.0-r0 | Title Not Available — ghcr.io/voxpupuli/r10k:latest (alpine 3.24.1) |
| UNKNOWN | CVE-2026-39824 | golang.org/x/sys | v0.43.0 | 0.44.0 | Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows — usr/local/bin/supercronic-linux-amd64 |
Grype
CRITICAL 32
HIGH 112
MEDIUM 36
LOW 12
UNKNOWN 2
NVD/CPE filtered 53
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-110264 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-19931 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86413 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86413 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-60002 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-60002 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-60002 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-92388 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-92388 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86414 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87861 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86414 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87861 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-93577 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-93577 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-18924 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-18924 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-89078 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-89078 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87866 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87866 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86411 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86411 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-110264 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r1 | 1.2.1-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-97229 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-97229 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| CRITICAL | GO-2026-6612 | stdlib | go1.26.2 | 1.26.9 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. — /usr/local/bin/supercronic-linux-amd64 |
| CRITICAL | CVE-2026-19931 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-94265 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-94265 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-77214 | libexpat | 2.8.3-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-59999 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-117610 | libexpat | 2.8.3-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-58050 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-86145 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-59999 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-89161 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-93990 | libexpat | 2.8.3-r0 | 2.8.5-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-95692 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95692 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-80255 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80255 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-66035 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-76957 | libexpat | 2.8.3-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80231 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-113351 | libexpat | 2.8.3-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-13608 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-13608 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-115506 | libexpat | 2.8.3-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80231 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6613 | stdlib | go1.26.2 | 1.26.9, 1.27.2 | When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6610 | stdlib | go1.26.2 | 1.26.9 | Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-94266 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-94266 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-89157 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107496 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-107496 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-58051 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-80230 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80230 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-123864 | llhttp | 9.4.1-r0 | 9.4.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-76641 | libexpat | 2.8.3-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82209 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82209 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-95691 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95691 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-105437 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-76956 | libexpat | 2.8.3-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-103111 | pcre2 | 10.47-r1 | 10.49-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-88823 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-88823 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-105437 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80212 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-59999 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-80212 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82208 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-82208 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-118370 | libexpat | 2.8.3-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-102633 | libexpat | 2.8.3-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86415 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86415 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-66034 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-92389 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86410 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86410 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-4918 | stdlib | go1.26.2 | 1.25.10, 1.26.3 | 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. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6611 | stdlib | go1.26.2 | 1.26.9 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-92386 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87863 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86412 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92386 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87863 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86412 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87864 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87864 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6603 | stdlib | go1.26.2 | 1.26.9 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-66046 | libexpat | 2.8.3-r0 | 2.8.4-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87862 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87862 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92387 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92387 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86409 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86409 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92391 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92391 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-q339-8rmv-2mhv | erb | 4.0.4 | 4.0.4.1 | ERB has an @_init deserialization guard bypass via def_module / def_method / def_class — /usr/lib/ruby/gems/3.4.0/specifications/default/erb-4.0.4.gemspec |
| HIGH | CVE-2026-92392 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r2 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r2 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r2 | /lib/apk/db/installed |
| HIGH | GO-2026-5026 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | 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". — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-92392 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6089 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-5972 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6090 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-80229 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.6-r2 | 1.2.6-r3 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl | 1.2.6-r2 | 1.2.6-r3 | /lib/apk/db/installed |
| HIGH | CVE-2026-92390 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-80229 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92390 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-5037 | stdlib | go1.26.2 | 1.25.11, 1.26.4 | (*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, ".") to execute repeatedly on the same input hostname. With a large DNS SAN list, verification costs scaled quadratically based on the number of SAN entries multiplied by the hostname's label count. Because x509.Verify validates hostnames before building the certificate chain, this overhead occurred even for untrusted certificates. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-87865 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87865 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6605 | stdlib | go1.26.2 | 1.26.9, 1.27.2 | When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-60000 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-60000 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-92389 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107928 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107928 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6607 | stdlib | go1.26.2 | 1.26.9, 1.27.2 | Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-6608 | stdlib | go1.26.2 | 1.26.9, 1.27.2 | Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-107929 | curl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107929 | libcurl | 8.21.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6617 | stdlib | go1.26.2 | 1.26.9 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | GO-2026-4971 | stdlib | go1.26.2 | 1.25.10, 1.26.3 | The Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0). — /usr/local/bin/supercronic-linux-amd64 |
| HIGH | CVE-2026-66033 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-66032 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | /lib/apk/db/installed |
| HIGH | CVE-2026-60000 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-80213 | ruby-libs | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-80213 | ruby | 3.4.9-r0 | 3.4.12-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59996 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114469 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59998 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59998 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59998 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59997 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59997 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59997 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-73282 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-73282 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-73282 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2025-15661 | libssh2 | 1.11.1-r3 | 1.11.1-r4 | /lib/apk/db/installed |
| MEDIUM | GO-2026-6218 | stdlib | go1.26.2 | 1.25.13, 1.26.6, 1.27.0-rc.3 | Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte buffer using index-based backtracking for '..' segments, eliminating the quadratic time complexity and significantly reducing memory allocations. — /usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | GO-2026-6809 | stdlib | go1.26.2 | 1.26.10, 1.27.3 | On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy. — /usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | GO-2026-6859 | stdlib | go1.26.2 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | GO-2026-5856 | stdlib | go1.26.2 | 1.25.12, 1.26.5, 1.27.0-rc.2 | Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of pre-shared key identities in the unencrypted client hello. — /usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | GO-2026-5039 | stdlib | go1.26.2 | 1.25.11, 1.26.4 | When returning errors, functions in the net/textproto package would include its input as part of the error. This might allow an attacker to inject misleading content to errors that are printed or logged. — /usr/local/bin/supercronic-linux-amd64 |
| MEDIUM | CVE-2026-60001 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-60001 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-60001 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-89156 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59995 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59996 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59995 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59996 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-59995 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-89158 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-58055 | nghttp2-libs | 1.69.0-r0 | 1.70.0-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-88822 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-88822 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-89160 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-73283 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| LOW | CVE-2026-73283 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| LOW | CVE-2026-73283 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| LOW | CVE-2026-89162 | pcre2 | 10.47-r1 | 10.48-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-73281 | openssh-keygen | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| LOW | CVE-2026-73281 | openssh-client-default | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| LOW | CVE-2026-73281 | openssh-client-common | 10.3_p1-r0 | 10.3_p1-r1 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-113408 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-113408 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | GHSA-x2f5-4prf-w687 | json | 2.9.1 | 2.19.9 | Ruby json: JSON generator heap buffer overflow when streaming to an IO — /usr/lib/ruby/gems/3.4.0/specifications/default/json-2.9.1.gemspec |
| UNKNOWN | CVE-2026-80256 | curl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
| UNKNOWN | CVE-2026-80256 | libcurl | 8.21.0-r0 | 8.22.0-r0 | /lib/apk/db/installed |
Filtered NVD/CPE matches (53)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-132825 | ruby | 3.4.9-r0 | Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-59850 | libssh2 | 1.11.1-r3 | A flaw was found in libssh. If data packets are processed after a channel is closed, channel data callbacks can be invoked after the associated data has already been freed, leading to crashes or possible use-after-free conditions. — /lib/apk/db/installed | |
| HIGH | CVE-2026-132825 | ruby-libs | 3.4.9-r0 | Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libssl3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libssl3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libcrypto3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libssl3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-54873 | libcrypto3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-54873 | libssl3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libcrypto3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libssl3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libcrypto3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59845 | libssh2 | 1.11.1-r3 | A flaw was found in libssh. When ProxyCommand is used, an unchecked fork() failure can be stored as process ID -1; during cleanup, signals may then be sent across the caller's accessible process tree, leading to local denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100407 | git | 2.54.0-r0 | Git for Windows is the Windows port of Git. From 2.44.0.windows.1 until 2.55.0.windows.3, the git-credential-wincred store operation in contrib/credential/wincred/git-credential-wincred.c uses _scwprintf() to size a formatted wide-character credential buffer without space for the terminating NUL when both password and oauth_refresh_token are present. The operation also passes a byte count to _snwprintf_s() where a wide-character count is required, allowing the terminator to be written one WCHAR past the heap allocation before CredWriteW() persists the credential. The resulting fixed two-byte NUL overwrite can terminate the helper with Windows heap-corruption status and can cause git credential approve to report success even though the OAuth credential was not stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100408 | git | 2.54.0-r0 | Git for Windows is the Windows port of Git. From 2.43.0.windows.1 until 2.55.0.windows.3, when a matching git:* credential exists in Windows Credential Manager and a git-credential-wincred erase input includes a password field, the operation in contrib/credential/wincred/git-credential-wincred.c allocates a buffer of exactly CredentialBlobSize bytes in match_cred_password() and then uses wcsncpy_s() to copy the corresponding number of wide characters plus a terminating NUL. The destination capacity is also supplied in bytes instead of WCHAR elements, allowing a fixed two-byte NUL write past the allocation before the password comparison determines whether CredDeleteW() should remove the credential; erase without a password field does not enter this comparison path. The helper can terminate with Windows heap-corruption status, and git credential reject can appear successful while the rejected credential remains stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59848 | libssh2 | 1.11.1-r3 | A flaw was found in libssh. A malicious SFTP server can send responses for unknown request IDs that libssh clients keep queued indefinitely, causing unbounded memory growth and client-side denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75806 | libcrypto3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75806 | libssl3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59843 | libssh2 | 1.11.1-r3 | A flaw was found in libssh. A remote authenticated peer can advertise a zero maximum packet size in SSH_MSG_CHANNEL_OPEN, causing later channel writes to loop indefinitely and consume CPU, leading to denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-59844 | libssh2 | 1.11.1-r3 | A flaw was found in libssh. A remote authenticated client can issue SSH_FXP_READ requests with an arbitrarily large length, causing a libssh SFTP server to allocate excessive memory and potentially exhaust it through repeated requests. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libcrypto3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libssl3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libcrypto3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libssl3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libcrypto3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libssl3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libcrypto3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libssl3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libssl3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libssl3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libcrypto3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libcrypto3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libssl3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libcrypto3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-59846 | libssh2 | 1.11.1-r3 | A flaw was found in libssh. A malicious username expanded through %r in ProxyCommand handling can inject shell metacharacters, exposing environment variables and causing unintended shell behavior. — /lib/apk/db/installed |
ghcr.io/voxpupuli/renovate
Downloads
ghcr.io/voxpupuli/renovate:latest (2026-11-21)
Trivy
HIGH 12
MEDIUM 21
LOW 1
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2024-21907 | Newtonsoft.Json | 10.0.2 | 13.0.1 | Improper Handling of Exceptional Conditions in Newtonsoft.Json — usr/local/renovate/lib/modules/manager/nuget/__fixtures__/packages.props |
| HIGH | CVE-2017-8700 | Microsoft.AspNetCore.Mvc.Core | 1.1.3 | 1.0.6, 1.1.6 | ASP.NET: CORS not properly applied — usr/local/renovate/lib/modules/manager/nuget/__fixtures__/packages.props |
| HIGH | CVE-2026-87018 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via TLS renegotiation with mismatched certificate — Node.js |
| HIGH | CVE-2026-19534 | undici | 6.27.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: Denial of Service via unrequested WebSocket subprotocol — Node.js |
| HIGH | CVE-2026-109869 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unhandled stream error on excessive content encodings — Node.js |
| HIGH | CVE-2026-109383 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Certificate validation bypass via dropped TLS options in Agent — Node.js |
| HIGH | CVE-2026-73566 | tar | 7.5.19 | 7.5.21 | tar: node-tar: Denial of Service via crafted long-path tar archive — Node.js |
| HIGH | CVE-2026-69192 | ip-address | 10.2.0 | 10.3.1 | ip-address: ip-address: Inconsistent IP address parsing leads to Server-Side Request Forgery (SSRF) and trust-boundary bypass — Node.js |
| HIGH | CVE-2026-102276 | brace-expansion | 5.0.7 | 5.0.10, 3.0.7, 2.1.5, 1.1.19 | brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns — Node.js |
| HIGH | CVE-2026-102278 | brace-expansion | 5.0.7 | 5.0.11, 3.0.8, 2.1.6, 1.1.20 | brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns — Node.js |
| HIGH | CVE-2026-14257 | brace-expansion | 5.0.7 | 5.0.8, 3.0.3, 2.1.3, 1.1.17 | brace-expansion: Brace-expansion: Denial of Service via memory exhaustion in expand() function — Node.js |
| HIGH | CVE-2026-69152 | brace-expansion | 5.0.7 | 1.1.18, 2.1.4, 3.0.6, 5.0.9 | brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation — Node.js |
| MEDIUM | CVE-2026-85024 | undici | 6.27.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: Denial of Service via unhandled error in WebSocket permessage-deflate decompression — Node.js |
| MEDIUM | CVE-2026-16729 | undici | 6.27.0 | 6.28.0, 7.29.0, 8.9.0 | undici: Undici: Cookie attribute injection allows bypassing security protections — Node.js |
| MEDIUM | CVE-2026-16728 | undici | 6.27.0 | 6.28.0, 7.29.0, 8.9.0 | undici: undici: Response desynchronization via retry interceptor with mismatched Content-Length — Node.js |
| MEDIUM | CVE-2026-15157 | undici | 6.27.0 | 6.28.0, 7.29.0, 8.9.0 | undici: undici: HTTP header injection via unvalidated blob-like body type property — Node.js |
| MEDIUM | CVE-2026-109932 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unbounded WebSocket PONG buffering — Node.js |
| MEDIUM | CVE-2026-109924 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via memory exhaustion in EventSource client — Node.js |
| MEDIUM | CVE-2026-102277 | brace-expansion | 5.0.7 | 5.0.12, 3.0.9, 2.1.7, 1.1.21 | brace-expansion: brace-expansion: Denial of Service via crafted brace patterns — Node.js |
| MEDIUM | CVE-2026-118773 | glob | 10.5.0 | 14.0.2 | glob: glob: Denial of Service (DoS) via incomplete traversal cancellation — Node.js |
| MEDIUM | CVE-2026-118773 | glob | 13.0.6 | 14.0.2 | glob: glob: Denial of Service (DoS) via incomplete traversal cancellation — Node.js |
| MEDIUM | CVE-2026-104844 | postcss-selector-parser | 7.1.4 | 7.1.6, 6.1.5 | postcss-selector-parser: postcss-selector-parser: Denial of Service via crafted CSS selectors — Node.js |
| MEDIUM | CVE-2026-118764 | minimatch | 9.0.9 | 11.0.1 | minimatch: minimatch: Denial of Service via crafted glob pattern expansion — Node.js |
| MEDIUM | CVE-2026-118764 | minimatch | 10.2.6 | 11.0.1 | minimatch: minimatch: Denial of Service via crafted glob pattern expansion — Node.js |
| MEDIUM | CVE-2026-118764 | minimatch | 10.2.5 | 11.0.1 | minimatch: minimatch: Denial of Service via crafted glob pattern expansion — Node.js |
| MEDIUM | CVE-2026-69198 | ip-address | 10.2.0 | 10.2.2 | ip-address: ip-address: Server-Side Request Forgery (SSRF) and trust-boundary bypass — Node.js |
| MEDIUM | CVE-2026-54272 | ip-address | 10.2.0 | 10.2.1 | ip-address: ip-address: Server-Side Request Forgery via IPv4-mapped/NAT64 IPv6 address misclassification — Node.js |
| MEDIUM | CVE-2026-111997 | ip-address | 10.2.0 | 10.7.4 | ip-address: ip-address: Denial of Service via excessive percent characters in IPv6 address input — Node.js |
| MEDIUM | CVE-2026-101913 | ip-address | 10.2.0 | 10.5.1 | ip-address: ip-address: Security bypass via incomplete IPv6 link-local address validation — Node.js |
| MEDIUM | CVE-2026-101912 | ip-address | 10.2.0 | 10.7.1 | ip-address: ip-address: Access control bypass via cross-family subnet comparison — Node.js |
| MEDIUM | CVE-2026-101911 | ip-address | 10.2.0 | 10.7.1 | ip-address: ip-address: Denial of Service via unbounded IPv6 address parsing — Node.js |
| MEDIUM | CVE-2026-101910 | ip-address | 10.2.0 | 10.5.1 | ip-address: ip-address: Security boundary bypass via unclassified NAT64 local-use address range — Node.js |
| MEDIUM | CVE-2026-118773 | glob | 13.0.6 | 14.0.2 | glob: glob: Denial of Service (DoS) via incomplete traversal cancellation — Node.js |
| LOW | CVE-2026-18540 | undici | 6.27.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: HTTP response splitting via retry interceptor — Node.js |
Grype
HIGH 11
MEDIUM 22
LOW 1
NVD/CPE filtered 34
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | GHSA-rgw5-rvv9-x895 | brace-expansion | 5.0.7 | 5.0.9 | brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GHSA-mh99-v99m-4gvg | brace-expansion | 5.0.7 | 5.0.8 | brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GHSA-r292-9mhp-454m | tar | 7.5.19 | 7.5.21 | node-tar: Uncontrolled recursion in mapHas/filesFilter allows uncatchable stack-overflow DoS via crafted long-path tar with member selection — /usr/local/lib/node_modules/npm/node_modules/tar/package.json |
| HIGH | GHSA-qhr7-859c-m2p7 | brace-expansion | 5.0.7 | 5.0.11 | brace-expansion: DoS via uncontrolled recursion on nested brace groups causing stack exhaustion — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GO-2026-5970 | golang.org/x/text | v0.37.0 | 0.39.0 | A norm.Iter can enter an infinite loop when handling input containing invalid UTF-8 bytes. — /usr/bin/yq |
| HIGH | GHSA-mwp4-54f8-5fhr | ip-address | 10.2.0 | 10.3.1 | ip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and trust-boundary bypass — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| HIGH | GHSA-6j4f-fj2g-mc7p | brace-expansion | 5.0.7 | 5.0.10 | brace-expansion: DoS via uncontrolled recursion in parseCommaParts causing stack exhaustion — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GHSA-rfgv-xxqx-mfg5 | undici | 6.27.0 | 6.28.1 | undici vulnerable to Denial of Service via unrequested WebSocket subprotocol — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | GHSA-xjj6-f33q-929c | undici | 6.27.0 | 6.29.1 | undici vulnerable to Denial of Service via unhandled error on excessive content-encodings — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | GHSA-2m5v-pch6-74hx | undici | 6.27.0 | 6.29.1 | undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | GHSA-qrxm-fqhp-jwvm | undici | 6.27.0 | 6.29.1 | undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-3g3m-2fjr-6pw4 | glob | 13.0.6 | 14.0.2 | Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal — /usr/local/lib/node_modules/npm/node_modules/glob/package.json |
| MEDIUM | GHSA-g3hv-75wg-m249 | minimatch | 10.2.5 | 11.0.1 | minimatch has potential denial of service via globparts amplification — /usr/local/lib/node_modules/npm/node_modules/minimatch/package.json |
| MEDIUM | GHSA-g3hv-75wg-m249 | minimatch | 10.2.6 | 11.0.1 | minimatch has potential denial of service via globparts amplification — /usr/local/renovate/node_modules/.pnpm/[email protected]/node_modules/minimatch/package.json |
| MEDIUM | GHSA-g3hv-75wg-m249 | minimatch | 9.0.9 | 11.0.1 | minimatch has potential denial of service via globparts amplification — /usr/local/renovate/node_modules/.pnpm/[email protected]/node_modules/minimatch/package.json |
| MEDIUM | GHSA-rxp7-6hxx-x8q5 | ip-address | 10.2.0 | 10.7.4 | ip-address: Address6 matches a zone identifier in quadratic time ahead of its length limit, allowing a single long string to stall the process — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-4qv8-2p9j-2685 | undici | 6.27.0 | 6.29.1 | undici vulnerable to Denial of Service via unbounded memory in the EventSource parser — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-9fm3-97px-rjf6 | undici | 6.27.0 | 6.29.1 | undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-8xcm-r25x-g524 | undici | 6.27.0 | 6.28.0 | undici vulnerable to downstream response desynchronization via retry interceptor — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-v3r7-h72x-cjcm | undici | 6.27.0 | 6.28.0 | undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-m8rv-5g2x-5cg5 | undici | 6.27.0 | 6.28.0 | undici vulnerable to CRLF Injection via blob-like body 'type' property — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-3g3m-2fjr-6pw4 | glob | 13.0.6 | 14.0.2 | Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal — /usr/local/renovate/node_modules/.pnpm/[email protected]/node_modules/glob/package.json |
| MEDIUM | GHSA-3g3m-2fjr-6pw4 | glob | 10.5.0 | 14.0.2 | Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal — /usr/local/renovate/node_modules/.pnpm/[email protected]/node_modules/glob/package.json |
| MEDIUM | GO-2026-6859 | stdlib | go1.26.9 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/bin/yq |
| MEDIUM | GHSA-j6r3-76f7-8jcv | ip-address | 10.2.0 | 10.7.1 | ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit an address outside its range — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-rj75-hqrm-r3gf | postcss-selector-parser | 7.1.4 | 7.1.6 | PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion — /usr/local/lib/node_modules/npm/node_modules/postcss-selector-parser/package.json |
| MEDIUM | GHSA-h3mg-xc3c-68pw | ip-address | 10.2.0 | 10.7.1 | ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-rpw4-54j3-4h4q | ip-address | 10.2.0 | 10.5.1 | ip-address: Address6.isLinkLocal() recognizes fe80::/64 rather than fe80::/10, allowing SSRF and trust-boundary bypass to on-link hosts — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-q2hr-2g5m-vwhr | brace-expansion | 5.0.7 | 5.0.12 | brace-expansion: Quadratic-time expansion of the `{a},b}` rewrite causes CPU denial of service — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| MEDIUM | GHSA-3wwx-pv8p-q78v | undici | 6.27.0 | 6.28.1 | undici vulnerable to Denial of Service via unhandled error in WebSocket permessage-deflate decompression — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-2vr4-cq9g-pvrc | ip-address | 10.2.0 | 10.5.1 | ip-address: no classifier recognizes the NAT64 local-use range 64:ff9b:1::/48, allowing SSRF and trust-boundary bypass — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-22jq-vg5j-6vgg | ip-address | 10.2.0 | 10.2.1 | ip-address: misclassification of IPv4-mapped/NAT64 IPv6 addresses can bypass SSRF and trust-boundary checks — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-4xrf-jv44-h6hh | ip-address | 10.2.0 | 10.2.2 | ip-address: a CIDR suffix on the parsed address suppresses special-use classification and can bypass SSRF and trust-boundary checks — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| LOW | GHSA-r53p-7pc4-xj5r | undici | 6.27.0 | 6.28.1 | undici vulnerable to downstream response splitting via retry interceptor — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
Filtered NVD/CPE matches (34)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-107493 | libssl3 | 3.5.9-r1 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.9-r1 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119373 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5MergeRowidLists() that undersizes the output buffer when merging detail=none prefix doclists. Attackers who can populate a detail=none FTS5 table with negative rowids and run a prefix MATCH query can write past the allocation, corrupting heap memory and crashing the process. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.9-r1 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.9-r1 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119374 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5DoSecureDelete() that allows attackers to write past the leaf page buffer via crafted footer key offsets. Attackers can supply a database file with a corrupted FTS5 index that, when deleted from with secure-delete enabled, corrupts heap memory and crashes the application. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.9-r1 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119586 | sqlite-libs | 3.53.4-r0 | SQLite command-line shell through 3.54.1 contains a command injection vulnerability in the .recover command that emits attacker-planted dot-commands stored in sqlite_schema.sql values verbatim. Attackers can craft a database whose schema holds a valid CREATE statement followed by a .shell or .system line, executing OS commands when victims pipe .recover output into sqlite3. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.9-r1 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.9-r1 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119379 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with the session extension contains a heap buffer overflow vulnerability in sqlite3changeset_apply() that allows attackers to corrupt heap memory by supplying crafted changesets. Attackers can repeat a table name in a second changeset block with a larger column count, causing sessionUpdateFind() to memset past the undersized aUpdateMask allocation. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.9-r1 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.9-r1 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.9-r1 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100408 | git | 2.54.1-r0 | Git for Windows is the Windows port of Git. From 2.43.0.windows.1 until 2.55.0.windows.3, when a matching git:* credential exists in Windows Credential Manager and a git-credential-wincred erase input includes a password field, the operation in contrib/credential/wincred/git-credential-wincred.c allocates a buffer of exactly CredentialBlobSize bytes in match_cred_password() and then uses wcsncpy_s() to copy the corresponding number of wide characters plus a terminating NUL. The destination capacity is also supplied in bytes instead of WCHAR elements, allowing a fixed two-byte NUL write past the allocation before the password comparison determines whether CredDeleteW() should remove the credential; erase without a password field does not enter this comparison path. The helper can terminate with Windows heap-corruption status, and git credential reject can appear successful while the rejected credential remains stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100407 | git | 2.54.1-r0 | Git for Windows is the Windows port of Git. From 2.44.0.windows.1 until 2.55.0.windows.3, the git-credential-wincred store operation in contrib/credential/wincred/git-credential-wincred.c uses _scwprintf() to size a formatted wide-character credential buffer without space for the terminating NUL when both password and oauth_refresh_token are present. The operation also passes a byte count to _snwprintf_s() where a wide-character count is required, allowing the terminator to be written one WCHAR past the heap allocation before CredWriteW() persists the credential. The resulting fixed two-byte NUL overwrite can terminate the helper with Windows heap-corruption status and can cause git credential approve to report success even though the OAuth credential was not stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119372 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with FTS3/FTS4 and SQLITE_ENABLE_FTS3_PARENTHESIS contains a use-after-free vulnerability in fts3BestSnippet() caused by dangling cached position-list pointers. Attackers can run a full-text MATCH query combining OR and NEAR operators with snippet() to read freed heap memory and crash the process. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119591 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a stack exhaustion vulnerability in countOfViewOptimization() that allows attackers to crash the host process via count(*) over a large multi-row VALUES clause. Attackers supplying SQL or a database file with a crafted view can trigger deeply nested TK_PLUS expressions whose recursive freeing in sqlite3ExprDeleteNN() exhausts the C stack, causing denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119376 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH limit by chaining COLLATE postfix operators. Attackers can supply roughly 175,000 chained COLLATE operators in SQL or an untrusted database view to trigger unbounded recursion in sqlite3WalkExprNN() and crash the process. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.9-r1 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.9-r1 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119371 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH nesting limit because common table expressions are not counted against it. Attackers can supply a WITH clause chaining tens of thousands of CTEs, via plain SQL or a view in an untrusted database file, causing unbounded selectExpander() recursion that crashes the process. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.9-r1 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119375 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains an information disclosure vulnerability that allows attackers to read uninitialized page-cache memory by supplying a WAL file with an undersized page size. Attackers can craft a database and WAL file whose oversized record payload makes queries like substr() return stale bytes, disclosing other table rows and internal pointers. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.9-r1 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119378 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a use-after-free vulnerability in the R-Tree extension that allows attackers to make applications use freed heap memory by manipulating the %_node shadow table. Attackers can supply a database declaring %_node WITHOUT ROWID or with a RAISE(IGNORE) trigger so nodeWrite() hashes nodes as 0, crashing the process after node splits. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| LOW | CVE-2022-3219 | gnupg-dirmngr | 2.4.9-r1 | GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB. — /lib/apk/db/installed | |
| LOW | CVE-2022-3219 | gnupg-gpgconf | 2.4.9-r1 | GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB. — /lib/apk/db/installed | |
| LOW | CVE-2022-3219 | gnupg-keyboxd | 2.4.9-r1 | GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB. — /lib/apk/db/installed | |
| LOW | CVE-2022-3219 | gpg | 2.4.9-r1 | GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB. — /lib/apk/db/installed | |
| LOW | CVE-2026-119377 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains an authorization bypass vulnerability in lookupName() that invokes the authorizer only for the first joined table's USING column. Attackers able to submit SQL can query a shared USING column in a RIGHT or FULL JOIN to read columns denied via sqlite3_set_authorizer() SQLITE_READ restrictions. — /lib/apk/db/installed |
ghcr.io/voxpupuli/semantic-release
Downloads
ghcr.io/voxpupuli/semantic-release:latest (2026-09-23)
Trivy
CRITICAL 4
HIGH 56
MEDIUM 72
LOW 54
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r1 | 1.2.1-r0 | brotli: Out-of-Bounds Write in Google Brotli Decoder — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| CRITICAL | CVE-2026-123158 | openssh-client-common | 10.3_p1-r1 | 10.3_p1-r2 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| CRITICAL | CVE-2026-123158 | openssh-client-default | 10.3_p1-r1 | 10.3_p1-r2 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| CRITICAL | CVE-2026-123158 | openssh-keygen | 10.3_p1-r1 | 10.3_p1-r2 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-97031 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-87018 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via TLS renegotiation with mismatched certificate — Node.js |
| HIGH | CVE-2026-19534 | undici | 6.27.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: Denial of Service via unrequested WebSocket subprotocol — Node.js |
| HIGH | CVE-2026-109869 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unhandled stream error on excessive content encodings — Node.js |
| HIGH | CVE-2026-109383 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Certificate validation bypass via dropped TLS options in Agent — Node.js |
| HIGH | CVE-2026-73566 | tar | 7.5.19 | 7.5.21 | tar: node-tar: Denial of Service via crafted long-path tar archive — Node.js |
| HIGH | CVE-2026-69192 | ip-address | 10.2.0 | 10.3.1 | ip-address: ip-address: Inconsistent IP address parsing leads to Server-Side Request Forgery (SSRF) and trust-boundary bypass — Node.js |
| HIGH | CVE-2026-102278 | brace-expansion | 5.0.9 | 5.0.11, 3.0.8, 2.1.6, 1.1.20 | brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns — Node.js |
| HIGH | CVE-2026-102276 | brace-expansion | 5.0.9 | 5.0.10, 3.0.7, 2.1.5, 1.1.19 | brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns — Node.js |
| HIGH | CVE-2026-69152 | brace-expansion | 5.0.7 | 1.1.18, 2.1.4, 3.0.6, 5.0.9 | brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation — Node.js |
| HIGH | CVE-2026-14257 | brace-expansion | 5.0.7 | 5.0.8, 3.0.3, 2.1.3, 1.1.17 | brace-expansion: Brace-expansion: Denial of Service via memory exhaustion in expand() function — Node.js |
| HIGH | CVE-2026-102278 | brace-expansion | 5.0.7 | 5.0.11, 3.0.8, 2.1.6, 1.1.20 | brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns — Node.js |
| HIGH | CVE-2026-102276 | brace-expansion | 5.0.7 | 5.0.10, 3.0.7, 2.1.5, 1.1.19 | brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns — Node.js |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | zlib: zlib: Heap buffer overflow in gz_vacate() allows arbitrary code execution — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-103111 | pcre2 | 10.48-r0 | 10.49-r0 | pcre2: pcre2: Out-of-bounds write via crafted regular expression — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.6-r2 | 1.2.6-r3 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-107891 | musl | 1.2.6-r2 | 1.2.6-r3 | musl: musl: Arbitrary code execution via integer overflow in regcomp — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-93990 | libexpat | 2.8.4-r0 | 2.8.5-r0 | expat: Expat: XML Injection via Malformed UTF-16 Input — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-77214 | libexpat | 2.8.4-r0 | 2.9.0-r0 | expat: expat: Information disclosure via heap buffer over-read in XML_ParseBuffer — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-118370 | libexpat | 2.8.4-r0 | 2.10.0-r0 | expat: expat: Denial of Service via integer overflow during XML attribute parsing — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-117610 | libexpat | 2.8.4-r0 | 2.10.0-r0 | expat: expat: Denial of Service via NULL pointer dereference in external entity parsing — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-115506 | libexpat | 2.8.4-r0 | 2.10.0-r0 | expat: expat: Denial of Service via delayed entity amplification detection — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-113351 | libexpat | 2.8.4-r0 | 2.10.0-r0 | expat: expat: Denial of Service via improper memory tracking in XML_ParserReset — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-78669 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-78667 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang: golang: Denial of Service via crafted HTTP Range headers — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56862 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | crypto/tls: golang: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56860 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | net/url: golang: golang net/url: Denial of Service from quadratic complexity in path resolution — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56859 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | encoding/xml: golang: Go: Denial of Service via XML decoding recursion depth issue — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56858 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | html/template: golang: Go html/template: Cross-Site Scripting via pathological input — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56853 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | net/http: golang: Go net/http: Unencrypted HTTP/2 connections vulnerable to Denial of Service — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-46600 | stdlib | v1.26.4 | 1.26.6, 1.27.0-rc.3 | golang.org/x/net/dns/dnsmessage: golang.org/x/net/dns/dnsmessage: Denial of Service via invalid DNS record parsing — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-39822 | stdlib | v1.26.4 | 1.25.12, 1.26.5, 1.27.0-rc.2 | golang: Go os.Root: Symlink following vulnerability allows directory traversal — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-39821 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-33818 | stdlib | v1.26.4 | 1.25.13, 1.26.6, 1.27.0-rc.3 | encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-111943 | stdlib | v1.26.4 | 1.26.10, 1.27.3 | crypto/x509: golang: crypto/x509: Man-in-the-middle attacks via untrusted intermediate certificates — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56852 | golang.org/x/text | v0.38.0 | 0.39.0 | golang.org/x/text: golang.org/x/text: Denial of Service via invalid UTF-8 input — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-56851 | golang.org/x/text | v0.38.0 | 0.41.0 | golang.org/x/text: golang.org/x/text: Denial of Service via out-of-bounds slice error in Nickname profile — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | CVE-2026-87018 | undici | 7.29.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via TLS renegotiation with mismatched certificate — Node.js |
| HIGH | CVE-2026-109869 | undici | 7.29.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unhandled stream error on excessive content encodings — Node.js |
| HIGH | CVE-2026-109829 | undici | 7.29.1 | 7.30.1, 8.12.2 | undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching — Node.js |
| HIGH | CVE-2026-109383 | undici | 7.29.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Certificate validation bypass via dropped TLS options in Agent — Node.js |
| HIGH | CVE-2026-87018 | undici | 6.28.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via TLS renegotiation with mismatched certificate — Node.js |
| HIGH | CVE-2026-109869 | undici | 6.28.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unhandled stream error on excessive content encodings — Node.js |
| HIGH | CVE-2026-109383 | undici | 6.28.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Certificate validation bypass via dropped TLS options in Agent — Node.js |
| HIGH | CVE-2026-87018 | undici | 6.28.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via TLS renegotiation with mismatched certificate — Node.js |
| HIGH | CVE-2026-19534 | undici | 6.28.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: Denial of Service via unrequested WebSocket subprotocol — Node.js |
| HIGH | CVE-2026-109869 | undici | 6.28.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unhandled stream error on excessive content encodings — Node.js |
| HIGH | CVE-2026-109383 | undici | 6.28.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Certificate validation bypass via dropped TLS options in Agent — Node.js |
| HIGH | CVE-2026-114466 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-92392 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: HTTP/2 upload Use-After-Free — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-105437 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-111760 | git | 2.54.0-r0 | 2.54.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-105437 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-111760 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-92392 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: HTTP/2 upload Use-After-Free — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| HIGH | CVE-2026-114466 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-109924 | undici | 6.28.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via memory exhaustion in EventSource client — Node.js |
| MEDIUM | CVE-2026-101913 | ip-address | 10.5.0 | 10.5.1 | ip-address: ip-address: Security bypass via incomplete IPv6 link-local address validation — Node.js |
| MEDIUM | CVE-2026-101912 | ip-address | 10.5.0 | 10.7.1 | ip-address: ip-address: Access control bypass via cross-family subnet comparison — Node.js |
| MEDIUM | CVE-2026-101911 | ip-address | 10.5.0 | 10.7.1 | ip-address: ip-address: Denial of Service via unbounded IPv6 address parsing — Node.js |
| MEDIUM | CVE-2026-101910 | ip-address | 10.5.0 | 10.5.1 | ip-address: ip-address: Security boundary bypass via unclassified NAT64 local-use address range — Node.js |
| MEDIUM | CVE-2026-69198 | ip-address | 10.2.0 | 10.2.2 | ip-address: ip-address: Server-Side Request Forgery (SSRF) and trust-boundary bypass — Node.js |
| MEDIUM | CVE-2026-54272 | ip-address | 10.2.0 | 10.2.1 | ip-address: ip-address: Server-Side Request Forgery via IPv4-mapped/NAT64 IPv6 address misclassification — Node.js |
| MEDIUM | CVE-2026-111997 | ip-address | 10.2.0 | 10.7.4 | ip-address: ip-address: Denial of Service via excessive percent characters in IPv6 address input — Node.js |
| MEDIUM | CVE-2026-101913 | ip-address | 10.2.0 | 10.5.1 | ip-address: ip-address: Security bypass via incomplete IPv6 link-local address validation — Node.js |
| MEDIUM | CVE-2026-101912 | ip-address | 10.2.0 | 10.7.1 | ip-address: ip-address: Access control bypass via cross-family subnet comparison — Node.js |
| MEDIUM | CVE-2026-101911 | ip-address | 10.2.0 | 10.7.1 | ip-address: ip-address: Denial of Service via unbounded IPv6 address parsing — Node.js |
| MEDIUM | CVE-2026-101910 | ip-address | 10.2.0 | 10.5.1 | ip-address: ip-address: Security boundary bypass via unclassified NAT64 local-use address range — Node.js |
| MEDIUM | CVE-2026-118773 | glob | 13.0.6 | 14.0.2 | glob: glob: Denial of Service (DoS) via incomplete traversal cancellation — Node.js |
| MEDIUM | CVE-2026-118773 | glob | 13.0.6 | 14.0.2 | glob: glob: Denial of Service (DoS) via incomplete traversal cancellation — Node.js |
| MEDIUM | CVE-2026-109932 | undici | 7.29.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unbounded WebSocket PONG buffering — Node.js |
| MEDIUM | CVE-2026-87029 | undici | 7.29.1 | 7.30.1, 8.12.2 | undici: undici: Denial of Service via unhandled exception in decompress interceptor — Node.js |
| MEDIUM | CVE-2026-110306 | fast-uri | 3.1.8 | 2.4.8, 3.1.9, 4.2.3 | fast-uri: fast-uri: Cross-Site Scripting via improper URI scheme decoding — Node.js |
| MEDIUM | CVE-2026-110180 | fast-uri | 3.1.8 | 2.4.8, 3.1.9, 4.2.3 | fast-uri: fast-uri: Security policy bypass via improper host canonicalization — Node.js |
| MEDIUM | CVE-2026-102277 | brace-expansion | 5.0.9 | 5.0.12, 3.0.9, 2.1.7, 1.1.21 | brace-expansion: brace-expansion: Denial of Service via crafted brace patterns — Node.js |
| MEDIUM | CVE-2026-109932 | undici | 6.28.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unbounded WebSocket PONG buffering — Node.js |
| MEDIUM | CVE-2026-85024 | undici | 6.28.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: Denial of Service via unhandled error in WebSocket permessage-deflate decompression — Node.js |
| MEDIUM | CVE-2026-109932 | undici | 6.28.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unbounded WebSocket PONG buffering — Node.js |
| MEDIUM | CVE-2026-109924 | undici | 6.28.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via memory exhaustion in EventSource client — Node.js |
| MEDIUM | CVE-2026-109841 | undici | 7.29.1 | 7.30.1, 8.12.2 | undici: undici: Subresource Integrity bypass via non-lowercase algorithm tokens — Node.js |
| MEDIUM | CVE-2026-109924 | undici | 7.29.1 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via memory exhaustion in EventSource client — Node.js |
| MEDIUM | CVE-2026-85024 | undici | 6.27.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: Denial of Service via unhandled error in WebSocket permessage-deflate decompression — Node.js |
| MEDIUM | CVE-2026-16729 | undici | 6.27.0 | 6.28.0, 7.29.0, 8.9.0 | undici: Undici: Cookie attribute injection allows bypassing security protections — Node.js |
| MEDIUM | CVE-2026-16728 | undici | 6.27.0 | 6.28.0, 7.29.0, 8.9.0 | undici: undici: Response desynchronization via retry interceptor with mismatched Content-Length — Node.js |
| MEDIUM | CVE-2026-15157 | undici | 6.27.0 | 6.28.0, 7.29.0, 8.9.0 | undici: undici: HTTP header injection via unvalidated blob-like body type property — Node.js |
| MEDIUM | CVE-2026-109932 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via unbounded WebSocket PONG buffering — Node.js |
| MEDIUM | CVE-2026-109924 | undici | 6.27.0 | 6.29.1, 7.30.1, 8.12.2 | undici: undici: Denial of Service via memory exhaustion in EventSource client — Node.js |
| MEDIUM | CVE-2026-113408 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-114467 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-114469 | git | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-104844 | postcss-selector-parser | 7.1.4 | 7.1.6, 6.1.5 | postcss-selector-parser: postcss-selector-parser: Denial of Service via crafted CSS selectors — Node.js |
| MEDIUM | CVE-2026-104844 | postcss-selector-parser | 7.1.4 | 7.1.6, 6.1.5 | postcss-selector-parser: postcss-selector-parser: Denial of Service via crafted CSS selectors — Node.js |
| MEDIUM | CVE-2026-118764 | minimatch | 9.0.9 | 11.0.1 | minimatch: minimatch: Denial of Service via crafted glob pattern expansion — Node.js |
| MEDIUM | CVE-2026-118764 | minimatch | 10.2.5 | 11.0.1 | minimatch: minimatch: Denial of Service via crafted glob pattern expansion — Node.js |
| MEDIUM | CVE-2026-118764 | minimatch | 10.2.5 | 11.0.1 | minimatch: minimatch: Denial of Service via crafted glob pattern expansion — Node.js |
| MEDIUM | CVE-2026-111997 | ip-address | 10.5.0 | 10.7.4 | ip-address: ip-address: Denial of Service via excessive percent characters in IPv6 address input — Node.js |
| MEDIUM | CVE-2026-113408 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-58055 | nghttp2-libs | 1.69.0-r0 | 1.70.0-r0 | nghttp2: nghttp2: HTTP Request/Response Smuggling and Response-Queue Poisoning via ambiguous HTTP/1.1 Upgrade requests — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-95692 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-95691 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-107496 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-102633 | libexpat | 2.8.4-r0 | 2.9.0-r0 | expat: expat: Denial of Service via integer overflow in expat_realloc — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-92388 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: FTP wildcard write callback mixup — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-42505 | stdlib | v1.26.4 | 1.25.12, 1.26.5, 1.27.0-rc.2 | crypto/tls: golang: Go crypto/tls: Information disclosure in Encrypted Client Hello — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-56866 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang: golang: Cross-user response poisoning via desynchronized HTTP CONNECT connections — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-78659 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang.org/x/net/http2: golang: net/http: Denial of Service via HTTP/2 trailer header memory exhaustion — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-78660 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang: golang.org/x/net/http2: net/http: HTTP response smuggling via malformed HTTP/2 framing headers — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-78663 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: golang: flow control limit bypass via double refund in HTTP/2 server — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-94439 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: golang: net/http: HTTP request smuggling via improper handling of HTTP/1 CONNECT responses — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-94440 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/textproto: mime/multipart: golang: golang: Denial of Service via memory limit bypass in multipart form parsing — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-94448 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | html/template: golang: golang: cross-site scripting via consecutive expressions in JavaScript template literals — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-97030 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | html/template: golang: html/template: Cross-site scripting via improper escaping of yield keyword — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-97032 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: net/http: Denial of Service via concurrent HPACK encoder modification — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-97054 | stdlib | v1.26.4 | 1.26.11, 1.27.4 | net/http: golang: net/http: Denial of Service via race condition when handling oversized HTTP/1 requests — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| MEDIUM | CVE-2026-102277 | brace-expansion | 5.0.7 | 5.0.12, 3.0.9, 2.1.7, 1.1.21 | brace-expansion: brace-expansion: Denial of Service via crafted brace patterns — Node.js |
| MEDIUM | CVE-2026-114467 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-107496 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-95691 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2025-25289 | @octokit/request-error | 3.0.3 | 5.1.1, 6.1.7 | @octokit/request-error: @octokit/request-error has a Regular Expression in index that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — Node.js |
| MEDIUM | CVE-2025-25289 | @octokit/request-error | 2.1.0 | 5.1.1, 6.1.7 | @octokit/request-error: @octokit/request-error has a Regular Expression in index that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — Node.js |
| MEDIUM | CVE-2025-25290 | @octokit/request | 6.2.8 | 9.2.1, 8.4.1 | octokit/request: @octokit/request has a Regular Expression in fetchWrapper that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — Node.js |
| MEDIUM | CVE-2025-25290 | @octokit/request | 5.6.3 | 9.2.1, 8.4.1 | octokit/request: @octokit/request has a Regular Expression in fetchWrapper that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — Node.js |
| MEDIUM | CVE-2025-25288 | @octokit/plugin-paginate-rest | 6.1.2 | 11.4.1, 9.2.2 | octokit/plugin-paginate-rest: @octokit/plugin-paginate-rest has a Regular Expression in iterator that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — Node.js |
| MEDIUM | CVE-2026-92388 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: FTP wildcard write callback mixup — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2025-25288 | @octokit/plugin-paginate-rest | 2.21.3 | 11.4.1, 9.2.2 | octokit/plugin-paginate-rest: @octokit/plugin-paginate-rest has a Regular Expression in iterator that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — Node.js |
| MEDIUM | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | Improper Restriction of Operations within the Bounds of a Memory Buffe ... — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| MEDIUM | CVE-2026-95692 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-56857 | stdlib | v1.26.4 | 1.26.9, 1.27.2 | os: golang: golang: Directory traversal via Windows junction handling — npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| LOW | CVE-2026-92387 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: never-ending loop via server response omission — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-92386 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie aborts cookie jar load — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87866 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: wolfSSL public-key pinning bypass — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87862 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: HSTS cache import drops longer-lived child — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87861 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: cross-origin reuse of a Negotiate connection — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87864 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: IMAP APPEND plus CRLF conversion command injection — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87865 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: knownhost callback mismatches key as missing — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86415 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: auto client cert connection reuse mixup — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86414 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: leaking host credentials to HTTP proxy — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86413 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: Negotiate credentials sent to redirected origin — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87863 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: Hsts Response Erases Persisted Entries — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86412 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie erases cookie jar — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-107928 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: info leak uploading over WebSockets with GnuTLS — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-107929 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: local interface connection reuse mixup — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86409 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: stale SigV4 headers sent unintended — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86410 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: redirect to SFTP or SCP bypasses host verification — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86411 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: FTP connection reuse inherits client-certificate — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86411 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: FTP connection reuse inherits client-certificate — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86412 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie erases cookie jar — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86413 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: Negotiate credentials sent to redirected origin — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86414 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: leaking host credentials to HTTP proxy — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-94266 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: password leak in CURLINFO_EFFECTIVE_URL — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-94265 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: Authorization: Negotiate sent to foreign origin — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-92391 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: curl_mime_free stack overflow by recursion — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-92390 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: -J no-clobber guarantee bypassed with 103 early hints — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-92389 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: TFTP direction confusion — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-92387 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: never-ending loop via server response omission — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-92386 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: server-set cookie aborts cookie jar load — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87866 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: wolfSSL public-key pinning bypass — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87865 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: knownhost callback mismatches key as missing — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87864 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: IMAP APPEND plus CRLF conversion command injection — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87863 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: Hsts Response Erases Persisted Entries — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87862 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: HSTS cache import drops longer-lived child — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-87861 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: cross-origin reuse of a Negotiate connection — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86415 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: auto client cert connection reuse mixup — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-92389 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: TFTP direction confusion — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-92390 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: -J no-clobber guarantee bypassed with 103 early hints — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-92391 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: curl_mime_free stack overflow by recursion — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-18540 | undici | 6.28.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: HTTP response splitting via retry interceptor — Node.js |
| LOW | CVE-2026-94265 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: Authorization: Negotiate sent to foreign origin — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-94266 | curl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: password leak in CURLINFO_EFFECTIVE_URL — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-18540 | undici | 6.27.0 | 6.28.1, 7.29.1, 8.10.2 | undici: undici: HTTP response splitting via retry interceptor — Node.js |
| LOW | CVE-2026-126066 | fast-xml-parser | 5.11.1 | 5.12.0 | fast-xml-parser: fast-xml-parser: Denial of Service via quadratic rescanning of unterminated tags — Node.js |
| LOW | CVE-2026-110725 | fast-uri | 3.1.8 | 2.4.8, 3.1.9, 4.2.3 | fast-uri: fast-uri: Cross-site scripting via unescaped colon in relative URI paths — Node.js |
| LOW | CVE-2026-110095 | fast-uri | 3.1.8 | 2.4.8, 3.1.9, 4.2.3 | fast-uri: fast-uri: Path traversal via improper relative URI normalization — Node.js |
| LOW | CVE-2026-88822 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-88823 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Message authentication bypass via zero-length AAD update — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-107928 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: info leak uploading over WebSockets with GnuTLS — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-107929 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: local interface connection reuse mixup — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-88823 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: OpenSSL: Message authentication bypass via zero-length AAD update — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-88822 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86409 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: stale SigV4 headers sent unintended — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
| LOW | CVE-2026-86410 | libcurl | 8.22.0-r0 | 8.23.0-r0 | curl: curl: redirect to SFTP or SCP bypasses host verification — ghcr.io/voxpupuli/semantic-release:latest (alpine 3.24.2) |
Grype
CRITICAL 18
HIGH 96
MEDIUM 53
LOW 9
NVD/CPE filtered 68
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-86411 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86411 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87866 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87866 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87861 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86414 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-87861 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86414 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-92388 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-92388 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-4738 | zlib | 1.3.2-r0 | 1.4-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86413 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-86413 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-94265 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | CVE-2026-94265 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| CRITICAL | GO-2026-6612 | stdlib | go1.26.8 | 1.26.9 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. — /usr/bin/git-lfs |
| CRITICAL | GO-2026-6612 | golang.org/x/net | v0.57.0 | 0.60.0 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. — /usr/bin/git-lfs |
| CRITICAL | CVE-2026-111497 | brotli-libs | 1.2.0-r1 | 1.2.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86415 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-117610 | libexpat | 2.8.4-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-4w7w-5xrc-9h26 | undici | 7.29.1 | 7.30.1 | undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects — /npm/node_modules/undici/package.json |
| HIGH | CVE-2026-93990 | libexpat | 2.8.4-r0 | 2.8.5-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-95692 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95692 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | GHSA-6j4f-fj2g-mc7p | brace-expansion | 5.0.9 | 5.0.10 | brace-expansion: DoS via uncontrolled recursion in parseCommaParts causing stack exhaustion — /npm/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GHSA-6j4f-fj2g-mc7p | brace-expansion | 5.0.7 | 5.0.10 | brace-expansion: DoS via uncontrolled recursion in parseCommaParts causing stack exhaustion — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GHSA-mwp4-54f8-5fhr | ip-address | 10.2.0 | 10.3.1 | ip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and trust-boundary bypass — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| HIGH | GO-2026-5970 | golang.org/x/text | v0.38.0 | 0.39.0 | A norm.Iter can enter an infinite loop when handling input containing invalid UTF-8 bytes. — /npm/node_modules/@typescript/typescript-linux-x64/lib/tsc |
| HIGH | GHSA-qhr7-859c-m2p7 | brace-expansion | 5.0.9 | 5.0.11 | brace-expansion: DoS via uncontrolled recursion on nested brace groups causing stack exhaustion — /npm/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GHSA-qhr7-859c-m2p7 | brace-expansion | 5.0.7 | 5.0.11 | brace-expansion: DoS via uncontrolled recursion on nested brace groups causing stack exhaustion — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | CVE-2026-113351 | libexpat | 2.8.4-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-qrxm-fqhp-jwvm | undici | 6.28.0 | 6.29.1 | undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation — /npm/node_modules/npm/node_modules/undici/package.json |
| HIGH | GHSA-qrxm-fqhp-jwvm | undici | 6.27.0 | 6.29.1 | undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | CVE-2026-85091 | zlib | 1.3.2-r0 | 1.3.2-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-115506 | libexpat | 2.8.4-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-103111 | pcre2 | 10.48-r0 | 10.49-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6613 | stdlib | go1.26.8 | 1.26.9, 1.27.2 | When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP. — /usr/bin/git-lfs |
| HIGH | GHSA-r292-9mhp-454m | tar | 7.5.19 | 7.5.21 | node-tar: Uncontrolled recursion in mapHas/filesFilter allows uncatchable stack-overflow DoS via crafted long-path tar with member selection — /usr/local/lib/node_modules/npm/node_modules/tar/package.json |
| HIGH | GO-2026-6610 | stdlib | go1.26.8 | 1.26.9 | Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling. — /usr/bin/git-lfs |
| HIGH | GO-2026-6610 | golang.org/x/net | v0.57.0 | 0.60.0 | Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling. — /usr/bin/git-lfs |
| HIGH | CVE-2026-107891 | musl-utils | 1.2.6-r2 | 1.2.6-r3 | /lib/apk/db/installed |
| HIGH | GHSA-2m5v-pch6-74hx | undici | 7.29.1 | 7.30.1 | undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent — /npm/node_modules/undici/package.json |
| HIGH | GHSA-2m5v-pch6-74hx | undici | 6.28.1 | 6.29.1 | undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent — /npm/node_modules/@actions/http-client/node_modules/undici/package.json |
| HIGH | GHSA-2m5v-pch6-74hx | undici | 6.28.0 | 6.29.1 | undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent — /npm/node_modules/npm/node_modules/undici/package.json |
| HIGH | CVE-2026-107496 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-107496 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | GHSA-xjj6-f33q-929c | undici | 7.29.1 | 7.30.1 | undici vulnerable to Denial of Service via unhandled error on excessive content-encodings — /npm/node_modules/undici/package.json |
| HIGH | GHSA-xjj6-f33q-929c | undici | 6.28.1 | 6.29.1 | undici vulnerable to Denial of Service via unhandled error on excessive content-encodings — /npm/node_modules/@actions/http-client/node_modules/undici/package.json |
| HIGH | GHSA-xjj6-f33q-929c | undici | 6.28.0 | 6.29.1 | undici vulnerable to Denial of Service via unhandled error on excessive content-encodings — /npm/node_modules/npm/node_modules/undici/package.json |
| HIGH | GHSA-xjj6-f33q-929c | undici | 6.27.0 | 6.29.1 | undici vulnerable to Denial of Service via unhandled error on excessive content-encodings — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | CVE-2026-77214 | libexpat | 2.8.4-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | GHSA-2m5v-pch6-74hx | undici | 6.27.0 | 6.29.1 | undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | GHSA-rfgv-xxqx-mfg5 | undici | 6.28.0 | 6.28.1 | undici vulnerable to Denial of Service via unrequested WebSocket subprotocol — /npm/node_modules/npm/node_modules/undici/package.json |
| HIGH | GHSA-rfgv-xxqx-mfg5 | undici | 6.27.0 | 6.28.1 | undici vulnerable to Denial of Service via unrequested WebSocket subprotocol — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| HIGH | CVE-2026-105437 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-105437 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-88823 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95691 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-95691 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-88823 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| HIGH | GHSA-qrxm-fqhp-jwvm | undici | 7.29.1 | 7.30.1 | undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation — /npm/node_modules/undici/package.json |
| HIGH | GHSA-qrxm-fqhp-jwvm | undici | 6.28.1 | 6.29.1 | undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation — /npm/node_modules/@actions/http-client/node_modules/undici/package.json |
| HIGH | CVE-2026-118370 | libexpat | 2.8.4-r0 | 2.10.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-102633 | libexpat | 2.8.4-r0 | 2.9.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86415 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86410 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86410 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6611 | stdlib | go1.26.8 | 1.26.9 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. — /usr/bin/git-lfs |
| HIGH | GO-2026-6611 | golang.org/x/net | v0.57.0 | 0.60.0 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. — /usr/bin/git-lfs |
| HIGH | CVE-2026-92386 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87863 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86412 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92386 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87863 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86412 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87864 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87864 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6603 | stdlib | go1.26.8 | 1.26.9 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. — /usr/bin/git-lfs |
| HIGH | GO-2026-6603 | golang.org/x/net | v0.57.0 | 0.60.0 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. — /usr/bin/git-lfs |
| HIGH | CVE-2026-87862 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87862 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92387 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92387 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86409 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-86409 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92391 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92391 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92392 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92392 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-keygen | 10.3_p1-r1 | 10.3_p1-r2 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-client-default | 10.3_p1-r1 | 10.3_p1-r2 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-client-common | 10.3_p1-r1 | 10.3_p1-r2 | /lib/apk/db/installed |
| HIGH | CVE-2026-107891 | musl | 1.2.6-r2 | 1.2.6-r3 | /lib/apk/db/installed |
| HIGH | CVE-2026-92390 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92390 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87865 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-87865 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6605 | stdlib | go1.26.8 | 1.26.9, 1.27.2 | When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning. — /usr/bin/git-lfs |
| HIGH | GHSA-mh99-v99m-4gvg | brace-expansion | 5.0.7 | 5.0.8 | brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | GHSA-rgw5-rvv9-x895 | brace-expansion | 5.0.7 | 5.0.9 | brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| HIGH | CVE-2026-94266 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6617 | stdlib | go1.26.8 | 1.26.9 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. — /usr/bin/git-lfs |
| HIGH | GO-2026-6617 | golang.org/x/net | v0.57.0 | 0.60.0 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. — /usr/bin/git-lfs |
| HIGH | CVE-2026-107929 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107929 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | GO-2026-6608 | stdlib | go1.26.8 | 1.26.9, 1.27.2 | Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes. — /usr/bin/git-lfs |
| HIGH | GO-2026-6607 | stdlib | go1.26.8 | 1.26.9, 1.27.2 | Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result. — /usr/bin/git-lfs |
| HIGH | CVE-2026-107928 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-107928 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-94266 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92389 | libcurl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-92389 | curl | 8.22.0-r0 | 8.23.0-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-9fm3-97px-rjf6 | undici | 7.29.1 | 7.30.1 | undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering — /npm/node_modules/undici/package.json |
| MEDIUM | CVE-2026-88822 | libcrypto3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-88822 | libssl3 | 3.5.8-r0 | 3.5.9-r1 | /lib/apk/db/installed |
| MEDIUM | GHSA-4qv8-2p9j-2685 | undici | 6.27.0 | 6.29.1 | undici vulnerable to Denial of Service via unbounded memory in the EventSource parser — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-9fm3-97px-rjf6 | undici | 6.27.0 | 6.29.1 | undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-4qv8-2p9j-2685 | undici | 7.29.1 | 7.30.1 | undici vulnerable to Denial of Service via unbounded memory in the EventSource parser — /npm/node_modules/undici/package.json |
| MEDIUM | GHSA-9fm3-97px-rjf6 | undici | 6.28.1 | 6.29.1 | undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering — /npm/node_modules/@actions/http-client/node_modules/undici/package.json |
| MEDIUM | GHSA-4qv8-2p9j-2685 | undici | 6.28.0 | 6.29.1 | undici vulnerable to Denial of Service via unbounded memory in the EventSource parser — /npm/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-9fm3-97px-rjf6 | undici | 6.28.0 | 6.29.1 | undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering — /npm/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-4qv8-2p9j-2685 | undici | 6.28.1 | 6.29.1 | undici vulnerable to Denial of Service via unbounded memory in the EventSource parser — /npm/node_modules/@actions/http-client/node_modules/undici/package.json |
| MEDIUM | CVE-2026-58055 | nghttp2-libs | 1.69.0-r0 | 1.70.0-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-55wc-3pg8-jfw6 | undici | 7.29.1 | 7.30.1 | undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor — /npm/node_modules/undici/package.json |
| MEDIUM | GHSA-8xcm-r25x-g524 | undici | 6.27.0 | 6.28.0 | undici vulnerable to downstream response desynchronization via retry interceptor — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-w74x-v6f9-j3xg | fast-uri | 3.1.8 | 3.1.9 | fast-uri vulnerable to URI scheme spoofing via percent-encoded scheme decoding — /npm/node_modules/fast-uri/package.json |
| MEDIUM | GHSA-f72v-6w45-q472 | undici | 7.29.1 | 7.30.1 | undici vulnerable to Subresource Integrity bypass via non-lowercase algorithm tokens — /npm/node_modules/undici/package.json |
| MEDIUM | GHSA-v3r7-h72x-cjcm | undici | 6.27.0 | 6.28.0 | undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-wjr9-j795-jxcr | fast-uri | 3.1.8 | 3.1.9 | fast-uri vulnerable to host confusion via unchecked WHATWG host canonicalization — /npm/node_modules/fast-uri/package.json |
| MEDIUM | GHSA-m8rv-5g2x-5cg5 | undici | 6.27.0 | 6.28.0 | undici vulnerable to CRLF Injection via blob-like body 'type' property — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | CVE-2026-114469 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| MEDIUM | GHSA-rmvr-2pp2-xj38 | @octokit/request | 5.6.3 | 8.4.1 | @octokit/request has a Regular Expression in fetchWrapper that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — /npm/node_modules/@octokit/rest/node_modules/@octokit/request/package.json |
| MEDIUM | GHSA-rmvr-2pp2-xj38 | @octokit/request | 6.2.8 | 8.4.1 | @octokit/request has a Regular Expression in fetchWrapper that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — /npm/node_modules/semantic-release-github-pullrequest/node_modules/@octokit/request/package.json |
| MEDIUM | GHSA-h5c3-5r3r-rr8q | @octokit/plugin-paginate-rest | 2.21.3 | 9.2.2 | @octokit/plugin-paginate-rest has a Regular Expression in iterator Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — /npm/node_modules/@octokit/rest/node_modules/@octokit/plugin-paginate-rest/package.json |
| MEDIUM | GHSA-h5c3-5r3r-rr8q | @octokit/plugin-paginate-rest | 6.1.2 | 9.2.2 | @octokit/plugin-paginate-rest has a Regular Expression in iterator Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — /npm/node_modules/semantic-release-github-pullrequest/node_modules/@octokit/plugin-paginate-rest/package.json |
| MEDIUM | GHSA-xx4v-prfh-6cgc | @octokit/request-error | 2.1.0 | 5.1.1 | @octokit/request-error has a Regular Expression in index that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — /npm/node_modules/@octokit/rest/node_modules/@octokit/request-error/package.json |
| MEDIUM | GHSA-xx4v-prfh-6cgc | @octokit/request-error | 3.0.3 | 5.1.1 | @octokit/request-error has a Regular Expression in index that Leads to ReDoS Vulnerability Due to Catastrophic Backtracking — /npm/node_modules/semantic-release-github-pullrequest/node_modules/@octokit/request-error/package.json |
| MEDIUM | GHSA-4xrf-jv44-h6hh | ip-address | 10.2.0 | 10.2.2 | ip-address: a CIDR suffix on the parsed address suppresses special-use classification and can bypass SSRF and trust-boundary checks — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-22jq-vg5j-6vgg | ip-address | 10.2.0 | 10.2.1 | ip-address: misclassification of IPv4-mapped/NAT64 IPv6 addresses can bypass SSRF and trust-boundary checks — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GO-2026-6809 | stdlib | go1.26.8 | 1.26.10, 1.27.3 | On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy. — /usr/bin/git-lfs |
| MEDIUM | GHSA-2vr4-cq9g-pvrc | ip-address | 10.2.0 | 10.5.1 | ip-address: no classifier recognizes the NAT64 local-use range 64:ff9b:1::/48, allowing SSRF and trust-boundary bypass — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-2vr4-cq9g-pvrc | ip-address | 10.5.0 | 10.5.1 | ip-address: no classifier recognizes the NAT64 local-use range 64:ff9b:1::/48, allowing SSRF and trust-boundary bypass — /npm/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-3wwx-pv8p-q78v | undici | 6.27.0 | 6.28.1 | undici vulnerable to Denial of Service via unhandled error in WebSocket permessage-deflate decompression — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-3wwx-pv8p-q78v | undici | 6.28.0 | 6.28.1 | undici vulnerable to Denial of Service via unhandled error in WebSocket permessage-deflate decompression — /npm/node_modules/npm/node_modules/undici/package.json |
| MEDIUM | GHSA-q2hr-2g5m-vwhr | brace-expansion | 5.0.7 | 5.0.12 | brace-expansion: Quadratic-time expansion of the `{a},b}` rewrite causes CPU denial of service — /usr/local/lib/node_modules/npm/node_modules/brace-expansion/package.json |
| MEDIUM | GHSA-q2hr-2g5m-vwhr | brace-expansion | 5.0.9 | 5.0.12 | brace-expansion: Quadratic-time expansion of the `{a},b}` rewrite causes CPU denial of service — /npm/node_modules/npm/node_modules/brace-expansion/package.json |
| MEDIUM | GHSA-rpw4-54j3-4h4q | ip-address | 10.2.0 | 10.5.1 | ip-address: Address6.isLinkLocal() recognizes fe80::/64 rather than fe80::/10, allowing SSRF and trust-boundary bypass to on-link hosts — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-rxp7-6hxx-x8q5 | ip-address | 10.5.0 | 10.7.4 | ip-address: Address6 matches a zone identifier in quadratic time ahead of its length limit, allowing a single long string to stall the process — /npm/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-rxp7-6hxx-x8q5 | ip-address | 10.2.0 | 10.7.4 | ip-address: Address6 matches a zone identifier in quadratic time ahead of its length limit, allowing a single long string to stall the process — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-g3hv-75wg-m249 | minimatch | 9.0.9 | 11.0.1 | minimatch has potential denial of service via globparts amplification — /npm/node_modules/@typescript-eslint/typescript-estree/node_modules/minimatch/package.json |
| MEDIUM | GHSA-g3hv-75wg-m249 | minimatch | 10.2.5 | 11.0.1 | minimatch has potential denial of service via globparts amplification — /usr/local/lib/node_modules/npm/node_modules/minimatch/package.json |
| MEDIUM | GHSA-g3hv-75wg-m249 | minimatch | 10.2.5 | 11.0.1 | minimatch has potential denial of service via globparts amplification — /npm/node_modules/npm/node_modules/minimatch/package.json |
| MEDIUM | GHSA-3g3m-2fjr-6pw4 | glob | 13.0.6 | 14.0.2 | Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal — /usr/local/lib/node_modules/npm/node_modules/glob/package.json |
| MEDIUM | GHSA-3g3m-2fjr-6pw4 | glob | 13.0.6 | 14.0.2 | Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal — /npm/node_modules/npm/node_modules/glob/package.json |
| MEDIUM | GO-2026-6859 | stdlib | go1.26.8 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/bin/git-lfs |
| MEDIUM | GHSA-j6r3-76f7-8jcv | ip-address | 10.5.0 | 10.7.1 | ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit an address outside its range — /npm/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-j6r3-76f7-8jcv | ip-address | 10.2.0 | 10.7.1 | ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit an address outside its range — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-rj75-hqrm-r3gf | postcss-selector-parser | 7.1.4 | 7.1.6 | PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion — /usr/local/lib/node_modules/npm/node_modules/postcss-selector-parser/package.json |
| MEDIUM | GHSA-rj75-hqrm-r3gf | postcss-selector-parser | 7.1.4 | 7.1.6 | PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion — /npm/node_modules/npm/node_modules/postcss-selector-parser/package.json |
| MEDIUM | GHSA-h3mg-xc3c-68pw | ip-address | 10.5.0 | 10.7.1 | ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process — /npm/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-h3mg-xc3c-68pw | ip-address | 10.2.0 | 10.7.1 | ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process — /usr/local/lib/node_modules/npm/node_modules/ip-address/package.json |
| MEDIUM | GHSA-rpw4-54j3-4h4q | ip-address | 10.5.0 | 10.5.1 | ip-address: Address6.isLinkLocal() recognizes fe80::/64 rather than fe80::/10, allowing SSRF and trust-boundary bypass to on-link hosts — /npm/node_modules/npm/node_modules/ip-address/package.json |
| LOW | GHSA-474x-hrwr-fgx4 | fast-xml-parser | 5.11.1 | 5.12.0 | fast-xml-parser: Quadratic CPU consumption scanning unterminated stop-node tags — /npm/node_modules/fast-xml-parser/package.json |
| LOW | GHSA-r53p-7pc4-xj5r | undici | 6.27.0 | 6.28.1 | undici vulnerable to downstream response splitting via retry interceptor — /usr/local/lib/node_modules/npm/node_modules/undici/package.json |
| LOW | GHSA-r53p-7pc4-xj5r | undici | 6.28.0 | 6.28.1 | undici vulnerable to downstream response splitting via retry interceptor — /npm/node_modules/npm/node_modules/undici/package.json |
| LOW | GHSA-333x-w4r6-6crp | fast-uri | 3.1.8 | 3.1.9 | fast-uri vulnerable to scheme injection via an unescaped first-segment colon in suffix references — /npm/node_modules/fast-uri/package.json |
| LOW | GHSA-xhq7-xmqj-769h | fast-uri | 3.1.8 | 3.1.9 | fast-uri vulnerable to improper path equivalence in relative reference normalization — /npm/node_modules/fast-uri/package.json |
| LOW | CVE-2026-113408 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-113408 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git-init-template | 2.54.0-r0 | 2.54.1-r0 | /lib/apk/db/installed |
Filtered NVD/CPE matches (68)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-111497 | node | 24.21.0 | 11.0.0, 22.23.4, 24.22.1, 26.12.1 | A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1.2.1. — /usr/local/bin/node |
| HIGH | CVE-2026-107493 | libssl3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.8-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.8-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.8-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-106069 | node | 24.21.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`. `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| HIGH | CVE-2026-105483 | node | 24.21.0 | 24.22.1, 26.12.1 | A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`). `tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618. This vulnerability affects Node.js **26.x** and **24.x**. — /usr/local/bin/node |
| HIGH | CVE-2026-123864 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the request body. Triggering it requires a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and reading the leaked memory requires any ordinary route that echoes or stores a request body. Cleartext node:http is not affected. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-72897 | libssl3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-72897 | libcrypto3 | 3.5.8-r0 | Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-123872 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only client-cert auth on one host and ordinary client-cert auth on another, a client that authenticates for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to the protected host, bypassing the stricter policy. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-105482 | node | 24.21.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). This is an incomplete fix of CVE-2026-48930, which only covered dns.lookup() and the net/tls host options. Because the name is passed to c-ares as a C string, resolving attacker.example\0.trusted.example queries attacker.example and returns its records without any error. Applications that validate a hostname, for example against a domain allowlist, and then resolve it with dns.resolve*() can act on records for a different name than the one they validated. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-54873 | libcrypto3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-54873 | libssl3 | 3.5.8-r0 | Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-123863 | node | 24.21.0 | 24.22.3, 26.13.1 | A reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. A client can arrange for an Http2Stream that still holds nghttp2-allocated header buffers to outlive its session: the stream is removed from the session's stream set but never detached, so when ~Http2Session() runs the memory accounting is nonzero and the CHECK_EQ(current_nghttp2_memory_, 0) assertion fails, terminating the process. The trigger needs only a default http2 server whose handler responds before the request body has ended, which is typical. It is a variant of CVE-2024-27983 that the earlier fix did not cover, because that fix only detached streams still tracked in the session. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0). — /usr/local/bin/node |
| HIGH | CVE-2026-123874 | node | 24.21.0 | 24.22.3, 26.13.1 | A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respondWithFile() or respondWithFD(). A client can make the server free an Http2Stream while a write request that points to it is still queued on the socket; when that write completes, the code dereferences and makes a virtual call through the freed object. The only precondition is that the application serves a file with stream.respondWithFile() or stream.respondWithFD(), with default settings otherwise. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0). — /usr/local/bin/node |
| HIGH | CVE-2026-123866 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer `RST_STREAM` or by the server's own per-stream timeout destroying the stream, the stream's response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.8-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libcrypto3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84784 | libssl3 | 3.5.8-r0 | Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-123865 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js's HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| HIGH | CVE-2026-84782 | libcrypto3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84782 | libssl3 | 3.5.8-r0 | Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-126051 | node | 24.21.0 | 24.22.3, 26.13.1 | A deferred-callback use-after-destroy in Node.js TLS server handshake handling allows a remote, unauthenticated attacker to terminate the server process. When a TLS server uses any of the SNICallback, OCSPRequest, newSession, or resumeSession hooks, or server.addContext(), the corresponding OpenSSL callbacks are deferred, and the deferred code does not handle the underlying socket being destroyed between scheduling and execution. By sending a client hello that reaches the vulnerable path (for example, no SNI together with an OCSP request) followed by padding and a socket FIN, an attacker makes OpenSSL deliver the client hello and the end-of-file in the same tick, so the socket is destroyed before the deferred callback runs and the process raises an uncaught exception instead of emitting an 'error' event. This vulnerability affects Node.js 26.x and 24.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-123877 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-106074 | node | 24.21.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt()` to be saved into user-land startup snapshots (`--build-snapshot`) and single executable applications built with `useSnapshot`. If any of these functions, or an API that relies on them such as `URL.createObjectURL()`, is called while the snapshot is built, every process started from that snapshot returns the same values until the cache is refilled: up to 127 UUIDs and about 1,000 `randomInt()` values. Identifiers expected to be unique can collide across processes, and values issued by one process can be predicted by observing another. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r31 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-123828 | node | 24.21.0 | 24.22.3, 26.13.1 | A one-byte heap buffer overflow in Node.js HTTP/2 Alt-Svc handling lets a remote, unauthenticated attacker corrupt process memory. When an application passes an attacker-controlled value such as a request's :authority header to Http2Session.altsvc(), the AltSvc implementation in src/node_http2.cc allocates a buffer sized to the origin length and then writes it with a null terminator, placing one byte past the end of the allocation. A single request carrying a long but syntactically valid :authority triggers the out-of-bounds write, which aborts the process and serves as a remote heap-corruption primitive. This vulnerability affects Node.js 26.x and 24.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-75806 | libcrypto3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.8-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-123871 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | Node.js discloses proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. CVE-2026-48615 established that a proxy credential must not appear in a Node.js error message and redacted the username and password from ProxyConfig.href, but that fix missed four error paths in the same subsystem, one of them inside the same constructor, which interpolate the raw proxy URL, credentials included, into an ERR_PROXY_INVALID_CONFIG message. The proxy URL comes from the environment, but the defect is the sink: a secret that Node.js redacts everywhere else is emitted verbatim into a much wider audience than the process environment, such as stderr, container logs, log aggregation, and crash reporting services. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-123867 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })` but no server certificate in that SNI context, the per-host client CA is never installed and the handshake falls back to the default client CA. In `src/crypto/crypto_tls.cc`, `CertCbDone` installs the SNI context's CA only when `setSniContext` succeeds, but `setSniContext` returns `false` for a context with no server certificate, so a CA-only SNI context silently keeps the default CA. A client holding a certificate trusted by the default CA, but not the protected CA, can therefore complete mTLS to the protected hostname and read its response even with `requestCert` and `rejectUnauthorized` enabled, while a client certified by the protected CA is rejected. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-100407 | git | 2.54.0-r0 | Git for Windows is the Windows port of Git. From 2.44.0.windows.1 until 2.55.0.windows.3, the git-credential-wincred store operation in contrib/credential/wincred/git-credential-wincred.c uses _scwprintf() to size a formatted wide-character credential buffer without space for the terminating NUL when both password and oauth_refresh_token are present. The operation also passes a byte count to _snwprintf_s() where a wide-character count is required, allowing the terminator to be written one WCHAR past the heap allocation before CredWriteW() persists the credential. The resulting fixed two-byte NUL overwrite can terminate the helper with Windows heap-corruption status and can cause git credential approve to report success even though the OAuth credential was not stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100408 | git | 2.54.0-r0 | Git for Windows is the Windows port of Git. From 2.43.0.windows.1 until 2.55.0.windows.3, when a matching git:* credential exists in Windows Credential Manager and a git-credential-wincred erase input includes a password field, the operation in contrib/credential/wincred/git-credential-wincred.c allocates a buffer of exactly CredentialBlobSize bytes in match_cred_password() and then uses wcsncpy_s() to copy the corresponding number of wide characters plus a terminating NUL. The destination capacity is also supplied in bytes instead of WCHAR elements, allowing a fixed two-byte NUL write past the allocation before the password comparison determines whether CredDeleteW() should remove the credential; erase without a password field does not enter this comparison path. The helper can terminate with Windows heap-corruption status, and git credential reject can appear successful while the rejected credential remains stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-106072 | node | 24.21.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`. `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| MEDIUM | CVE-2026-75804 | libcrypto3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75804 | libssl3 | 3.5.8-r0 | Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-123868 | node | 24.21.0 | 24.22.3, 26.13.1 | An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-42772 | libcrypto3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-42772 | libssl3 | 3.5.8-r0 | Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-123875 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | A NULL pointer dereference in Node.js HTTP/2 lets an unauthenticated client crash the server, over both TLS and cleartext, by cancelling file downloads. When the server serves a file with stream.respondWithFile() or stream.respondWithFD() and the client cancels the request, a StreamPipe used for the transfer is torn down in an order that leaves a NULL pointer which is then dereferenced, aborting the process. No crafted frames are needed, and a handful of cancelled requests against a default file-serving handler is enough. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| MEDIUM | CVE-2026-75806 | libssl3 | 3.5.8-r0 | Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-75805 | libcrypto3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.8-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libssl3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35189 | libcrypto3 | 3.5.8-r0 | Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-105481 | node | 24.21.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. This is an incomplete fix of CVE-2026-48931. The guard that destroys idle keep-alive sockets when unexpected data arrives only runs when the event loop polls for I/O. If an unsolicited response has already reached the socket but has not been read yet when the socket is handed to a new request, for example because the event loop was busy with synchronous work, the guard is removed without seeing it and the data is parsed as the response to the new request. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| MEDIUM | CVE-2026-75805 | libssl3 | 3.5.8-r0 | Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| LOW | CVE-2026-123829 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | A Permission Model bypass in Node.js recursive file watching discloses the names of files and directories the process is not permitted to read. On macOS and Windows, fs.watch() and fs.promises.watch() in recursive mode are backed by the native libuv watcher: FSEventWrap::Start checks kFileSystemRead only once, on the watched root, and FSEventWrap::OnEvent then forwards every filename libuv reports (relative paths at any depth) to the JavaScript callback without checking that each path is covered by the read grant. Code running under --permission with an exact read grant on a directory can therefore learn names such as sub/secret.txt even though readdir on that subdirectory is denied. The flaw exposes names and timing metadata, not file contents, and requires macOS or Windows plus files created under the watched directory by another actor. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| LOW | CVE-2026-123862 | node | 24.21.0 | 22.23.5, 24.22.3, 26.13.1 | An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write's callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream's error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. This vulnerability affects Node.js 26.x, 24.x, and 22.x. — /usr/local/bin/node |
| LOW | CVE-2026-106073 | node | 24.21.0 | 22.23.4, 24.22.1, 26.12.1 | A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks. This is an incomplete fix of CVE-2026-21715, which only covered `fs.realpathSync.native()`. As a result, code running under `--permission` with restricted `--allow-fs-read` can still use `fs.realpathSync()` to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. — /usr/local/bin/node |
| LOW | CVE-2026-54875 | libcrypto3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-54875 | libssl3 | 3.5.8-r0 | Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libcrypto3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-35191 | libssl3 | 3.5.8-r0 | Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libcrypto3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-54872 | libssl3 | 3.5.8-r0 | Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libssl3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed | |
| LOW | CVE-2026-77696 | libcrypto3 | 3.5.8-r0 | Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm. — /lib/apk/db/installed |
ghcr.io/voxpupuli/voxbox
Downloads
ghcr.io/voxpupuli/voxbox:latest (2026-11-04)
Trivy
CRITICAL 3
HIGH 10
MEDIUM 16
UNKNOWN 4
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | CVE-2026-123158 | openssh-keygen | 10.2_p1-r0 | 10.2_p1-r1 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-123158 | openssh-client-default | 10.2_p1-r0 | 10.2_p1-r1 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| CRITICAL | CVE-2026-123158 | openssh-client-common | 10.2_p1-r0 | 10.2_p1-r1 | openssh: OpenSSH: Password authentication bypass via password hash misinterpretation — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| HIGH | CVE-2026-78669 | golang.org/x/net | v0.57.0 | 0.60.0 | net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames — usr/local/bin/jig |
| HIGH | CVE-2026-78661 | golang.org/x/net | v0.57.0 | 0.62.0 | golang.org/x/net/html: golang.org/x/net/html: Denial of Service via crafted HTML input — usr/local/bin/jig |
| HIGH | CVE-2026-80212 | resolv | 0.2.3 | ~> 0.3.2, >= 0.7.2 | resolv: resolv gem: Denial of Service via uncontrolled memory growth from crafted DNS responses — Ruby |
| HIGH | GHSA-hjwv-j52r-xcg7 | net-ssh | 7.3.8 | ~> 7.3.9, >= 8.1.1 | net-ssh - @revoked known_hosts entries are treated as valid pinned host keys — revoked host key accepted — Ruby |
| HIGH | CVE-2026-114466 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| HIGH | CVE-2026-111760 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| HIGH | CVE-2026-105437 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| HIGH | CVE-2026-105437 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Heap corruption via integer overflow in merge size calculations — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| HIGH | CVE-2026-111760 | git | 2.52.0-r0 | 2.52.1-r0 | git: Git: Arbitrary code execution via unsafe submodule metadata during recursive clones — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| HIGH | CVE-2026-114466 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Arbitrary file system access via fast-import features — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-97054 | stdlib | v1.27.3 | 1.26.11, 1.27.4 | net/http: golang: net/http: Denial of Service via race condition when handling oversized HTTP/1 requests — usr/local/bin/jig |
| MEDIUM | CVE-2026-97045 | golang.org/x/net | v0.57.0 | 0.62.0 | golang.org/x/net/html: golang.org/x/net/html: Cross-Site Scripting via improper namespace handling during HTML rendering — usr/local/bin/jig |
| MEDIUM | CVE-2026-97032 | golang.org/x/net | v0.57.0 | 0.60.0 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: net/http: Denial of Service via concurrent HPACK encoder modification — usr/local/bin/jig |
| MEDIUM | CVE-2026-78663 | golang.org/x/net | v0.57.0 | 0.60.0 | net/http: net/http/internal/http2: golang: golang.org/x/net/http2: golang: flow control limit bypass via double refund in HTTP/2 server — usr/local/bin/jig |
| MEDIUM | CVE-2026-78660 | golang.org/x/net | v0.57.0 | 0.60.0 | net/http: golang: golang.org/x/net/http2: net/http: HTTP response smuggling via malformed HTTP/2 framing headers — usr/local/bin/jig |
| MEDIUM | CVE-2026-78659 | golang.org/x/net | v0.57.0 | 0.60.0 | net/http: golang.org/x/net/http2: golang: net/http: Denial of Service via HTTP/2 trailer header memory exhaustion — usr/local/bin/jig |
| MEDIUM | CVE-2026-80213 | resolv | 0.2.3 | ~> 0.3.2, >= 0.7.2 | resolv: Resolv gem: DNS allowlist and egress bypass, and cache poisoning via crafted hostnames — Ruby |
| MEDIUM | GHSA-qcf4-j55x-72hv | net-ssh | 7.3.8 | ~> 7.3.10, >= 8.1.2 | Net::SSH::Proxy::HTTPS disables TLS certificate verification by default (CWE-295) — Ruby |
| MEDIUM | CVE-2026-113408 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| MEDIUM | GHSA-r6vf-943r-2wvw | minitar | 1.1.0 | ~> 1.1.1, >= 1.2.0 | minitar path traversal vulnerability on Windows with a maliciously crafted tarball — Ruby |
| MEDIUM | CVE-2026-4738 | zlib | 1.3.2-r1 | 1.4-r0 | Improper Restriction of Operations within the Bounds of a Memory Buffe ... — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114467 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114469 | git | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of Service via binary patch size validation bypass — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-114467 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Denial of service via commit messages with multiple GPG signatures — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| MEDIUM | CVE-2026-113408 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | git: git: Unintended file writes via malformed unborn HEAD advertisement — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| UNKNOWN | GO-2026-5932 | golang.org/x/crypto | v0.56.0 | 0.58.1-0.20261009181718-2f1f834330b2 | The golang.org/x/crypto/openpgp package is unmaintained, unsafe by design, and has known security issues — usr/local/bin/jig |
| UNKNOWN | CVE-2026-127231 | gnutls | 3.8.13-r0 | 3.8.14-r0 | A double free in the X.509 name constraints enforcement of GnuTLS 3.8. ... — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| UNKNOWN | CVE-2026-127040 | gnutls | 3.8.13-r0 | 3.8.14-r0 | The RSA-PSK ClientKeyExchange handler in gnutls before 3.8.14 does not ... — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
| UNKNOWN | CVE-2026-127039 | gnutls | 3.8.13-r0 | 3.8.14-r0 | The certificate authentication info handling in gnutls from 2.5.9 up t ... — ghcr.io/voxpupuli/voxbox:latest (alpine 3.23.4) |
Grype
CRITICAL 7
HIGH 10
MEDIUM 9
LOW 4
NVD/CPE filtered 59
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| CRITICAL | GHSA-34m4-m9fh-gqp5 | ruby | 3.2.11 | 3.3.14 | Heap buffer overflow in case conversion of strings — /usr/local/bin/ruby |
| CRITICAL | GHSA-3p8q-wmhx-vm2w | ruby | 3.2.11 | 3.3.14 | Heap buffer overflow in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-7x2q-68qv-6p8x | ruby | 3.2.11 | 3.3.14 | Double free in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-qm4g-8pfh-6996 | ruby | 3.2.11 | 3.3.13 | Overflow of internal identifiers in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-22mf-ggw7-pxfx | ruby | 3.2.11 | 3.3.13 | Integer overflow in regular expression compilation — /usr/local/bin/ruby |
| CRITICAL | GHSA-gfj3-8wj9-qx8p | ruby | 3.2.11 | 3.3.13 | Double free in regular expression parsing — /usr/local/bin/ruby |
| CRITICAL | CVE-2026-4738 | zlib | 1.3.2-r1 | 1.4-r0 | /lib/apk/db/installed |
| HIGH | GHSA-7whj-cfh7-xgm4 | ruby | 3.2.11 | 3.3.14 | Heap buffer overflow in Regexp#to_s — /usr/local/bin/ruby |
| HIGH | GHSA-87fm-7w84-j2px | ruby | 3.2.11 | 3.3.14 | Integer overflow in case conversion of strings — /usr/local/bin/ruby |
| HIGH | GHSA-wpqw-5qxg-m68r | ruby | 3.2.11 | 3.3.14 | Out-of-bounds read in case-insensitive regular expression matching — /usr/local/bin/ruby |
| HIGH | CVE-2026-105437 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-105437 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-111760 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-keygen | 10.2_p1-r0 | 10.2_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-client-default | 10.2_p1-r0 | 10.2_p1-r1 | /lib/apk/db/installed |
| HIGH | CVE-2026-123158 | openssh-client-common | 10.2_p1-r0 | 10.2_p1-r1 | /lib/apk/db/installed |
| MEDIUM | GHSA-pvgc-g7gj-pv6h | ruby | 3.2.11 | 3.3.14 | Out-of-bounds read in case-insensitive backreference matching — /usr/local/bin/ruby |
| MEDIUM | CVE-2026-114466 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114466 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114469 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-114469 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-127231 | gnutls | 3.8.13-r0 | 3.8.14-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-127039 | gnutls | 3.8.13-r0 | 3.8.14-r0 | /lib/apk/db/installed |
| MEDIUM | CVE-2026-127040 | gnutls | 3.8.13-r0 | 3.8.14-r0 | /lib/apk/db/installed |
| MEDIUM | GO-2026-6859 | stdlib | go1.27.3 | 1.26.11, 1.27.4 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header. — /usr/local/bin/jig |
| LOW | CVE-2026-113408 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-113408 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
| LOW | CVE-2026-114467 | git-init-template | 2.52.0-r0 | 2.52.1-r0 | /lib/apk/db/installed |
Filtered NVD/CPE matches (59)
These broad CPE matches are unconfirmed for the distribution package and excluded from scanner totals.
| Severity | ID | Package | Installed | Fixed | Title / target |
|---|---|---|---|---|---|
| HIGH | CVE-2026-119373 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5MergeRowidLists() that undersizes the output buffer when merging detail=none prefix doclists. Attackers who can populate a detail=none FTS5 table with negative rowids and run a prefix MATCH query can write past the allocation, corrupting heap memory and crashing the process. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libssl3 | 3.5.9-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-84786 | libcrypto3 | 3.5.9-r0 | Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libcrypto3 | 3.5.9-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107493 | libssl3 | 3.5.9-r0 | Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-132825 | ruby | 3.2.11 | 3.3.14, 3.4.13, 4.0.10 | Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252. — /usr/local/bin/ruby |
| HIGH | CVE-2026-119374 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5DoSecureDelete() that allows attackers to write past the leaf page buffer via crafted footer key offsets. Attackers can supply a database file with a corrupted FTS5 index that, when deleted from with secure-delete enabled, corrupts heap memory and crashes the application. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libssl3 | 3.5.9-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-121482 | libcrypto3 | 3.5.9-r0 | Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. — /lib/apk/db/installed | |
| HIGH | CVE-2026-88823 | libssl3 | 3.5.9-r0 | Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-88823 | libcrypto3 | 3.5.9-r0 | Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libssl3 | 3.5.9-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107494 | libcrypto3 | 3.5.9-r0 | Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119379 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with the session extension contains a heap buffer overflow vulnerability in sqlite3changeset_apply() that allows attackers to corrupt heap memory by supplying crafted changesets. Attackers can repeat a table name in a second changeset block with a larger column count, causing sessionUpdateFind() to memset past the undersized aUpdateMask allocation. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95691 | libssl3 | 3.5.9-r0 | Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95691 | libcrypto3 | 3.5.9-r0 | Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-119586 | sqlite-libs | 3.53.4-r0 | SQLite command-line shell through 3.54.1 contains a command injection vulnerability in the .recover command that emits attacker-planted dot-commands stored in sqlite_schema.sql values verbatim. Attackers can craft a database whose schema holds a valid CREATE statement followed by a .shell or .system line, executing OS commands when victims pipe .recover output into sqlite3. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107496 | libssl3 | 3.5.9-r0 | Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely. Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service. CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns. The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option. The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected. The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely. FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libcrypto3 | 3.5.9-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-107496 | libcrypto3 | 3.5.9-r0 | Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely. Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service. CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns. The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option. The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected. The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely. FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached. — /lib/apk/db/installed | |
| HIGH | CVE-2026-124709 | libssl3 | 3.5.9-r0 | Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95692 | libcrypto3 | 3.5.9-r0 | Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected. Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV. CWE: CWE-125: Out-of-bounds Read Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length. The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery. Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application. FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm. — /lib/apk/db/installed | |
| HIGH | CVE-2026-95692 | libssl3 | 3.5.9-r0 | Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected. Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV. CWE: CWE-125: Out-of-bounds Read Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length. The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery. Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application. FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libcrypto3 | 3.5.9-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100408 | git | 2.52.0-r0 | Git for Windows is the Windows port of Git. From 2.43.0.windows.1 until 2.55.0.windows.3, when a matching git:* credential exists in Windows Credential Manager and a git-credential-wincred erase input includes a password field, the operation in contrib/credential/wincred/git-credential-wincred.c allocates a buffer of exactly CredentialBlobSize bytes in match_cred_password() and then uses wcsncpy_s() to copy the corresponding number of wide characters plus a terminating NUL. The destination capacity is also supplied in bytes instead of WCHAR elements, allowing a fixed two-byte NUL write past the allocation before the password comparison determines whether CredDeleteW() should remove the credential; erase without a password field does not enter this comparison path. The helper can terminate with Windows heap-corruption status, and git credential reject can appear successful while the rejected credential remains stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119371 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH nesting limit because common table expressions are not counted against it. Attackers can supply a WITH clause chaining tens of thousands of CTEs, via plain SQL or a view in an untrusted database file, causing unbounded selectExpander() recursion that crashes the process. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-115559 | python3 | 3.12.16-r0 | IMAP4.starttls() wraps the socket in TLS but leaves self._readbuf, imaplib's own read-ahead buffer, untouched. Any plaintext bytes that arrived in the same recv() as the tagged OK to STARTTLS are returned by readline() after the handshake, so the client treats them as the first responses on the protected channel. A network attacker who cannot break TLS can append forged lines after the server's OK, let the handshake complete with the real server and a valid certificate, and have the client accept the forged CAPABILITY and the forged tagged completion of the next command. This is the STARTTLS command/response injection class of CVE-2011-0411. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libcrypto3 | 3.5.9-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-35190 | libssl3 | 3.5.9-r0 | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119376 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH limit by chaining COLLATE postfix operators. Attackers can supply roughly 175,000 chained COLLATE operators in SQL or an untrusted database view to trigger unbounded recursion in sqlite3WalkExprNN() and crash the process. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-6019 | python3 | 3.12.16-r0 | http.cookies.Morsel.js_output() returns an inline <script> snippet and only escapes " for JavaScript string context. It does not neutralize the HTML parser-sensitive sequence </script> inside the generated script element. Mitigation base64-encodes the cookie value to disallow escaping using cookie value. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-3446 | python3 | 3.12.16-r0 | When calling base64.b64decode() or related functions the decoding process would stop after encountering the first padded quad regardless of whether there was more information to be processed. This can lead to data being accepted which may be processed differently by other implementations. Use "validate=True" to enable stricter processing of base64 data. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119591 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a stack exhaustion vulnerability in countOfViewOptimization() that allows attackers to crash the host process via count(*) over a large multi-row VALUES clause. Attackers supplying SQL or a database file with a crafted view can trigger deeply nested TK_PLUS expressions whose recursive freeing in sqlite3ExprDeleteNN() exhausts the C stack, causing denial of service. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-115791 | python3 | 3.12.16-r0 | When tarfile or zipfile command line interface (CLI) is used to decompress an archive, a Python script shadowing the stdlib can be created. Then if an error occurs during decompressing the next file, the newly created Python script is executed. This is especially true if the created Python is called traceback.py. The problem is that Python adds the current directory to sys.path when python -m MODULE is run, and the archive is also decompressed in the current directory. The fix removes sys.path[0] in gzip, tarfile and zipfile command line interface to prevent shadowing standard library modules from extracted files. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-100407 | git | 2.52.0-r0 | Git for Windows is the Windows port of Git. From 2.44.0.windows.1 until 2.55.0.windows.3, the git-credential-wincred store operation in contrib/credential/wincred/git-credential-wincred.c uses _scwprintf() to size a formatted wide-character credential buffer without space for the terminating NUL when both password and oauth_refresh_token are present. The operation also passes a byte count to _snwprintf_s() where a wide-character count is required, allowing the terminator to be written one WCHAR past the heap allocation before CredWriteW() persists the credential. The resulting fixed two-byte NUL overwrite can terminate the helper with Windows heap-corruption status and can cause git credential approve to report success even though the OAuth credential was not stored. This issue is fixed in version 2.55.0.windows.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119372 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 built with FTS3/FTS4 and SQLITE_ENABLE_FTS3_PARENTHESIS contains a use-after-free vulnerability in fts3BestSnippet() caused by dangling cached position-list pointers. Attackers can run a full-text MATCH query combining OR and NEAR operators with snippet() to read freed heap memory and crash the process. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-15367 | python3 | 3.12.16-r0 | The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-15366 | python3 | 3.12.16-r0 | The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-12781 | python3 | 3.12.16-r0 | When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues. This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet. The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprecates the behavior which will be replaced with the newly recommended behavior in a future version of Python. Users are recommended to mitigate by verifying user-controlled inputs match the base64 alphabet they are expecting or verify that their application would not be affected if the b64decode() functions accepted "+" or "/" outside of altchars. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-95690 | libssl3 | 3.5.9-r0 | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | busybox-binsh | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2025-60876 | ssl_client | 1.37.0-r30 | BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20). — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-124249 | python3 | 3.12.16-r0 | http.cookiejar.CookieJar deleted a stored cookie when a response carried an already expired Set-Cookie header for it, using the Domain and Path attributes from the header without consulting the cookie policy. A server could therefore delete cookies belonging to other domains from a shared cookie jar, such as the one used by urllib's HTTPCookieProcessor. The fix consults the cookie policy before an expired cookie may delete an existing one, as required by RFC 6265 section 5.3. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-88822 | libcrypto3 | 3.5.9-r0 | Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-88822 | libssl3 | 3.5.9-r0 | Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets. Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic. CWE: CWE-457 (Use of Uninitialized Variable) Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119378 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains a use-after-free vulnerability in the R-Tree extension that allows attackers to make applications use freed heap memory by manipulating the %_node shadow table. Attackers can supply a database declaring %_node WITHOUT ROWID or with a RAISE(IGNORE) trigger so nodeWrite() hashes nodes as 0, crashing the process after node splits. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-58055 | nghttp2-libs | 1.69.0-r0 | nghttp2's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also carries a Content-Length header and body onto reusable keep-alive backend connections, re-adding the Upgrade and Connection headers while passing Content-Length verbatim. A backend that resolves the resulting ambiguous message in the attacker's favor enables HTTP request/response smuggling and cross-client response-queue poisoning. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-116566 | python3 | 3.12.16-r0 | socket.getaddrinfo() previously accepted null bytes within *host* and *port* parameters which can cause the values to be silently truncated. — /lib/apk/db/installed | |
| MEDIUM | CVE-2026-119375 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains an information disclosure vulnerability that allows attackers to read uninitialized page-cache memory by supplying a WAL file with an undersized page size. Attackers can craft a database and WAL file whose oversized record payload makes queries like substr() return stale bytes, disclosing other table rows and internal pointers. — /lib/apk/db/installed | |
| LOW | CVE-2026-119377 | sqlite-libs | 3.53.4-r0 | SQLite before 3.54.0 contains an authorization bypass vulnerability in lookupName() that invokes the authorizer only for the first joined table's USING column. Attackers able to submit SQL can query a shared USING column in a RIGHT or FULL JOIN to read columns denied via sqlite3_set_authorizer() SQLITE_READ restrictions. — /lib/apk/db/installed | |
| LOW | CVE-2026-16052 | python3 | 3.12.16-r0 | The http.cookies.Morsel class allows separator semicolons in attribute values and includes them verbatim in all output formats. An attacker who can control these values could use this to relax the cookie's Domain or SameSite restrictions. — /lib/apk/db/installed | |
| LOW | CVE-2026-103995 | python3 | 3.12.16-r0 | Response body and chunk parsing would handle non-hex or negative integers incorrectly which could result in misinterpreting HTTP response contents. — /lib/apk/db/installed | |
| LOW | CVE-2022-3219 | gpg | 2.4.9-r0 | GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB. — /lib/apk/db/installed | |
| LOW | CVE-2022-3219 | gnupg-keyboxd | 2.4.9-r0 | GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB. — /lib/apk/db/installed | |
| LOW | CVE-2022-3219 | gnupg-gpgconf | 2.4.9-r0 | GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB. — /lib/apk/db/installed | |
| LOW | CVE-2022-3219 | gnupg-dirmngr | 2.4.9-r0 | GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB. — /lib/apk/db/installed | |
| UNKNOWN | CVE-2026-19552 | python3 | 3.12.16-r0 | When ca_certs parameter was supplied to ssl.get_server_certificate() function, the identity of the certificate is not checked. — /lib/apk/db/installed | |
| UNKNOWN | CVE-2026-3479 | python3 | 3.12.16-r0 | DISPUTED: The project has clarified that the documentation was incorrect, and that pkgutil.get_data() has the same security model as open(). The documentation has been updated to clarify this point. There is no vulnerability in the function if following the intended security model. pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals. — /lib/apk/db/installed |