Funding rounds, leadership changes, incidents, new capabilities and announcements across the vendors in this catalog — collected automatically from vendors' own public feeds. Product release versions are on their own page, so the landing feed here never reads as one vendor's changelog.Where this comes fromEvery item links to the vendor's own published source: a GitHub release feed, a changelog, a status page, an SEC filing or a company blog. Nothing here is written or editorially reviewed by 0-Doubt, and nothing is a recommendation — it is machine-collected public record, labelled the same way as all other baseline content on the platform. Coverage is uneven by design: a vendor that publishes no public feed will not appear, and that absence is not a judgement about the vendor.
4 matching stories — incident, in Network Detection & Response (NDR) — showing up to 3 per vendorPer-vendor capWhile browsing, no single vendor may fill more than three slots on any one page, so a vendor with a chatty release cadence cannot buy the page you are looking at. That means a page can render fewer stories than the count above. Searching a headline or naming a vendor turns the cap off, because then you have asked to see everything that matches.
In the process of fuzzing MS-RPC and Distributed File System (DFS) APIs, we discovered a one-packet mechanism set to crash an entire Windows server, which the Microsoft Security Response Center (MSRC) later assigned as CVE-2026-70111. Corelight customers using the Corelight Feed, a custom ruleset within our Open Network Detection and Response (NDR) Platform that’s designed to swiftly detect and help respond to emerging threats, are already automatically covered with the latest detection for expl
Services are back. The incident channel has gone quiet. People who spent days dealing with the breach are catching up on everything that stopped while they were responding.Now, it's time for the post-mortem. Someone presents a timeline, the team discusses what went wrong, and the meeting ends with recommendations: improve awareness, strengthen... The post After the incident: Running a post-mortem that actually changes security behavior appeared first on ManageEngine Blog.
On July 27, 2026, Apple released security updates for iOS 26.6 and iPadOS 26.6, fixing vulnerabilities across several components — Accessibility, Kernel, Libnotify, and WebKit. Among them is CVE-2026-64739, a stack-based buffer overflow in Libnotify/notifyd found and reported to Apple by ThreatBook XGPT. Apple's advisory credits Feng XUE and XGPT of ThreatBook. The same flaw also affects tvOS, watchOS, visionOS, and macOS — see Affected Scope below. There is no evidence of in-the-wild exploitati
Published: Apr 25, 2022. Vectra Research: 74% of organizations experienced a significant security incident in the past year. Visit our news releases page to read more!
