In short: Patch PHP and self-managed GitLab first: both have critical flaws that let attackers run code without logging in, and CSA reports attacks on PHP. Then update NGINX to 1.31.7 or 1.30.6, Node.js to 22.23.4, 24.22.1 or 26.12.1, and Go to 1.27.3 or 1.26.10. Check your TLS chain for eMudhra.
Between 14 and 21 October 2026, PHP, GitLab, NGINX, Node.js and Go all released security fixes, and eMudhra had eight intermediate certificates revoked after their private keys were found to be weak. Two of these matter most for Singapore businesses: PHP and self-managed GitLab both have critical flaws that let an attacker run code on your server without logging in. The Cyber Security Agency of Singapore (CSA) has issued alerts for PHP, NGINX and GitLab.
This page lists what is affected, the version to move to, and what to ask your developer or IT provider. Facts were checked against the vendors’ own advisories on 23 October 2026.
Summary: what to update
| Software | CVEs | Highest severity (vendor) | Update to | CSA alert |
|---|---|---|---|---|
| PHP | 2 | Critical, CVSS v4.0 9.2 | 8.5.12, 8.4.27, 8.3.36 or 8.2.35 | AL-2026-151 |
| GitLab (self-managed) | 12 | Critical, CVSS 10.0 | 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13 | AL-2026-152 |
| NGINX | 5 | Medium per nginx.org; CSA cites CVSS v4.0 9.2 | 1.31.7 or later, or 1.30.6 or later | AL-2026-150 |
| Node.js | 10 | High | 22.23.4, 24.22.1 or 26.12.1 | None found |
| Go | 1 | Not rated; Go recommends upgrading immediately | 1.27.3 or 1.26.10 | None found |
| eMudhra certificates | 8 intermediates revoked | Key compromise | Check your TLS chain | None found |
PHP: critical remote code execution (“PHP2Shell”)
PHP published fixes for two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, on 21 October 2026 (php.net). PHP calls them critical, unauthenticated remote code execution, with a CVSS v4.0 score of 9.2. CSA’s alert names the issue PHP2Shell and reports widespread exploitation attempts and public proof-of-concept code.
- Who is affected: any PHP setup that serves web requests, including PHP-FPM, mod_php, CGI, FrankenPHP and LiteSpeed. That covers most WordPress, WooCommerce, Laravel and Magento sites. Risk is highest with mod_php.
- Update to: 8.5.12, 8.4.27, 8.3.36 or 8.2.35.
- Older versions: PHP 8.1 and older get no upstream fix. If your site still runs one of them, plan an upgrade now. PHP 8.2 itself reaches end of life on 31 December 2026.
- Interim measures: PHP describes partial mitigations through memory_limit, post_max_size and disabling session.upload_progress, but updating is the only complete fix.
If you use shared hosting, ask your host whether the PHP versions on your account have been updated. Many hosts let you choose the PHP version in the control panel.
GitLab: CVSS 10 flaw in self-managed instances
GitLab’s critical patch release on 21 October 2026 fixes 12 vulnerabilities: 1 critical, 2 high, 5 medium and 4 low (GitLab). The critical one, CVE-2026-110264, is rated CVSS 10.0. An integer overflow in the regex compiler lets an unauthenticated user run code on the server. It affects Community and Enterprise Editions from 7.0 onwards.
- Who is affected: companies running their own GitLab server. GitLab.com is already patched.
- Update to: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13.
A self-managed GitLab server usually holds source code, deployment keys and credentials, so a compromise there can spread to everything it deploys. Patch it the same day if you can.
NGINX: five vulnerabilities fixed on 14 October
NGINX released 1.31.7 (mainline) and 1.30.6 (stable) on 14 October 2026 with fixes for five CVEs: CVE-2026-15176, CVE-2026-93479, CVE-2026-95101, CVE-2026-97629 and CVE-2026-97205 (nginx.org). nginx.org rates them medium. CSA’s alert cites CVSS v4.0 scores of 9.2 for three of them and also lists affected F5 products, including NGINX Plus R33 to R37 and NGINX Ingress Controller 5.6.0 to 5.6.3.
The most serious issue is a heap buffer overflow when the alias and rewrite directives are combined. An unauthenticated attacker can crash worker processes, and code execution is possible if address-space protections are disabled or bypassed.
- Update to: 1.31.7 or later, or 1.30.6 or later. For NGINX Plus and other F5 products, follow F5’s advisories linked from the CSA alert.
Node.js: 10 vulnerabilities, 4 rated high
Node.js released fixes on 21 October 2026 for 10 CVEs: 4 high, 3 medium and 3 low (Node.js). The most serious, CVE-2026-111497, is an out-of-bounds write in the Brotli decoder that can lead to remote code execution. Several high-rated issues bypass TLS hostname checks.
- Who is affected: the 26.x, 24.x and 22.x release lines, and all end-of-life lines.
- Update to: 22.23.4, 24.22.1 or 26.12.1. These releases also update the bundled CA certificates for the eMudhra incident.
- End-of-life versions: if your app runs on Node.js 20 or older, there is no fix. Upgrading the runtime is the fix.
Go: one certificate verification fix
Go 1.27.3 and 1.26.10, released on 19 October 2026, fix CVE-2026-111943 in crypto/x509 (go.dev). Certificate verification now rejects chains through a small set of distrusted intermediates, which is Go’s response to the eMudhra incident. Go does not rate the issue but recommends upgrading immediately. Rebuild and redeploy Go services after updating the toolchain.
eMudhra: eight intermediate certificates revoked
On 17 October 2026, a researcher reported that eight eMudhra intermediate CA certificates had private keys that could be recovered. eMudhra revoked all eight the next day (eMudhra). Mozilla and Google blocked the intermediates in Firefox and Chrome (Mozilla), and both are removing the emSign ECC Root CA - G3 root that signed them (Bugzilla). In the Bugzilla discussion, Chrome’s removal was expected in Chrome Stable around 27 October 2026.
No misissued certificate has been found. The practical impact is the root removal: certificates that chain to emSign ECC Root CA - G3 will stop being trusted. According to the Bugzilla discussion, nearly all of them sit in one US higher-education ecosystem, so most Singapore businesses are not affected.
What to check: open your website in a browser, view the certificate, and look at the chain. If it ends in emSign ECC Root CA - G3, replace the certificate with one from a different hierarchy before the root is removed. For servers and apps that make outbound TLS connections, keep the operating system’s ca-certificates package, Node.js and Go up to date.
What to ask your developer or IT provider this week
- Which PHP version does each of our websites and apps run, and has it been updated?
- Do we run our own GitLab server? If so, which version is it on now?
- Which NGINX version do our servers, load balancers and Kubernetes ingress controllers run?
- Which Node.js and Go versions are our apps built and deployed on?
- Does any of our certificates chain to emSign ECC Root CA - G3?
- Who is responsible for applying security updates, and how quickly are critical ones applied?
If nobody can answer the last question, that is the gap to fix. CSA’s Cyber Essentials mark covers patching as one of its core areas, and a managed security or IT provider can take ownership of updates. After patching an exposed system, a penetration test can confirm nothing else is open.
Under the PDPA’s protection obligation, organisations must make reasonable security arrangements to protect personal data (PDPC). Applying critical security updates promptly is part of that.
Get help
FYAdvisers can introduce one to five cybersecurity providers in Singapore who can check your systems, apply updates or take on patching as an ongoing service. A concierge confirms what you need first. It is free for businesses.
Frequently asked questions
Which of these vulnerabilities is most urgent?
PHP and self-managed GitLab. Both have critical flaws that allow remote code execution without logging in. PHP rates its two CVEs critical with a CVSS v4.0 score of 9.2, and GitLab's critical CVE is rated CVSS 10.0. CSA's alert on PHP reports widespread exploitation attempts and public proof-of-concept code.
Were all of these vulnerabilities announced on the same day?
No. The NGINX fixes were released on 14 October 2026, the eMudhra incident was reported on 17 October, Go released its fix on 19 October, and PHP, Node.js and GitLab published fixes on 21 October.
My website runs on WordPress. Does the PHP vulnerability affect me?
WordPress runs on PHP, so the PHP version on your hosting matters. Ask your host or developer which PHP version the site runs and whether it has been updated to 8.5.12, 8.4.27, 8.3.36 or 8.2.35. PHP 8.1 and older receive no upstream fix.
Do I need to do anything about the eMudhra certificate incident?
Most Singapore businesses do not. Check whether your website's TLS certificate chains to emSign ECC Root CA - G3. If it does, replace it with a certificate from another hierarchy before Chrome removes that root, which was expected around 27 October 2026. Also keep the trust stores of servers and apps up to date.
Who can patch these systems for us?
Your hosting provider, IT support provider or developer. If nobody owns patching, a managed security or IT provider can take it on. FYAdvisers can introduce one to five cybersecurity providers at no cost to your business.
