← CRA Glossary
CVD & Vulnerability Management

Security Advisory

A security advisory is a public document published by a manufacturer to inform users of a security vulnerability in a product, the severity of the issue, and how to remediate it. Annex I Part II of the CRA requires manufacturers to publish security advisories when releasing vulnerability fixes.

A security advisory is a public document published by a manufacturer to inform users of a security vulnerability in a product, the severity of the issue, and how to remediate it. Annex I Part II of the CRA requires manufacturers to publish security advisories when releasing vulnerability fixes.

CVD & Vulnerability Management

Last updated 17 October 2026

What Is a Security Advisory?

A security advisory is a formal communication from a manufacturer to its product users that describes a security vulnerability, communicates its severity and exploitability, and provides remediation guidance - typically a patch, workaround, or configuration change. Advisories serve three audiences simultaneously: users who need to know if they are affected and what to do; security professionals who need technical detail to assess risk; and regulators and CSIRTs who need structured data to coordinate response across affected organisations. Advisories may be published in human-readable formats (web pages, PDFs) but the CRA ecosystem increasingly expects machine-readable CSAF format.

CRA reference: and

CRA Requirements for Security Advisories

Annex I Part II requires manufacturers to disclose vulnerability information to affected users when patches are released. A CRA-compliant security advisory must include:

  • Product identification - name, affected versions, and platform.
  • CVE identifier - the assigned CVE ID (or a request confirmation if pending).
  • CVSS score and vector string - severity rating with the scoring version specified.
  • Vulnerability description - a clear explanation of the vulnerability type (CWE classification recommended), attack scenario, and impact.
  • Affected versions - precise version ranges; ideally using CPE or PURL identifiers.
  • Remediation - the patched version(s) and/or workarounds.
  • Acknowledgement - credit to the researcher or reporter (unless they request anonymity).
CRA reference:Annex I Part II, Article 13

Publishing Advisories in CSAF Format

ENISA recommends that manufacturers publish security advisories in CSAF 2.0 (Common Security Advisory Framework) format to enable machine-readable processing by customers' security tools. A CSAF publication workflow requires:

  1. Authoring the advisory as a CSAF JSON document (Security Advisory profile).
  2. Validating with the open-source CSAF validator.
  3. Signing the document and generating SHA-256/SHA-512 hash files.
  4. Publishing to /.well-known/csaf/ with an updated provider-metadata.json index.
  5. Optionally listing the advisory in public CSAF aggregators (e.g. BSI's CSAF aggregator).

Machine-readable advisories allow large customers to automatically correlate your advisory against their asset inventory and prioritise patching without manual research.

CRA reference:, Article 14

Advisory Timing and Coordinated Disclosure

The timing of advisory publication is a critical CVD decision:

  • Simultaneous release (patch + advisory at the same time) is the standard - users can immediately remediate upon learning of the vulnerability.
  • Embargoed advisory - for complex vulnerabilities affecting many vendors, an advisory may be drafted under embargo and released simultaneously with a coordinated multi-vendor patch.
  • Advisory before patch - publishing an advisory without a fix (to warn users of active exploitation) is sometimes necessary and appropriate; it must include any available mitigations.
  • Post-fix delay - delaying advisory publication after a patch is available to give users time to patch (a 'silent patch') is controversial and increasingly discouraged; it leaves researchers unaware and may breach CRA obligations to inform users.

The advisory must reach all affected users - consider direct notification, mailing lists, and RSS feeds in addition to website publication.

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Must we publish a security advisory for every vulnerability we fix?+

The CRA requires manufacturers to disclose vulnerability information to affected users when patches are released. For significant vulnerabilities (particularly those with CVE IDs and CVSS scores above Low), a standalone advisory is expected. Minor security hardening changes bundled into a routine release may be described in release notes rather than a standalone advisory. However, for any vulnerability that a researcher reported through your CVD process, a standalone advisory with appropriate credit is standard practice.

How long should we keep security advisories publicly available?+

Security advisories should remain publicly accessible indefinitely - or at least for the duration of the product's support period plus several years. Advisories are referenced in customers' patch management records, insurance documentation, and regulatory compliance evidence. Removing or redirecting old advisories breaks these references and creates compliance complications. CSAF advisories published to a permanent URL with version history are the recommended approach.

What if the researcher who reported the vulnerability asks not to be credited?+

Researchers sometimes prefer anonymous disclosure - they may have legal concerns, wish to maintain a low profile, or have disclosed under specific conditions. You should honour the researcher's preference. Simply state in the acknowledgement section 'reported by an anonymous researcher' or omit the acknowledgement section entirely if the researcher requests no mention at all. Never include a researcher's name or identifying information without their explicit consent.

Sector checklists covering Security Advisory

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Smart Cameras & Video SurveillanceSmart cameras and IP video surveillance systems are frequently compromised via default credentials and unpatched firmware - they were among the first device classes targeted by Mirai and similar botnets. The CRA's prohibition on default passwords and requirement for secure update mechanisms directly target these failure modes. Manufacturers must also consider GDPR obligations around video data and the NIS2 implications for critical infrastructure deployments.Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Security Advisory fits into your complete CRA compliance programme.

View checklists →