Automated feed

Threat Wire

Aggregated every six hours from CISA KEV, NIST NVD, CISA advisories and trade reporting, then deduplicated and stored. Free to read, and it will stay that way, because these are links to other people's public work. What a membership adds is the analyst layer on top of them.

What “Exploited” means

The entry is on CISA’s Known Exploited Vulnerabilities catalogue, so it is being used against real targets rather than theorised about. A medium-severity KEV outranks a critical nobody has weaponised, and it is the one thing worth filtering on first.

Tuesday 13 October4

  1. NVDhigh8.2CVE-2025-1674

    A lack of input validation allows for out of bounds reads caused by malicious or malformed packets.

    A lack of input validation allows for out of bounds reads caused by malicious or malformed packets.

  2. NVDhigh8.2CVE-2025-1673

    A malicious or malformed DNS packet without a payload can cause an out-of-bounds read, resulting in a crash (denial of service) or an incorrect computation.

    A malicious or malformed DNS packet without a payload can cause an out-of-bounds read, resulting in a crash (denial of service) or an incorrect computation.

  3. NVDhigh7.6CVE-2025-10458

    Parameters are not validated or sanitized, and are later used in various internal operations.

    Parameters are not validated or sanitized, and are later used in various internal operations.

  4. NVDhigh7.1CVE-2025-10456

    A vulnerability was identified in the handling of Bluetooth Low Energy (BLE) fixed channels (such as SMP or ATT). Specifically, an attacker could exploit a flaw that causes the BLE target (i.e., the device under attack) to attempt to disconnect a fixed channel,…

    A vulnerability was identified in the handling of Bluetooth Low Energy (BLE) fixed channels (such as SMP or ATT). Specifically, an attacker could exploit a flaw that causes the BLE target (i.e., the device under attack) to attempt to disconnect a fixed channel, which is not allowed per the Bluetooth specification. This leads to undefined behavior, including potential assertion failures, crashes, or memory corruption, depending on the BLE stack implementation.

Every entry links to its original source. Severity is the publisher's own rating where one exists. We don't re-score other people's advisories.