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

18 results

  • Sep 21, 2026Fluent Bit is a fast and lightweight logs, metrics, and traces processor for Linux, BSD, macOS, and Windows.CVE-2026-61674 · Other software · fluent · reported by GitHubCritical 9.2

    Fluent Bit is a fast and lightweight logs, metrics, and traces processor for Linux, BSD, macOS, and Windows. From 0.11.0 until 5.0.8, plugins/out_forward/forward.c secure_forward_pong copies the server-controlled PONG[2] reason into the 32-byte stack buffer msg with memcpy without checking its MessagePack type or length. An attacker who controls or can impersonate an out_forward Secure Forward destination configured with Shared_Key or Empty_Shared_Key can send an oversized reason during the first handshake and overwrite stack control data. Protected builds reliably terminate, while builds without a stack canary or with a disclosure can allow remote code execution as the Fluent Bit process user. When the opt-in --supervisor mode is used, fork-only respawns preserve the canary and address layout, allowing repeated crash-or-survive probes to support code execution on a hardened build; ordinary exec-based or service-manager restarts do not preserve that state. This issue is fixed in version 5.0.8.

    Product
    fluent-bit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 24, 2025Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins contain a flaw in the tag_key validation logic that fails to enforce exact key-length matchingCVE-2025-12978 · Other software · FluentBit · reported by cret@cert.orgMedium 5.4

    Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins contain a flaw in the tag_key validation logic that fails to enforce exact key-length matching. This allows crafted inputs where a tag prefix is incorrectly treated as a full match. A remote attacker with authenticated or exposed access to these input endpoints can exploit this behavior to manipulate tags and redirect records to unintended destinations. This compromises the authenticity of ingested logs and can allow injection of forged data, alert flooding and routing manipulation.

    Product
    Fluent Bit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 24, 2025Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins fail to sanitize tag_key inputs.CVE-2025-12977 · Other software · FluentBit · reported by cret@cert.orgCritical 9.1

    Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins fail to sanitize tag_key inputs. An attacker with network access or the ability to write records into Splunk or Elasticsearch can supply tag_key values containing special characters such as newlines or ../ that are treated as valid tags. Because tags influence routing and some outputs derive filenames or contents from tags, this can allow newline injection, path traversal, forged record injection, or log misrouting, impacting data integrity and log routing.

    Product
    Fluent Bit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 24, 2025Fluent Bit out_file plugin does not properly sanitize tag values when deriving output file names.CVE-2025-12972 · Other software · FluentBit · reported by cret@cert.orgMedium 5.3

    Fluent Bit out_file plugin does not properly sanitize tag values when deriving output file names. When the File option is omitted, the plugin uses untrusted tag input to construct file paths. This allows attackers with network access to craft tags containing path traversal sequences that cause Fluent Bit to write files outside the intended output directory.

    Product
    Fluent Bit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 24, 2025The extract_name function in Fluent Bit in_docker input plugin copies container names into a fixed size stack buffer without validating length.CVE-2025-12970 · Other software · FluentBit · reported by cret@cert.orgHigh 8.8

    The extract_name function in Fluent Bit in_docker input plugin copies container names into a fixed size stack buffer without validating length. An attacker who can create containers or control container names, can supply a long name that overflows the buffer, leading to process crash or arbitrary code execution.

    Product
    Fluent Bit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 24, 2025Fluent Bit in_forward input plugin does not properly enforce the security.users authentication mechanism under certain configuration conditions.CVE-2025-12969 · Other software · FluentBit · reported by cret@cert.orgMedium 6.5

    Fluent Bit in_forward input plugin does not properly enforce the security.users authentication mechanism under certain configuration conditions. This allows remote attackers with network access to the Fluent Bit instance exposing the forward input to send unauthenticated data. By bypassing authentication controls, attackers can inject forged log records, flood alerting systems, or manipulate routing decisions, compromising the authenticity and integrity of ingested logs.

    Product
    Fluent Bit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 7, 2025An issue in fluent-bit v.3.7.2 allows a local attacker to cause a denial of service via the cfl_list_size in cfl_list.h:165.CVE-2025-29478 · Other software · Treasuredata · reported by MITREMedium 5.5

    An issue in fluent-bit v.3.7.2 allows a local attacker to cause a denial of service via the cfl_list_size in cfl_list.h:165.

    Product
    Fluent BIT
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 4, 2025An issue in fluent-bit v.3.7.2 allows a local attacker to cause a denial of service via the function consume_event.CVE-2025-29477 · Other software · Treasuredata · reported by MITREMedium 5.5

    An issue in fluent-bit v.3.7.2 allows a local attacker to cause a denial of service via the function consume_event.

    Product
    Fluent BIT
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 18, 2025An issue was discovered in Fluent Bit 3.1.9.CVE-2024-50609 · Other software · Treasuredata · reported by MITREHigh 7.5

    An issue was discovered in Fluent Bit 3.1.9. When the OpenTelemetry input plugin is running and listening on an IP address and port, one can send a packet with Content-Length: 0 and it crashes the server. Improper handling of the case when Content-Length is 0 allows a user (with access to the endpoint) to perform a remote Denial of service attack. The crash happens because of a NULL pointer dereference when 0 (from the Content-Length) is passed to the function cfl_sds_len, which in turn tries to cast a NULL pointer into struct cfl_sds. This is related to process_payload_traces_proto_ng() at opentelemetry_prot.c.

    Product
    Fluent BIT
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 18, 2025An issue was discovered in Fluent Bit 3.1.9.CVE-2024-50608 · Other software · Treasuredata · reported by MITREHigh 7.5

    An issue was discovered in Fluent Bit 3.1.9. When the Prometheus Remote Write input plugin is running and listening on an IP address and port, one can send a packet with Content-Length: 0 and it crashes the server. Improper handling of the case when Content-Length is 0 allows a user (with access to the endpoint) to perform a remote Denial of service attack. The crash happens because of a NULL pointer dereference when 0 (from the Content-Length) is passed to the function cfl_sds_len, which in turn tries to cast a NULL pointer into struct cfl_sds. This is related to process_payload_metrics_ng() at prom_rw_prot.c.

    Product
    Fluent BIT
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 20, 2024A memory corruption vulnerability in Fluent Bit versions 2.0.7 thru 3.0.3.CVE-2024-4323 · Other software · Fluent Bit · reported by vulnreport@tenable.comCritical 9.8

    A memory corruption vulnerability in Fluent Bit versions 2.0.7 thru 3.0.3. This issue lies in the embedded http server’s parsing of trace requests and may result in denial of service conditions, information disclosure, or remote code execution.

    Product
    Fluent Bit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 26, 2024In Fluent Bit 2.1.8 through 2.2.1, a NULL pointer dereference can be caused via an invalid HTTP payload with the content type of x-www-form-urlencoded.CVE-2024-23722 · Other software · fluent · reported by MITREHigh 7.5

    In Fluent Bit 2.1.8 through 2.2.1, a NULL pointer dereference can be caused via an invalid HTTP payload with the content type of x-www-form-urlencoded. It crashes and does not restart. This could result in logs not being delivered properly.

    Product
    fluent_bit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 11, 2023An issue was discovered in Treasure Data Fluent Bit 1.7.1, a wrong variable is used to get the msgpack data resulting in a heap overflow in flb_msgpack_gelf_valCVE-2021-46879 · Other software · Treasuredata · reported by MITREHigh 7.8

    An issue was discovered in Treasure Data Fluent Bit 1.7.1, a wrong variable is used to get the msgpack data resulting in a heap overflow in flb_msgpack_gelf_value_ext. An attacker can craft a malicious file and tick the victim to open the file with the software, triggering a heap overflow and execute arbitrary code on the target system.

    Product
    Fluent BIT
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 11, 2023An issue was discovered in Treasure Data Fluent Bit 1.7.1, erroneous parsing in flb_pack_msgpack_to_json_format leads to type confusion bug that interprets whatCVE-2021-46878 · Other software · Treasuredata · reported by MITREHigh 7.8

    An issue was discovered in Treasure Data Fluent Bit 1.7.1, erroneous parsing in flb_pack_msgpack_to_json_format leads to type confusion bug that interprets whatever is on the stack as msgpack maps and arrays, leading to use-after-free. This can be used by an attacker to craft a specially craft file and trick the victim opening it using the affect software, triggering use-after-free and execute arbitrary code on the target system.

    Product
    Fluent BIT
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 30, 2021Fluent Bit (aka fluent-bit) 1.7.0 through 1.7.4 has a double free in flb_free (called from flb_parser_json_do and flb_parser_do).CVE-2021-36088 · Other software · treasuredata · reported by MITRECritical 9.8

    Fluent Bit (aka fluent-bit) 1.7.0 through 1.7.4 has a double free in flb_free (called from flb_parser_json_do and flb_parser_do).

    Product
    fluent_bit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 10, 2021Fluent Bit 1.6.10 has a NULL pointer dereference when an flb_malloc return value is not validated by flb_avro.c or http_server/api/v1/metrics.c.CVE-2021-27186 · Other software · Treasuredata · reported by MITREHigh 7.5

    Fluent Bit 1.6.10 has a NULL pointer dereference when an flb_malloc return value is not validated by flb_avro.c or http_server/api/v1/metrics.c.

    Product
    Fluent BIT
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 3, 2021flb_gzip_compress in flb_gzip.c in Fluent Bit before 1.6.4 has an out-of-bounds write because it does not use the correct calculation of the maximum gzip data-sCVE-2020-35963 · Other software · Treasuredata · reported by MITREHigh 7.8

    flb_gzip_compress in flb_gzip.c in Fluent Bit before 1.6.4 has an out-of-bounds write because it does not use the correct calculation of the maximum gzip data-size expansion.

    Product
    Fluent BIT
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 13, 2019An issue was discovered in the MQTT input plugin in Fluent Bit through 1.0.4.CVE-2019-9749 · Other software · Treasuredata · reported by MITREHigh 7.5

    An issue was discovered in the MQTT input plugin in Fluent Bit through 1.0.4. When this plugin acts as an MQTT broker (server), it mishandles incoming network messages. After processing a crafted packet, the plugin's mqtt_packet_drop function (in /plugins/in_mqtt/mqtt_prot.c) executes the memmove() function with a negative size parameter. That leads to a crash of the whole Fluent Bit server via a SIGSEGV signal.

    Product
    Fluent BIT
    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.