When a significant security vulnerability or attack is disclosed, we assess our exposure and publish the result here, whether or not we are affected. Customers and partners can use this page to answer their own supplier questionnaires without waiting for a reply from us.
How we assess an advisory
- We check what is actually running, not what our records say. We read software versions directly from every live system, including components bundled inside other applications.
- We check whether the vulnerable code can run at all, for example whether it needs particular hardware or configuration.
- We check whether the affected system can be reached, and by whom.
- Where we are affected, we record the issue in our change control process, fix it, and update this page with what we did and when.
Magic Suite, our customer-facing platform, is built on Microsoft .NET and runs on a currently supported .NET runtime. We release a new version every month, and each release includes current .NET runtime and NuGet dependency updates, with automated code and dependency scanning in our build pipeline.
Advisories
| Advisory | Assessed | Status | Summary |
|---|---|---|---|
| NGINX2Root (CVE-2026-123007 and four related CVEs), nginx | 2026-11-19 | Mitigated | The Magic Suite Australia region uses an affected version of nginx at its internet-facing front end. The two flaws that could be reached there both need HTTP/2, so we disabled HTTP/2 for that region on 19 November 2026, which closes the route to them. Browsers and API clients continue to work over HTTP/1.1. The other three flaws need features we do not use. HTTP/2 will stay off until that front end runs a fixed version of nginx, and we will update this page when it does. Our other production systems use a different technology at their internet-facing front end, which is not affected. |
| Java4Shell (CVE-2026-114938), OpenJDK | 2026-11-18 | Not affected | Magic Suite does not use Java. Java runs only in a small number of internal supporting systems, and the processors that host them do not support AVX-512, which the vulnerability needs, so the vulnerable code cannot run. As a precaution we are moving those systems to the fixed Java builds as vendors release them. |
| Optimizely Web supply-chain attack (no CVE), 2026-11-16 | 2026-11-18 | Not affected | We do not use Optimizely on our websites or in Magic Suite, so no Optimizely script is served to our visitors or users. |
| PHP2Shell (CVE-2026-109618, CVE-2026-109619), PHP | 2026-10-22 | Patched | Systems running affected PHP versions were patched on 22 October 2026. We found no evidence of compromise. |
Questions
If you need more detail for your own assessment, or want to ask about an advisory not listed here, please contact us. Our wider approach to information security is described in our policies and certifications.