Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 2 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,762exploited flaws on CISA’s list
34added in the last 30 days
344new WordPress flaws this week
390,080entries in the database

31 results

  • Oct 5, 2026A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.CVE-2026-93321 · Other software · moby · reported by security@docker.comMedium 6.9

    A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026When proxy networking with CA injection is enabled, a build can modify its CA bundle before cleanup.CVE-2026-93315 · Other software · moby · reported by security@docker.comMedium 5.8

    When proxy networking with CA injection is enabled, a build can modify its CA bundle before cleanup. This may cause cleanup to block, operate outside the build rootfs, or fail without failing the build.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026A build step for a Git source, crafted in a specific way, can bypass some policy validation rules.CVE-2026-93326 · Other software · moby · reported by security@docker.comMedium 6

    A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026BuildKit – Product Builder for WooCommerce – Custom PC Builder: Improper Validation of Specified Quantity in InputCVE-2026-97275 · WordPress plugins & themes · reported by PatchstackMedium 5.3

    Improper Validation of Specified Quantity in Input vulnerability in VillaTheme BuildKit – Product Builder for WooCommerce – Custom PC Builder woo-product-builder allows Input Data Manipulation.This issue affects BuildKit – Product Builder for WooCommerce – Custom PC Builder: from n/a through 1.0.28.

    Product
    BuildKit – Product Builder for WooCommerce – Custom PC Builder
    Affected
    up to 1.0.28
    What to do
    Affects up to 1.0.28. Update BuildKit – Product Builder for WooCommerce – Custom PC Builder to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Oct 5, 2026The Dockerfile frontend loaded the Dockerfile and .dockerignore files of a build context into memory without a size limit.CVE-2026-93323 · Other software · moby · reported by security@docker.comMedium 6.8

    The Dockerfile frontend loaded the Dockerfile and .dockerignore files of a build context into memory without a size limit. A build context containing an oversized file could make buildkitd allocate memory proportional to that file, potentially exhausting memory and terminating the daemon, which interrupts other builds on the same instance. Fixed by rejecting such files above 16 MiB.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.CVE-2026-93322 · Other software · moby · reported by security@docker.comMedium 6.9

    A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026BuildKit may be tricked into performing file actions with special file inodes where regular files are expected.CVE-2026-93320 · Other software · moby · reported by security@docker.comMedium 6

    BuildKit may be tricked into performing file actions with special file inodes where regular files are expected. Special files may block operations or, on rootful workers, allow unintended host device access.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon toCVE-2026-93319 · Other software · moby · reported by security@docker.comMedium 5.7

    A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon to panic.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026A malicious image can advertise DiffIDs from another image while containing different layer contents.CVE-2026-93318 · Other software · moby · reported by security@docker.comHigh 7.5

    A malicious image can advertise DiffIDs from another image while containing different layer contents. In affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without validating that they matched the actual layer contents. If a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build using the victim image may mount the attacker-controlled layer contents as the base image. This can allow code from the malicious image to run in the victim build, for example by replacing a commonly executed path such as /bin/sh. The attacker-controlled code may read build secrets mounted into the build, access other build resources, alter output artifacts, or hang the build. The issue affects both regular snapshotters and lazy-pulling snapshotters such as stargz.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest.CVE-2026-93317 · Other software · moby · reported by security@docker.comMedium 5.9

    An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest. The resulting snapshot could be cached under that digest and reused by a later victim build, compromising build-input integrity.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 5, 2026If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices.CVE-2026-93316 · Other software · moby · reported by security@docker.comHigh 7.1

    If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices. This can happen maliciously or by accident.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 2, 2026BuildKit: Does not properly sanitise and escape data submitted by contributor-level users before storing it and later using it in a SQL queryCVE-2026-94298 · WordPress plugins & themes · reported by WPScanMedium 6.2

    The BuildKit WordPress plugin before 1.0.29 does not properly sanitise and escape data submitted by contributor-level users before storing it and later using it in a SQL query, allowing a Contributor to inject SQL that runs against the database once the resulting content is published and viewed by any unauthenticated visitor.

    Product
    BuildKit
    Fixed in
    1.0.29
    What to do
    Update BuildKit to 1.0.29 or newer.
  • Oct 1, 2026BuildKit – Product Builder for WooCommerce – Custom PC Builder: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVE-2026-102379 · WordPress plugins & themes · reported by PatchstackHigh 8.5

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in VillaTheme BuildKit – Product Builder for WooCommerce – Custom PC Builder woo-product-builder allows Blind SQL Injection.This issue affects BuildKit – Product Builder for WooCommerce – Custom PC Builder: from n/a through 1.0.28.

    Product
    BuildKit – Product Builder for WooCommerce – Custom PC Builder
    Affected
    up to 1.0.28
    What to do
    Affects up to 1.0.28. Update BuildKit – Product Builder for WooCommerce – Custom PC Builder to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Aug 19, 2026BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2026-75593 · Other software · moby · reported by GitHubHigh 7.2

    BuildKit 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.

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 19, 2026BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2026-61712 · Other software · moby · reported by GitHubLow 2.3

    BuildKit 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.

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 19, 2026BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2026-61711 · Other software · moby · reported by GitHubMedium 5.3

    BuildKit 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.

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 21, 2026BuildKit custom frontends or clients using the raw low-level API can set git.checkoutbundle=true when checking out Git sources.CVE-2026-15793 · Other software · moby · reported by security@docker.comHigh 7.3

    BuildKit 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.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 21, 2026A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic.CVE-2026-15792 · Other software · moby · reported by security@docker.comMedium 6

    A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 21, 2026A crafted message in the BuildKit low-level build API can be used to remove the contents of the /tmp directory.CVE-2026-15791 · Other software · moby · reported by security@docker.comLow 1.8

    A 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.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 21, 2026A custom client can produce such an upload request to the BuildKit daemon that files can escape from the BuildKit-controlled state directory.CVE-2026-15789 · Other software · moby · reported by security@docker.comMedium 6.9

    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 the BuildKit control API to issue builds, e.g., bypass authentication, etc.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 20, 2026BuildKit's cache mount source= selector on Windows Container on Windows (WCOW) workers does not detect NTFS directory junctions placed inside the cache root.CVE-2026-15788 · Other software · moby · reported by security@docker.comMedium 5.6

    BuildKit's cache mount source= selector on Windows Container on Windows (WCOW) workers does not detect NTFS directory junctions placed inside the cache root. A build authored by an untrusted user on a WCOW-configured BuildKit daemon can read arbitrary host files reachable to the BuildKit daemon process.

    Product
    BuildKit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 27, 2026BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2026-33748 · Other software · moby · reported by GitHubHigh 8.2

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to version 0.28.1, insufficient validation of Git URL fragment subdir components may allow access to files outside the checked-out Git repository root. Possible access is limited to files on the same mounted filesystem. The issue has been fixed in version v0.28.1 The issue affects only builds that use Git URLs with a subpath component. As a workaround, avoid building Dockerfiles from untrusted sources or using the subdir component from an untrusted Git repository where the subdir component could point to a symlink.

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 26, 2026BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2026-33747 · Other software · moby · reported by GitHubHigh 8.4

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to version 0.28.1, when using a custom BuildKit frontend, the frontend can craft an API message that causes files to be written outside of the BuildKit state directory for the execution context. The issue has been fixed in v0.28.1. The vulnerability requires using an untrusted BuildKit frontend set with `#syntax` or `--build-arg BUILDKIT_SYNTAX`. Using these options with a well-known frontend image like `docker/dockerfile` is not affected.

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 17, 2025Buildx is a Docker CLI plugin that extends build capabilities using BuildKit.CVE-2025-0495 · Other software · docker · reported by security@docker.comMedium 4.1

    Buildx is a Docker CLI plugin that extends build capabilities using BuildKit. Cache backends support credentials by setting secrets directly as attribute values in cache-to/cache-from configuration. When supplied as user input, these secure values may be inadvertently captured in OpenTelemetry traces as part of the arguments and flags for the traced CLI command. OpenTelemetry traces are also saved in BuildKit daemon's history records. This vulnerability does not impact secrets passed to the Github cache backend via environment variables or registry authentication.

    Product
    buildx
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 31, 2024BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2024-23653 · Other software · moby · reported by GitHubCritical 9.8

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 31, 2024BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2024-23652 · Other software · moby · reported by GitHubCritical 10

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 31, 2024BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2024-23651 · Other software · moby · reported by GitHubHigh 8.7

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with --mount=type=cache,source=... options.

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 31, 2024BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2024-23650 · Other software · moby · reported by GitHubMedium 5.3

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic. The issue has been fixed in v0.12.5. As a workaround, avoid using BuildKit frontends from untrusted sources.

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 22, 2023A time-of-check-time-of-use race condition vulnerability in Buildkite Elastic CI for AWS versions prior to 6.7.1 and 5.22.5 allows the buildkite-agent user to bCVE-2023-43741 · Other software · Buildkite · reported by MITREHigh 7

    A time-of-check-time-of-use race condition vulnerability in Buildkite Elastic CI for AWS versions prior to 6.7.1 and 5.22.5 allows the buildkite-agent user to bypass a symbolic link check for the PIPELINE_PATH variable in the fix-buildkite-agent-builds-permissions script.

    Product
    Elastic CI Stack
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 22, 2023A symbolic link following vulnerability in Buildkite Elastic CI for AWS versions prior to 6.7.1 and 5.22.5 allows the buildkite-agent user to change ownership oCVE-2023-43116 · Other software · Buildkite · reported by MITREHigh 7.8

    A symbolic link following vulnerability in Buildkite Elastic CI for AWS versions prior to 6.7.1 and 5.22.5 allows the buildkite-agent user to change ownership of arbitrary directories via the PIPELINE_PATH variable in the fix-buildkite-agent-builds-permissions script.

    Product
    Elastic CI Stack
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 6, 2023BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.CVE-2023-26054 · Other software · moby · reported by GitHubMedium 6.5

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In affected versions when the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation. Git URL can be passed in two ways: 1) Invoking build directly from a URL with credentials. 2) If the client sends additional version control system (VCS) info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from `.git/config` file. When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation. Provenance attestations and VCS info hints were added in version v0.11.0. Previous versions are not vulnerable. In v0.10, when building directly from Git URL, the same URL could be visible in `BuildInfo` structure that is a predecessor of Provenance attestations. Previous versions are not vulnerable. This bug has been fixed in v0.11.4. Users are advised to upgrade. Users unable to upgra

    Product
    buildkit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.