> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/manage/wsus-updates-tab/import-cve-ids.md).

# Import CVE IDs Wizard in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

The *CVE Import Wizard* feature of Patch My PC (PMPC) Publisher allows you to bulk match Common Vulnerabilities and Exposures (CVEs) against the Patch My PC catalog to quickly determine whether a fix is available, already published, or unavailable.

Security teams commonly use this feature when they provide a list of CVE IDs (for example, from a vulnerability scanner or audit report) to assess and remediate.

{% hint style="danger" %}
**Important**

The CVE Import Wizard can only match CVE IDs present in the latest Patch My PC catalog metadata. If a CVE is fixed in a newer version of an application but is not explicitly referenced in the catalog, it may not appear as **Available** in the wizard.

Vulnerabilities are often remediated by upgrading to a later application version. In some cases, deploying the latest version of a product by enabling it in the [Product Tree](/patch-my-pc-publisher/fundamentals/product-tree/working.md) may resolve a CVE, even if the CVE Import Wizard does not directly identify or match it.
{% endhint %}

## To import a list of CVE IDs

1. Load Publisher.
2. Navigate to **WSUS Updates** and click **Import CVE IDs**.
3. On the **CVE Import Wizard**, click **Browse** and select a .csv or .txt file containing the CVE IDs you wish to process.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FN37T8fpHkXBIsX09Hsq1%2Fimage.png?alt=media&amp;token=3c6f335e-9fd5-47ea-9c76-6da35c48b303" alt="Click &#x27;Browse&#x27; an on the &#x27;CVE Import Wizard&#x27;" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**

Publisher will perform a regex against all columns and rows in the csv/txt file to look for the well-known CVE ID format e.g., CVE-2025-34092
{% endhint %}

4. Click **Process**. After processing completes, you will see a table listing all detected CVE IDs, grouped by state.

<table><thead><tr><th width="121.22222900390625" valign="top">State</th><th valign="top">Means</th></tr></thead><tbody><tr><td valign="top">Available</td><td valign="top">An update is available in the Patch My PC catalog, but it hasn't been published in your environment yet.</td></tr><tr><td valign="top">Published</td><td valign="top">The update is already published to WSUS/ConfigMgr and is available for deployment.</td></tr><tr><td valign="top">Unavailable</td><td valign="top">No update is published containing that CVE ID and there is no update in the Patch My PC catalog matching it.</td></tr></tbody></table>

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FlW5dmhlPk4B2ACC1tFED%2Fimage.png?alt=media&amp;token=00bb00e0-1a79-4093-9282-12559c45b851" alt="&#x27;CVE Import Wizard&#x27; results" width="563"><figcaption></figcaption></figure>

## **Group by products**

Checking the **Group by products** checkbox at the bottom of the **CVE Import Wizard** organizes the detected CVE IDs by vendor and indicates the number of vulnerabilities by vendor. This view makes it easier to see which products account for the most CVEs and prioritize remediation.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2F1ZY7yF8ZFJkTS3w5FjYl%2Fimage.png?alt=media&amp;token=30b68238-c6b1-4a82-88e5-b94ccf7a564b" alt="Checking the &#x27;Group by products&#x27; checkbox and the sorted results" width="563"><figcaption></figcaption></figure>

## Import Selected Patches

You can either:

* Individually select updates that are in an **Available** state.
* Click the **Select All Available** button.

After selecting the desired updates, click **Import Selected Patches** to publish them immediately.

{% hint style="danger" %}
**Important**

*Importing* in this context means publishing the selected updates immediately, outside of the normal sync schedule. After clicking this button, a dialog is displayed allowing you to monitor progress in the PatchMyPC.log file.
{% endhint %}

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FuSTezxn8nINcLvVshQLt%2Fimage.png?alt=media&amp;token=c5dda624-5d7b-4556-829a-05ac16d77814" alt="Importing selected patches to publish them " width="563"><figcaption></figcaption></figure>

Click **OK** on the **Selected CVE patches have been queued for publishing** dialog.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FOKBuM0GyZYeEu0bJwrUy%2Fimage.png?alt=media&amp;token=716ace9c-d915-416a-94c9-da1aada6dca4" alt="&#x27;Selected CVE patches have been queued for publishing&#x27; dialog" width="324"><figcaption></figcaption></figure>

The **PatchMyPC.log** indicates that you requested publish on demand.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FmP8QrwxfWaGDR9lg9QJb%2Fimage.png?alt=media&amp;token=4c1c6c71-4bef-4d22-b791-4fdda289a32f" alt="PatchMyPC.log indicates the publish on demand" width="563"><figcaption></figcaption></figure>

{% hint style="danger" %}
**Important**

Even if a product is not enabled in the **WSUS Updates** tab, any update selected in the CVE Import Wizard will be published immediately when **Import Selected Patches** is clicked.

Importing patches through the CVE Import Wizard does not automatically enable the corresponding product in the **WSUS Updates** tab. If the security team who provided the list of CVE IDs determined that a product should continue to be patched, we recommend enabling the product in the [Product Tree](/patch-my-pc-publisher/fundamentals/product-tree/working.md) of the **WSUS Updates** tab to ensure future updates for that product are published automatically.
{% endhint %}

## Reporting on Updates Imported

After you import updates through the CVE Import Wizard, a report is generated based on the [Alerts](/patch-my-pc-publisher/manage/alerts-tab.md) you have configured. Depending on your alert configuration, you may receive notifications via Microsoft Teams, Slack, Email, or a combination of these.

In the example below, you received both a Teams webhook notification and an email report, confirming the imported updates.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fq0TRTgWzL90wxo19eiqV%2Fimage.png?alt=media&amp;token=f6ad1409-9dd9-4f7f-a4df-e05d24464408" alt="CVE Import Wizard Results by Webhook" width="563"><figcaption></figcaption></figure>

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FCeWABCRPVqVHaF6yC6Xe%2Fimage.png?alt=media&amp;token=c39bf645-1f41-4b9d-b308-1ef6ce1d1410" alt="CVE Import Wizard Results by Email" width="563"><figcaption></figcaption></figure>


---

# 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.patchmypc.com/patch-my-pc-publisher/manage/wsus-updates-tab/import-cve-ids.md?ask=<question>&goal=<user_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.
