In the middle of the Dashain holidays, Nepal Rastra Bank did something a central bank rarely does. Its October 23 emergency notice informed the public that its website and web-based services were being taken offline temporarily. The reason cited was a "technical glitch in PHP software." Private banks followed with notices of their own, saying digital transactions would be suspended while their security systems were strengthened. Government portals went dark. The Customs Department shut down the system that tracks cargo vehicles. For many Nepalis, a country that had spent a decade promising a digital future suddenly appeared to have pulled the plug on itself.
The moment may have triggered panic, but it was not a cyberattack on Nepal. The central bank had taken precautionary measures against a flaw in a tool that only domain experts typically understand. This episode, therefore, deserves a clear explanation.
What actually went wrong
PHP is a server-side programming language that powers websites. By most estimates, more than two-thirds of websites worldwide use it, including the content management systems behind a vast number of government, banking and business websites. When much of the web runs on a shared foundation, a crack in that foundation becomes everyone's problem.
Nepal Rastra Bank's action was triggered by a discovery made two days earlier. On October 21, the PHP Foundation disclosed two serious vulnerabilities in its software, catalogued as CVE-2026-109618 and CVE-2026-109619 and nicknamed "PHP2Shell." They exist in PHP's core engine, not in the code of any particular website. The Common Vulnerability Scoring System (CVSS) rates them at around 9.2 out of 10 for severity because they allow an unauthenticated outsider—someone without a password or an account—to execute commands on a vulnerable server. From there, an attacker could steal data, alter records or take control of the machine. CVSS is a widely used open standard that cybersecurity professionals and institutions rely on to measure software vulnerabilities.
The identified flaws are memory-handling errors, a type of subtle bug that can remain undetected in code for years. Researchers at Wiz, a New York-based cybersecurity firm that uses AI and cloud analysis to detect software risks, reportedly discovered the vulnerabilities with the help of AI tools and privately reported them to the PHP team in August. This is how responsible disclosure is supposed to work: the finder quietly informs the maintainers, a fix is prepared, and the vulnerabilities are publicly disclosed once a patch is available.
However, that process was disrupted. Details leaked a day or two before the planned announcement. Security firms reported detecting attack traffic even before the fixes were released.
Two-day Huawei Digital Nepal Conclave 2022
How it reached Nepal's government
Nepal's authorities learned about the vulnerabilities through the public disclosure and warnings that circulated ahead of it. Engineers at the National Cyber Security Center (NCSC) responded promptly to the situation, taking systems offline as soon as the threat became known. The NCSC issued an advisory the following day, naming a focal person and directing agencies to update their systems.
The scale of the shutdown has a simple explanation. Concentrating digital services on a single platform can itself become a source of vulnerability. Thousands of government websites run on a shared platform. The government therefore chose to take them offline centrally, apply patches and restore them together. No unauthorised access or cyberattack has been detected, suggesting that the precautionary approach worked.
The bigger problem is the age of the software. PHP versions 8.1 and older no longer receive official security updates. Systems built on these versions cannot simply be patched; they must be upgraded. Officials admit that many older systems have never undergone source-code audits. This leaves Nepal's government websites vulnerable to attackers. Hackers have disrupted services at certain government departments in the past, while banking frauds have also occurred. Patching closes this particular security gap, but it cannot reveal what else may have been lurking alongside it. The timing during the holidays reduced the impact on the public, but it also slowed efforts to locate documentation and hosting details.
How technology can address the problem
No software is free of bugs, so the real question is how quickly and effectively a system can recover. Several defensive measures are worth understanding.
The first and most immediate step is to patch the vulnerability and restart the affected systems. The fixed releases—PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35—are available precisely for this purpose.
Agencies that cannot patch immediately for various reasons are advised to disconnect vulnerable systems from the internet. Web application firewalls can filter known attack patterns while patches are being prepared. Running services with minimal privileges also limits what an intruder can do, even after gaining access. These are critical precautions.
It is equally important to know which programs are running and whether they are up to date. Maintaining an updated inventory of systems and software versions is the unglamorous foundation of effective cybersecurity. Nepal's shared-platform approach made a centralised response possible, but it also exposed how much time can be lost when documentation is missing. Having identified the problem as a first responder, the NCSC can also play a key role in helping agencies prepare and maintain such inventories.
In this instance, researchers discovered the vulnerabilities before attackers could exploit them. The same AI tools that helped uncover these flaws can also assist defenders, and significant research is already underway in this area. Automated code analysis, fuzz testing and regular source-code audits are becoming essential. They are increasingly necessary to keep pace with attackers who are using similar tools.
Over the longer term, the industry is moving critical components towards memory-safe programming languages, which eliminate entire categories of vulnerabilities associated with memory management. This is a decade-long undertaking, but it offers a more fundamental solution.
What Nepal should do next
The shutdown should be treated as a successful preparedness drill. For cybersecurity researchers and policymakers, three lessons stand out. First, retire unsupported software altogether. Running PHP versions that no longer receive security updates is an open invitation to hackers. Second, make security audits routine rather than reactive, so that the next vulnerability disclosure does not expose systems that nobody has examined. Third, build the capacity to respond during holidays and weekends because attackers do not observe festivals.
Banks, ministries and government agencies should also maintain tested contingency plans to ensure the continuity of essential services, such as cargo clearance and payments, while their systems are offline. The public deserves clear communication about what happened, which services were affected and when they will be restored. The central bank's notice handled this aspect relatively well.
Although PHP still powers a large majority of websites, modern infrastructure is increasingly adopting alternatives such as Node.js, Python and Go, while critical systems are also moving towards memory-safe languages such as Rust to prevent low-level vulnerabilities before they reach production. Nepal's government digital services must embrace modern technological solutions rather than continue relying on outdated systems and repeatedly patching their vulnerabilities.
The systems went offline briefly this time, and that was the responsible choice. The real test of a digital nation is whether it is prepared for the next such incident.
(The author is a computer engineering student at CV Raman Global University, India, and has conducted research on emerging patterns in cybersecurity.)