ZeroDay Findings
Sign inSign up

Every 24 hours

Tech

Original briefings on what changed in security. Each story has a small illustration matched to what it covers, a short structure, and links to the catalog records and public identifiers it discusses.

  1. Oct 9, 2026

    A Successful Fishing Expedition: Caught a Longfin Squid

    In an exciting fishing adventure off the coast of Gloucester, Massachusetts, a fisherman had a remarkable day at sea, catching a variety of fish including cod, hake, and mackerel. Among the catch was a longfin squid, also known as the Boston squid, which was identified as Doryteuthis pealeii. This species is not only notable for its culinary appeal but also plays a role in the local marine ecosystem.

    What changed

    The fishing trip highlighted the biodiversity of the waters off Massachusetts, showcasing the abundance of marine life in the area. The caught squid was prepared on a barbecue grill, providing a delicious meal that emphasizes the importance of sustainable fishing practices. While cod was plentiful, regulations prevented keeping them, showcasing the need for responsible fishing to ensure long-term viability of fish stocks.

    Who is affected

    This experience serves as a reminder of the rich maritime heritage of New England, where fishing is not just a livelihood but also a cultural tradition. The longfin squid, in particular, has gained attention for its culinary versatility, often featured in various dishes.

    What it means

    The implications of such fishing excursions extend beyond personal enjoyment; they contribute to local economies and underscore the necessity of maintaining healthy ocean ecosystems. As fishing regulations evolve, it is crucial for fishermen and consumers alike to stay informed about sustainable practices that protect marine resources for future generations.

  2. Oct 9, 2026

    AWS WAF Vulnerabilities Exposed: CVE-2026-13762 and CVE-2026-13763

    Recent vulnerabilities identified in AWS Web Application Firewall (WAF) have raised significant concerns among users and security professionals. The vulnerabilities, cataloged as CVE-2026-13762 and CVE-2026-13763, pertain to the inspection of multi-frame request bodies in HTTP/2. This issue could potentially allow attackers to bypass security measures, making it crucial for organizations utilizing AWS WAF to be aware of the risks involved.

    What changed

    The vulnerabilities affect a broad range of AWS WAF users, particularly those relying on the service for web application protection against various threats. With the increasing adoption of HTTP/2 for its performance benefits, the implications of these vulnerabilities could be extensive, affecting the overall security posture of applications deployed on AWS.

    Who is affected

    Organizations that depend on AWS WAF must take immediate action to evaluate their configurations and ensure that they are not inadvertently exposing their applications to risks associated with these vulnerabilities. This includes reviewing their security policies and potentially implementing additional layers of security to mitigate the risks until a patch or update is available.

    What it means

    As cloud services continue to evolve, the discovery of such vulnerabilities highlights the importance of continuous monitoring and incident response planning. Companies must remain vigilant in maintaining their security measures and adapting to emerging threats in the cloud landscape. The AWS community is encouraged to stay updated on any announcements regarding fixes or workarounds for these vulnerabilities to safeguard their applications effectively.