When does a fix in a hosted service need no advisory?
A vulnerability fixed in a hosted service that a product uses needs a published advisory like any other fix. An advisory is not needed only when four conditions all hold. The manufacturer runs the service, the fix is applied, users have nothing to do and no residual risk remains for users. CVD Portal records this decision on the report, aligned to prEN 40000-1-3 RLS-2-RQ-06.
Key takeaways
- The CRA calls such a service a remote data processing solution, for example the cloud back end of a device or app.
- The panel Fix in a service you run is in the Disclose stage of a resolved report that has no published advisory.
- An admin must confirm all four conditions and say why no advisory is needed.
- The report then drops out of the count of resolved vulnerabilities with no published advisory on the Operate page.
- A reopened report loses the record, because its fix did not hold.
The four conditions
| Condition | Example where it does not hold |
|---|---|
| You run the service. Users do not install, host or deploy it. | A customer runs your back end on its own servers. |
| The fix is applied in the service for every user. | The fix is live in one region only. |
| Users have nothing to do. | Users must rotate an API key or change a setting. |
| No risk remains for users. | Data was exposed before the fix. |
When one condition does not hold, publish an advisory in the Disclose stage.
Record the decision
- Open the resolved report in Submissions and go to the Disclose stage.
- In Fix in a service you run, click Check the conditions.
- Confirm each of the four conditions.
- Say why no advisory is needed in 10 to 2,000 characters. Click Record no advisory.
Only an admin can record or remove the decision. Remove the record puts the report back in the count. Each change goes to the audit log with the full reason.
In the evidence
The reports file of the GRC evidence pack has the column "No advisory needed (fix in a service you run)". It shows Yes and leaves out the reason. The tenant export includes the full record.
Sources
- Regulation (EU) 2024/2847, the Cyber Resilience Act. Article 3(1) includes remote data processing solutions in the definition of a product with digital elements, and Article 3(2) defines remote data processing. Annex I Part II point 4 asks the manufacturer to publish information on fixed vulnerabilities. Article 14 sets the reporting duties for actively exploited vulnerabilities.
- prEN 40000-1-3, requirement RLS-2-RQ-06, sets the four conditions. It is a draft standard of CEN and CENELEC, and its text is not public, so this page paraphrases it.
Limits
CVD Portal does not check the four conditions. The admin who records the decision is responsible for it. The record does not change the Article 14 duties. A vulnerability that is actively exploited is still reported to the CSIRT.
Last updated 21 November 2026.