> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/security/reports/cve-report.md). # Vulnerability Report A read only view of the CVEs Microsoft Defender has found across your devices, one row per CVE, with any exception recorded against it shown alongside. Where [CVE Management](/user-documentation/security/defender/defender-cve-exceptions.md) is where you work the vulnerabilities, this page is where you report on them: it carries the exception detail, including who granted it, why, and when it lapses. ## Table Details | Column | Description | | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Cve Id | The CVE identifier. Each row is one CVE. | | Vulnerability Severity Level | Microsoft's severity rating for the vulnerability. | | Exploitability Level | Microsoft's assessment of how exploitable the vulnerability is. | | Devices | How many affected devices were counted. | | Software Name | The vulnerable software. | | Software Vendor | The vendor of the vulnerable software. | | Software Version | The version the vulnerability was found on. | | Exception Status | How widely an exception covers the CVE: `None` where none is recorded, `All` where a global exception applies, and `Partial` where only some of the affected tenants are covered. | | Exception Type | The reason category chosen when the exception was recorded, per tenant. | | Exception Comment | The justification written when the exception was recorded, per tenant. | | Exception Created By | Who recorded the exception, per tenant. | | Exception Readable Date | When the exception was recorded, per tenant. | | Exception Expiry | When the exception lapses, per tenant. Empty where the exception was recorded without an expiry. | {% hint style="info" %} The exception columns hold one entry per tenant, so a CVE excepted in several tenants shows several values in a single cell. Expand the cell to see which tenant each value belongs to. {% endhint %} *** ## Feature Requests / Ideas We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.cipp.app/user-documentation/security/reports/cve-report.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.