Safeguard
Security Guides•

Advisory, bulletin, notice or release note: what is the difference?

Advisories, bulletins, notices, release notes and CVE records overlap but are not the same. Plain definitions and what to do with each type of document.

Safeguard Security Team
3 min read

An advisory describes a specific vulnerability and its fix. A bulletin is often a periodic roundup of several. A notice or announcement is a heads-up, sometimes before details exist. A release note lists changes, including security fixes. A CVE record is an identifier entry, not guidance. Vendors use these words loosely, so read the content, not the label.

Plain definitions

TermUsually meansTypical contentWhat you do
Security advisoryA document about one issue or a related setAffected versions, fix, workaround, creditCheck exposure, plan the fix
Security bulletinA scheduled roundup of fixesA list of issues, often with severityScan the list for your products
Security notice or announcementA heads-upA date and severity, with few detailsPrepare a window
Release noteA change list for a versionNew features and fixes, sometimes security itemsRead when you upgrade, but do not rely on it alone
CVE recordAn identifier entryA short description, affected products, referencesUse as a key to look up the rest
Vulnerability noteA coordinated writeup, sometimes about many vendorsSummary and affected vendor listCheck the vendor list for yours

These are general meanings. A given vendor may call a single issue a bulletin, so use the table as a starting guide, not a rule.

Why the difference matters

If you treat a roundup bulletin like a single advisory, you may read the headline and miss the fifth item that names your product. If you treat a CVE record as the whole story, you may miss a workaround that only the vendor advisory states. If you rely on a release note, you may miss that a security fix was buried under a general "stability improvements" line.

How to read each type

  1. Advisory: go straight to affected versions and the fixed version. Then read workarounds.
  2. Bulletin: search the page for each product name you run, not just the first screen.
  3. Notice: write down the date and severity if given. Plan capacity, then wait for details.
  4. Release note: if you are deciding whether to upgrade for security reasons, look for a linked advisory.
  5. CVE record: check the state and the references. See CVE record states.

Which one is authoritative

For a vendor's product, the vendor's own advisory is the best source of truth about affected versions and fixes. A CVE record is useful as a stable identifier. A news article or social post is a lead. For the order to trust sources in, see primary vs secondary sources in security news.

A habit to build

When someone shares a link in chat, ask what type of document it is, who wrote it, and whether it names a version. Those three answers decide how much weight to give it.

Where Safeguard fits

Safeguard's SBOM and dependency scanning supplies the product and version facts you compare against whatever document type you read. A free scan is at https://gold.safeguard.sh/scan.

Quick check

Is a CVE the same as an advisory?

No. A CVE is an identifier with a short record. An advisory is a fuller document with fix guidance.

Should I trust release notes for security fixes?

Use them as a hint. Look for a linked advisory for the details.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.