Skip to content
Handbook · edition 1.2 · 63 pages · free with a work email

A new CVE lands. In fifteen minutes you know what to do, and can show you did it.

Ask your AI agent about a new vulnerability with sources attached: Lattice. See Lattice

The method we use to check, analyse and triage a vulnerability, written down so that someone who is not a full-time analyst can repeat it and defend the result. It works through 10 real cases read from the CVE records, the CISA catalogue and the vendors’ own advisories, with 5 scripts run on live data and the templates to keep a record.

Cover of The CVE Triage Handbook: how to check, analyse and triage a vulnerability, and prove you closed it.

What you will be able to do

A look inside

Three pages of the handbook as they are, so you can judge the level before you register. Press a page to open it full size.

What is in it

19 chapters in seven parts and 5 appendices: 5 scripts, 6 blank templates, 4 cards and checklists, a glossary and the sources. 5 figures, including the whole method on page 2. Every chapter ends with something you can do in ten minutes.

  1. CheckPart II

    Which source answers which question, a field-by-field reading of a real record, and how to notice a change.

  2. AnalysePart III

    Preconditions, version spans, and whether the vulnerable code is reachable on your systems.

  3. TriagePart IV

    Five questions and six outcomes, 10 worked cases and the awkward ones.

  4. ActPart V

    The mitigation ladder, proving a fix, and looking back for damage.

  5. Run itPart VI

    A thirty-minute daily routine, the records and numbers worth keeping, and how to tell people.

A change in a signal, such as a new exploitation notice or a revised record, sends you back to Triage.
FoundationsPart I

The vocabulary, why the feeds disagree, and how to decode a CVSS 3.1 and 4.0 vector. Every step above stands on it.

AI agentsPart VII

What to hand an assistant, what to keep, and four questions that work on an assistant or an analyst.

AppendicesPart VIII

Five scripts, six templates, four checklists, a glossary and the sources.

Where the lookups come from, and how to check a project

The handbook’s method starts from a CVE id. Lattice is the public graph that answers it for an AI agent over MCP; the lattice-scan command line compares an id with what a project declares, or with what a server has installed (its packages, snaps, running images with their operating system and packages, and kernel), and prints evidence for a person. The guide says which of the MCP server, the Claude skill and the command line fits your job. The package is on PyPI and in the signed apt repository.

10 worked cases, 12 CVEs

Instead of invented examples, the book reuses real CVEs from the weeks it was written, each chosen because it breaks a different rule of thumb. The outcomes are our triage judgements on a stated, hypothetical estate, not rulings on any vendor.

  1. Brotli, CVE-2026-111497

    Case 1

    Act now

    A library you cannot see, a CVSS 4.0 score, and the highest chance of exploitation in the set.

  2. Linux kernel Fragnesia, CVE-2026-46300

    Case 2

    Depends on who can run code

    A local 7.8 on the exploited list: the same flaw lands differently on a shared build host and a single-tenant appliance.

  3. VMware ESX, CVE-2026-41709

    Case 3

    This week, plus an investigation

    A CVSS 2.7 on the exploited list, and what it says about whose logs you can trust.

  4. Adobe Commerce, CVE-2026-48356

    Case 4

    Act now

    Patched in July, exploited in October: why triage once is not enough.

  5. jackson-databind, CVE-2026-110879

    Case 5

    Depends on configuration

    An incomplete fix: the upgrade you already did may not cover you.

  6. Apache Kafka Connect, CVE-2026-115644

    Case 6

    Not affected, if the check says so

    A flaw that exists only when you configured something, and the one-line check that proves it.

  7. MLflow, CVE-2026-116692

    Case 7

    Depends on three facts

    Exposure that needs three conditions at once.

  8. Dell Data Domain, DSA-2026-416

    Case 8

    This week

    Four 9.8s on the appliance you restore from, published four weeks before the CVE feed, and the firewall change that comes first.

  9. Canonical LXD, CVE-2026-112816

    Case 9

    This week

    A 10.0 that is not exploited, a fix that may not be offered to you yet, and a record and an advisory that name different products.

  10. Cisco ASA and FTD, CVE-2026-76418

    Case 10

    Act now

    Exploited, with a low prediction score, a precondition you must check in every group, and no vendor workaround.

Who it is for

What makes it different

Worked on real records

Fragnesia, the VMware logging flaw, Brotli, Adobe Commerce, jackson-databind, Kafka Connect, MLflow, Canonical LXD, Cisco ASA and more, each with the command and the output.

Says what it could not read

Where a source did not render, two sources disagreed, or we had no device to run a check on, the handbook says so. Our judgements are marked as ours.
What it is not
Not a scanner and not a product. The scripts fetch public data and compare it; they do not find affected systems on your estate. The decision stays with the person who knows what the asset does.
Edition 1.2 · 2 November 2026
A one-page start with the whole method as a diagram, a box at the head of every chapter, 5 figures, and two new worked cases (Canonical LXD and Cisco ASA and FTD), read on 31 October. The method, the rules and the clocks are unchanged from edition 1.0.

Questions

Is it free?
Yes, with a work email. We send one confirmation; when you press its button, the page you land on has the handbook, and the same link stays in the email.
What do you do with my email?
We keep what you send in the form: your name, work email and company, plus the role, phone number, postal code, device count and message if you add them. A person at NamiQ reads your registration. You can unsubscribe or ask us to delete it at any time.
Do I need special tools?
No. The method is on paper. The five scripts are optional, written in Python with the standard library only, and fetch public data. They do not find affected systems on your estate.
How current is it?
Edition 1.2, 2 November 2026. The cases were read from the CVE records, the CISA catalogue and the vendor advisories on the day each case states. The method and the rules are stable; new cases appear as notes in Insights as they happen.
Can I share it?
Unaltered, with attribution. The cover says so.

Get the handbook

Register with a work email. We send one confirmation; when you press its button, the page you land on has the handbook, and the same link stays in the email. A person at NamiQ will also read your registration.

Optional. Only if you would rather we called.

Optional. Tells us your timezone and which rules apply.

Optional. Helps us tell you quickly whether we are a fit.

Backups nobody has tested, a server someone else built, access you cannot account for — whatever comes to mind first is usually the right answer.

We keep your name, work email, company and role. Nothing else. Privacy · Unsubscribe or delete