{
  "cveId": "CVE-2026-15792",
  "url": "https://patchblox.com/security/cve/CVE-2026-15792",
  "summary": "CVE-2026-15792 is fixed in runfinch-finch on 1 platform by ALAS2023-2026-3140 (version 1.19.0-1.amzn2023.0.1), released September 28, 2026. It is not reported as exploited. Patch Radar priority: High.",
  "title": "runfinch-finch: Package updates are available for Amazon Linux 2023 that fix the following vulnerabilities:\nCVE-2026-78662:\n\tPrevious...",
  "description": "Package updates are available for Amazon Linux 2023 that fix the following vulnerabilities:\nCVE-2026-78662:\n\tPreviously, a channel registered in the mux\u0027s chanList is not usable until it is established. A malicious peer was able flood the channel\u0027s incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time, handlePacket drops every packet other than the open confirmation/failure, without blocking and without tearing down the connection.\n\nCVE-2026-75593:\n\tBuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to 0.31.2, a custom client can produce such an upload request to the BuildKit daemon that files can escape from the BuildKit-controlled state directory. The client needs to have valid permissions to access BuildKit control API to issue builds, eg., bypass authentication, etc. This issue is fixed in version 0.31.2.\n\nCVE-2026-61712:\n\tBuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to 0.31.1, BuildKit read attacker-controlled /etc/passwd and /etc/group files without an upper bound while resolving a username to a user identifier or group identifier in executor/oci/user.go and solver/llbsolver/ops/user_linux.go. A malicious base image or build could provide oversized files that exhausted memory during user resolution and caused out-of-memory termination of the buildkitd process. This issue is fixed in version 0.31.1.\n\nCVE-2026-61711:\n\tBuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to 0.31.1, a custom frontend could place an invalid SecurityMode value in a crafted build request, and executor/oci/spec_linux.go treated the unsupported value as a non-sandbox mode without requiring the security.insecure entitlement. This disabled Seccomp and AppArmor protections for the build container even though Linux capabilities remained restricted. This issue is fixed in version 0.31.1.\n\nCVE-2026-56855:\n\tPreviously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other messages as a protocol error and tear the connection down instead of buffering and blocking.\n\nCVE-2026-47262:\n\tMemory exhaustion DoS causing OOM kill of containerd process\n\nNOTE: https://github.com/containerd/containerd/security/advisories/GHSA-jpcc-p29g-p8mq\n\nCVE-2026-17106:\n\tThe tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory. A crafted archive can create or overwrite files outside the intended destination.\n\nCVE-2026-15793:\n\tBuildKit custom frontends or clients using the raw low-level API can set git.checkoutbundle=true when checking out Git sources. If the Git source is malicious, this could lead to a crafted command invocation on the host.\n\nCVE-2026-15792:\n\tA malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic.\n\nCVE-2026-15791:\n\tA crafted message in the BuildKit low-level build API can be used to remove the contents of the /tmp directory. The action that can normally be used to delete files inside the build container rootfs can escape into the real host temp directory.\n\nCVE-2026-15789:\n\tA custom client can produce such an upload request to the BuildKit daemon that files can escape from the BuildKit-controlled state directory. The client needs to have valid permissions to access the BuildKit control API to issue builds, e.g., bypass authentication, etc.",
  "published": "2026-09-28T09:00:00Z",
  "severity": "important",
  "epss": 0.00243,
  "epssPercentile": 0.15517,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "runfinch-finch",
      "release": "amzn 2023",
      "fixedVersion": "1.19.0-1.amzn2023.0.1",
      "fix": "ALAS2023-2026-3140",
      "url": "https://patchblox.com/security/fix/linux/alas2023-2026-3140",
      "released": "2026-09-28T09:00:00Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T19:12:23Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}