---
title: "Responding to a New Vulnerability"
slug: "responding-to-a-new-vulnerability"
updated: 2026-10-27T15:43:28Z
published: 2026-10-27T15:43:28Z
canonical: "docs.databee.buzz/responding-to-a-new-vulnerability"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt
> Use this file to discover all available pages before exploring further.

# Responding to a New Vulnerability

When a major new vulnerability is announced, the first question is always “Are we affected, and where?” Frontier AI Defense's **event** view answers that in one place: which applications and devices have the vulnerability, who needs to act, and whether a vendor fix exists yet.

## Open an event

1. In the box at the top right of the page (marked with a lightning bolt), type the vulnerability's CVE ID — for example, CVE-2025-51303.
2. Select **Open event** or press Enter.

Opening an event is only a lookup. It does not notify anyone.

## Reading the event

The event panel appears at the top of the Applications tab.

![An event for a single CVE: how many applications, devices, and teams are affected, and what to do next.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/frontier-ai-16-zero-day%282%29.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A33%3A57Z&se=2026-11-11T14%3A33%3A57Z&sr=c&sp=r&sig=UFCDbn3qVXlBUd1tu4FYrScvIsI40XtnDydOAEAo3rY%3D)

*An event for a single CVE: how many applications, devices, and teams are affected, and what to do next.*

- The header shows the CVE, its exploitation grade, its severity, and whether a vendor fix is available.
- The counts show how many **applications** and **devices** are exposed, how many **teams** need to be reached, and how many affected applications have **nobody to dispatch to**.
- The **What now** box gives a plain recommendation. If a fix exists, patch the highest-exposure applications first. If not, Frontier AI Defense tells you to watch for a vendor fix.
- The table lists each affected application with a **Compile** button that sends only the fix for this CVE. The button is greyed out until a vendor fix exists.

If no scanner has reported the vulnerability yet, the panel says so and shows when each scanner last reported. **No findings does not mean you are not exposed** — scanners often take days to detect a newly announced vulnerability. The panel fills in automatically as results arrive.

## Closing an event

An event closes itself when no open findings remain for that CVE. To stop showing it sooner, select **Archive event**. Archiving only hides the panel — the findings stay in the ranked list until they are actually fixed.

## Next steps

- [Sending Fixes to Remediation Teams](/user-manual/docs/sending-fixes-to-remediation-teams)
- [Finding Your Riskiest Applications](/user-manual/docs/finding-your-riskiest-applications)