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 10 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
343new WordPress flaws this week
390,080entries in the database

10 results

  • Jun 19, 2026A remote code execution vulnerability was found in libaom, the reference AV1 codec implementation.CVE-2026-56211 · Other software · Red Hat · reported by Red HatHigh 7.1

    A remote code execution vulnerability was found in libaom, the reference AV1 codec implementation. Insufficient bounds validation in the AV1 encoder's SVC (Scalable Video Coding) layer ID control allows an attacker to supply crafted video frame pixels that overlap with internal encoder layer context structures. In fork-based video processing services, an attacker can use this to hijack the cyclic refresh map pointer, brute-force the process base address via a crash oracle, and redirect control flow to achieve arbitrary command execution. Exploitation requires the target service to use libaom with SVC encoding enabled and accept attacker-supplied video frames.

    Product
    Red Hat Enterprise Linux AI 3.3 for RHEL 9
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 19, 2026A heap-buffer-overflow read vulnerability was found in libaom, the reference AV1 codec implementation.CVE-2026-56210 · Other software · Red Hat · reported by Red HatHigh 7.1

    A heap-buffer-overflow read vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC (Scalable Video Coding) layer ID control function allows setting a spatial_layer_id exceeding the configured number of layers. This causes an out-of-bounds heap read of approximately 40,728 bytes when computing a layer context array index. An attacker who can influence SVC encoder parameters in a network-facing service could exploit this for information disclosure (heap content leak) or denial of service (segmentation fault from hitting unmapped memory).

    Product
    Red Hat Enterprise Linux AI 3.3 for RHEL 9
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 19, 2026An arbitrary address write vulnerability was found in libaom, the reference AV1 codec implementation.CVE-2026-56209 · Other software · Red Hat · reported by Red HatHigh 7.1

    An arbitrary address write vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC (Scalable Video Coding) layer ID control function allows an attacker to inject an arbitrary pointer into the cyclic refresh map field via crafted image pixel values. The encoder then writes approximately 1,200 bytes at the attacker-controlled address. This is fully deterministic and does not require a separate information leak. An attacker who can supply frames to a network-facing libaom encoder with SVC enabled could exploit this for denial of service or potential code execution.

    Product
    Red Hat Enterprise Linux AI 3.3 for RHEL 9
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 19, 2026A heap buffer overflow vulnerability was found in libaom, the reference AV1 codec implementation.CVE-2026-56208 · Other software · Red Hat · reported by Red HatHigh 7.6

    A heap buffer overflow vulnerability was found in libaom, the reference AV1 codec implementation. A flaw in the AV1 encoder's Look-Ahead Processing (LAP) mode causes the first-pass stats ring buffer wrap-around guard to be bypassed when g_lag_in_frames is set to 1 or higher. This results in a 232-byte out-of-bounds write on every encoded frame after the second, corrupting adjacent heap objects. An attacker who can influence encoder configuration in a transcoding service or WebRTC session could exploit this to cause a denial of service (process crash) or potentially achieve code execution.

    Product
    Red Hat Enterprise Linux 10.0 Extended Update Support
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 12, 2025Heap buffer overflow in libaom in Google Chrome prior to 139.0.7258.127 allowed a remote attacker to potentially exploit heap corruption via a curated set of geCVE-2025-8879 · Computers, phones & browsers · Google · reported by chrome-cve-admin@google.comHigh 8.8

    Heap buffer overflow in libaom in Google Chrome prior to 139.0.7258.127 allowed a remote attacker to potentially exploit heap corruption via a curated set of gestures. (Chromium security severity: High)

    Product
    Chrome
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 5, 2024Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow.CVE-2024-5171 · Other software · libaom · reported by cve-coordination@google.comCritical 10

    Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow. This function can be reached via 3 callers: * Calling aom_img_alloc() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid. * Calling aom_img_wrap() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid. * Calling aom_img_alloc_with_border() with a large value of the d_w, d_h, align, size_align, or border parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid.

    Product
    libaom
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 27, 2023Increasing the resolution of video frames, while performing a multi-threaded encode, can result in a heap overflow in av1_loop_restoration_dealloc().CVE-2023-6879 · Other software · libaom · reported by cve-coordination@google.comCritical 9

    Increasing the resolution of video frames, while performing a multi-threaded encode, can result in a heap overflow in av1_loop_restoration_dealloc().

    Product
    libaom
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 4, 2021aom_dsp/noise_model.c in libaom in AOMedia before 2021-03-24 has a buffer overflow.CVE-2021-30475 · Other software · Aomedia · reported by MITRECritical 9.8

    aom_dsp/noise_model.c in libaom in AOMedia before 2021-03-24 has a buffer overflow.

    Product
    Aomedia
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 2, 2021aom_dsp/grain_table.c in libaom in AOMedia before 2021-03-30 has a use-after-free.CVE-2021-30474 · Other software · Aomedia · reported by MITRECritical 9.8

    aom_dsp/grain_table.c in libaom in AOMedia before 2021-03-30 has a use-after-free.

    Product
    Aomedia
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 6, 2021aom_image.c in libaom in AOMedia before 2021-04-07 frees memory that is not located on the heap.CVE-2021-30473 · Other software · Aomedia · reported by MITRECritical 9.8

    aom_image.c in libaom in AOMedia before 2021-04-07 frees memory that is not located on the heap.

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