Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?
Stakeholders / Everyone with PHP in the path / Distributors and packagers / Chainguard
Chainguard: its risk register
Published patched images before the embargo lifted, according to the PHP Foundation, which Chainguard disputes; found the same bugs with an AI harness.
Kind organisation · Assigned here 1 · In its register 1 · in the story as Chainguard, Dan Lorenc, Chainguard
The register
Assigned here, or arriving through a part of this stakeholder. The part played is the one recorded for whoever holds the assignment.
| Risk | Rating | Kind | Part played | Controls |
|---|---|---|---|---|
| R02-3 Patched builds published before the embargo lifted | 16 high | Supply chain | source | ISO/IEC 29147 and 30111 29147:coordination, Cyber Resilience Act Art.13, NIST CSF 2.0 GV.SC-05, OWASP Top 10s A03:2025 |
Where its risks sit
| Likelihood / impact | 1 Minor | 2 Moderate | 3 Significant | 4 Major | 5 Severe |
|---|---|---|---|---|---|
| 5 Happening | 5 | 10 | 15 | 20 | 25 |
| 4 Likely | 4 | 8 | 12 | 16 R02-3 | 20 |
| 3 Possible | 3 | 6 | 9 | 12 | 15 |
| 2 Unlikely | 2 | 4 | 6 | 8 | 10 |
| 1 Rare | 1 | 2 | 3 | 4 | 5 |
The standards its register touches
ISO/IEC 29147 and 30111 (1), Cyber Resilience Act (1), NIST CSF 2.0 (1), OWASP Top 10s (1)