Technology

UK Government Code Audit Uncovers Over 100 Critical Flaws, Including ‘God‑Tier’ Access

A researcher uncovered over 100 critical flaws in UK government code, including “god‑tier” access, prompting urgent calls for better cyber hygiene and a rethink of open‑source publishing.

S
SciTech Editorial Team
Newsroom
··1 min read
UK Government Code Audit Uncovers Over 100 Critical Flaws, Including ‘God‑Tier’ Access
A security researcher has uncovered more than 100 serious vulnerabilities in publicly available UK government code, exposing what he describes as “god‑tier” read‑write access to SharePoint sites and private OneDrive accounts. The findings, revealed by Chris Nesbitt‑Smith of ControlPlane, highlight an urgent need for better cyber hygiene across ministries that have long published their software openly. Using consumer‑grade large language models (LLMs) – Claude Opus and Sonnet – on a standard laptop, Nesbitt‑Smith scanned 349 codebases belonging to 33 public‑sector organisations. Roughly two‑thirds of the repositories contained at least one flaw. The most alarming case involved the Planning Inspectorate, which inadvertently committed login credentials to a public GitHub repository. The exposed Microsoft Entra ID would have granted unrestricted read and write rights to all SharePoint sites, employee OneDrive folders, HR records, and evidence libraries under legal hold. When the researcher reported the issue in August, the Planning Inspectorate’s monitoring tools detected the activity within minutes. The agency patched the vulnerability in just 20 minutes and confirmed that no data breach occurred. “We have reviewed and strengthened our systems and processes to prevent this type of issue recurring,” the spokesperson said, adding gratitude for the researcher’s disclosure. The episode fuels a growing debate about the wisdom of publishing government code openly. While transparency and reuse have been championed for a decade, funding squeezes have left many departments unable to maintain their technology estates. The NHS, for instance, ordered a shift away from open‑source components in May, citing AI‑driven vulnerability discovery as a key risk. Experts warn that withdrawing code without first fixing underlying flaws could be counter‑productive. “If you close the repository without remediation, you merely signal that something dangerous lies beneath,” Nesbitt‑Smith cautioned, noting that adversaries may have already cloned the repositories. The incident underscores the need for systematic code audits, automated AI‑assisted scanning, and robust governance before any decision to hide or expose source code is made.

Share

More from this section: Technology