[Integrations](https://spiral.ai/integrations) › [n8n](https://spiral.ai/integrations/n8n) › [Red Hat security advisory](https://spiral.ai/integrations/n8n/red-hat-security-advisory)

# How to Use Red Hat security advisory in n8n

Fetch the products, component versions, and CVEs covered by a Red Hat advisory. Use it when you have an erratum and need to explain what that update fixes.

|  |  |
| --- | --- |
| Model | Red Hat security advisory |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with Red Hat security advisory in n8n

- Recheck Red Hat security advisory for https://access.redhat.com/errata/RHSA-2021:5137 weekly. Report changes to its covered products, component versions, or CVE list.
- Every Monday at 9am: use Red Hat security advisory to look this up and give me the result as a table.
- Pull the latest numbers from Red Hat security advisory and tell me what changed since last week.
- Check Red Hat security advisory and summarize what you find in three bullet points.
- Pull the newest data from Red Hat security advisory and give me the result as a table.

## How to set up Red Hat security advisory in n8n

Pick the way that suits you. Each takes about two minutes.

### Use the Spiral skill

1. **Send n8n this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use Spiral's MCP server

1. **Create a key**: Create a key under API keys in the console.

2. **Add an MCP Client node**: In a workflow, add an MCP Client node (or, under an AI Agent node, an MCP Client Tool) and set:

```text
https://api.spiral.ai/mcp
```

3. **Pick a tool**: The node lists Spiral's tools. In an MCP Client node pick one, such as `run`, and give it its arguments:

```json
{
  "provider": "fal",
  "model": "fal-ai/flux/schnell",
  "input": { "prompt": "a lighthouse at dawn" },
  "wait": true
}
```

4. **Run Red Hat security advisory in a workflow step**: Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds Red Hat security advisory, prices it and runs it each time the step fires.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run Red Hat security advisory**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "access-redhat-com/vulnerabilities/advisory",
    "input": {
      "advisory_id": "<advisory_id>"
    }
  }'
