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

13 results

  • Sep 15, 2026A flaw was found in the buildah/copier Go package.CVE-2026-79705 · Other software · Red Hat · reported by Red HatMedium 4.5

    A flaw was found in the buildah/copier Go package. When used outside of Buildah by a non-root caller, a crafted tar archive containing malicious symlinks can escape the target extraction directory and create files outside the intended destination. Buildah itself uses chroot hardening and is not affected.

    Product
    Red Hat Hardened Images
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 21, 2026Buildah is a tool that facilitates building OCI images.CVE-2026-44517 · Other software · containers · reported by GitHubMedium 6.3

    Buildah is a tool that facilitates building OCI images. From 1.38.1 until 1.43.2 and 1.44.0, TempDirForURL in define/types.go does not securely confine Git repository subdirectories to the downloaded build context, and downloadToDirectory and stdinToDirectory can follow a Dockerfile symlink left by a partially extracted tar archive. A malicious server supplying a Git repository or tar archive can cause files outside the build context directory to be included in the context or copied into the build. This issue is fixed in versions 1.43.2 and 1.44.0.

    Product
    buildah
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 22, 2025A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a maliCVE-2024-11218 · Other software · Red Hat · reported by Red HatHigh 8.6

    A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.

    Product
    Red Hat Enterprise Linux 8
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 15, 2024A vulnerability was found in Podman, Buildah, and CRI-O.CVE-2024-9676 · Other software · Red Hat · reported by Red HatMedium 6.5

    A vulnerability was found in Podman, Buildah, and CRI-O. A symlink traversal vulnerability in the containers/storage library can cause Podman, Buildah, and CRI-O to hang and result in a denial of service via OOM kill when running a malicious image using an automatically assigned user namespace (`--userns=auto` in Podman and Buildah). The containers/storage library will read /etc/passwd inside the container, but does not properly validate if that file is a symlink, which can be used to cause the library to read an arbitrary file on the host.

    Product
    Red Hat Enterprise Linux 8
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 9, 2024A vulnerability was found in Buildah.CVE-2024-9675 · Other software · Red Hat · reported by Red HatHigh 7.8

    A vulnerability was found in Buildah. Cache mounts do not properly validate that user-specified paths for the cache are within our cache directory, allowing a `RUN` instruction in a Container file to mount an arbitrary directory from the host (read/write) into the container as long as those files can be accessed by the user running Buildah.

    Product
    Red Hat Enterprise Linux 8
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 18, 2024A flaw was found in Buildah (and subsequently Podman Build) which allows containers to mount arbitrary locations on the host filesystem into build containers.CVE-2024-1753 · Other software · Red Hat · reported by Red HatHigh 8.6

    A flaw was found in Buildah (and subsequently Podman Build) which allows containers to mount arbitrary locations on the host filesystem into build containers. A malicious Containerfile can use a dummy image with a symbolic link to the root filesystem as a mount source and cause the mount operation to mount the host root filesystem inside the RUN step. The commands inside the RUN step will then have read-write access to the host filesystem, allowing for full container escape at build time.

    Product
    Red Hat Enterprise Linux 8
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 8, 2022A flaw was found in Buildah.CVE-2022-4123 · Other software · Podman Project · reported by Red HatLow 3.3

    A flaw was found in Buildah. The local path and the lowest subdirectory may be disclosed due to incorrect absolute path traversal, resulting in an impact to confidentiality.

    Product
    Podman
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 8, 2022A vulnerability was found in buildah.CVE-2022-4122 · Other software · Podman Project · reported by Red HatMedium 5.3

    A vulnerability was found in buildah. Incorrect following of symlinks while reading .containerignore and .dockerignore results in information disclosure.

    Product
    Podman
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 13, 2022An incorrect handling of the supplementary groups in the Buildah container engine might lead to the sensitive information disclosure or possible data modificatiCVE-2022-2990 · Other software · Buildah Project · reported by Red HatHigh 7.1

    An incorrect handling of the supplementary groups in the Buildah container engine might lead to the sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.

    Product
    Buildah
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 4, 2022A flaw was found in buildah where containers were incorrectly started with non-empty default permissions.CVE-2022-27651 · Other software · Buildah Project · reported by Red HatMedium 6.8

    A flaw was found in buildah where containers were incorrectly started with non-empty default permissions. A bug was found in Moby (Docker Engine) where containers were incorrectly started with non-empty inheritable Linux process capabilities, enabling an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs. This has the potential to impact confidentiality and integrity.

    Product
    Buildah
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 3, 2022An information disclosure flaw was found in Buildah, when building containers using chroot isolation.CVE-2021-3602 · Other software · Buildah Project · reported by Red HatMedium 5.5

    An information disclosure flaw was found in Buildah, when building containers using chroot isolation. Running processes in container builds (e.g. Dockerfile RUN commands) can access environment variables from parent and grandparent processes. When run in a container in a CI/CD environment, environment variables may include sensitive information that was shared with the container in order to be used only by Buildah itself (e.g. container registry credentials).

    Product
    Buildah
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 31, 2020A path traversal flaw was found in Buildah in versions before 1.14.5.CVE-2020-10696 · Other software · Red Hat · reported by Red HatHigh 8.8

    A path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions.

    Product
    buildah
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 25, 2019The containers/image library used by the container tools Podman, Buildah, and Skopeo in Red Hat Enterprise Linux version 8 and CRI-O in OpenShift Container PlatCVE-2019-10214 · Other software · Buildah Project · reported by Red HatMedium 5.9

    The containers/image library used by the container tools Podman, Buildah, and Skopeo in Red Hat Enterprise Linux version 8 and CRI-O in OpenShift Container Platform, does not enforce TLS connections to the container registry authorization service. An attacker could use this vulnerability to launch a MiTM attack and steal login credentials or bearer tokens.

    Product
    Buildah
    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.