```

Then paste one of the prompts above: n8n finds Red Hat security advisory on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/n8n

## Red Hat security advisory tools and prices

- [Red Hat Security Data API · Advisory](https://spiral.ai/tools/alexandria/access-redhat-com/vulnerabilities/advisory) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| url |  | — | An https://access.redhat.com/errata/RHSA-... page URL. Mutually exclusive with advisory_id. Pattern: ^https?://. |

## What can you do with Red Hat security advisory in n8n?

Maintain a Red Hat vulnerability watchlist that highlights newly found records and changes in reported fix status. A scheduled agent can compare successive searches or record lookups and prepare a focused maintenance digest.

### Prepare an incident brief

Find relevant package CVEs, inspect their reported product status, and summarize the advisories that deliver fixes for an incident review.

### Plan a maintenance window

Build a product-specific vulnerability list and connect the findings to fixing advisories. Group the reported fixes into a maintenance review.

### Investigate a scanner finding

Compare a reported CVE with Red Hat's product assessment and the relevant advisory. Identify the vendor evidence needed for a remediation decision.

### Write remediation tickets

Turn package search results into tickets containing the CVE, Red Hat severity, reported product status, and fixing advisory where available.

### Review a security update

Start with an advisory, list the vulnerabilities it addresses, and inspect the CVE assessments to explain the update's security purpose.

### Document patch evidence

Assemble the advisory's covered products and component versions with the corresponding CVE assessments for a patch review record.

### Count vulnerabilities and updates separately

Use matching CVEs and their advisory references to produce separate counts of vulnerabilities and fixing updates. Explain where one advisory addresses several CVEs.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All n8n guides](https://spiral.ai/integrations/n8n)

## Red Hat security advisory in other agents

- [Amp](https://spiral.ai/integrations/amp/red-hat-security-advisory)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/red-hat-security-advisory)
- [Claude](https://spiral.ai/integrations/claude-desktop/red-hat-security-advisory)
- [Claude Code](https://spiral.ai/integrations/claude-code/red-hat-security-advisory)
- [Cline](https://spiral.ai/integrations/cline/red-hat-security-advisory)
- [Codex](https://spiral.ai/integrations/codex/red-hat-security-advisory)
- [Cursor](https://spiral.ai/integrations/cursor/red-hat-security-advisory)
- [Devin](https://spiral.ai/integrations/devin/red-hat-security-advisory)
- [dots](https://spiral.ai/integrations/dots/red-hat-security-advisory)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/red-hat-security-advisory)
- [Gemini](https://spiral.ai/integrations/gemini/red-hat-security-advisory)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/red-hat-security-advisory)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/red-hat-security-advisory)
- [goose](https://spiral.ai/integrations/goose/red-hat-security-advisory)
- [Grok](https://spiral.ai/integrations/grok/red-hat-security-advisory)
- [Grok Build](https://spiral.ai/integrations/grok-build/red-hat-security-advisory)
- [Hermes](https://spiral.ai/integrations/hermes/red-hat-security-advisory)
- [Instinct](https://spiral.ai/integrations/instinct/red-hat-security-advisory)
- [Manus](https://spiral.ai/integrations/manus/red-hat-security-advisory)
- [Muse](https://spiral.ai/integrations/muse/red-hat-security-advisory)
- [Muse Code](https://spiral.ai/integrations/muse-code/red-hat-security-advisory)
- [Notion](https://spiral.ai/integrations/notion/red-hat-security-advisory)
- [OpenClaw](https://spiral.ai/integrations/openclaw/red-hat-security-advisory)
- [opencode](https://spiral.ai/integrations/opencode/red-hat-security-advisory)
- [Perplexity](https://spiral.ai/integrations/perplexity/red-hat-security-advisory)
- [Raycast](https://spiral.ai/integrations/raycast/red-hat-security-advisory)
- [VS Code](https://spiral.ai/integrations/vscode/red-hat-security-advisory)
- [Windsurf](https://spiral.ai/integrations/windsurf/red-hat-security-advisory)
- [Zapier](https://spiral.ai/integrations/zapier/red-hat-security-advisory)

## More n8n guides

- [Red Hat CVE search](https://spiral.ai/integrations/n8n/red-hat-cve-search)
- [Semantic Scholar author publications](https://spiral.ai/integrations/n8n/semantic-scholar-author-publications)
- [Red Hat CVE details](https://spiral.ai/integrations/n8n/red-hat-cve-details)
- [Semantic Scholar author research metrics](https://spiral.ai/integrations/n8n/semantic-scholar-author-research-metrics)
- [Read the Docs project details](https://spiral.ai/integrations/n8n/read-the-docs-project-details)
- [Semantic Scholar author search](https://spiral.ai/integrations/n8n/semantic-scholar-author-search)

## Questions about Red Hat security advisory in n8n

**Can n8n use Red Hat security advisory?**

Yes. Add Spiral to n8n as an MCP server, and n8n can find and run Red Hat security advisory like any built-in tool.

**How much does Red Hat security advisory cost in n8n?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your n8n plan is separate.

**Do I need an Alexandria account to use Red Hat security advisory in n8n?**

You need no Alexandria account. n8n uses one Spiral API key for every tool, and Spiral runs Red Hat security advisory on its own Alexandria account.

**How long does it take to set up Red Hat security advisory in n8n?**

About two minutes: create a key, then add an MCP Client node, then pick a tool.

**Does n8n wait while Red Hat security advisory runs?**

Red Hat security advisory runs in the background. n8n starts the run, checks on it and gives you the json when it's ready.

**Does this cover vulnerabilities from every software vendor?**

The scope is Red Hat's product portfolio. Red Hat documents queries for any Red Hat product, including products beyond RHEL.

**When does Red Hat publish vulnerability information?**

Red Hat says it publishes CVE information and scores immediately after assessing disclosed or coordinated vulnerabilities, unless they are under embargo. It also updates machine-readable security data when fixes are released.

**Does a CVE record always include a fixed package version?**

No. Red Hat documents fixed package information as optional in a CVE record, including cases where multiple source RPMs share an erratum.

**Can one advisory cover several vulnerabilities?**

Yes. Red Hat advisories can address multiple CVEs, so counting advisories does not give you the number of vulnerabilities fixed.

**Does a product-status review include fixes already released?**

Yes, but Red Hat separates unresolved package states from releases that delivered fixes. Both are needed to describe the complete reported status of a CVE across products.

