Lead – A security researcher has identified more than 100 serious vulnerabilities in publicly‑available codebases used by UK government departments, exposing the risk of unauthorized access to sensitive information. The flaws were discovered using consumer‑grade AI models on a laptop, and the most severe case involved the Planning Inspectorate’s accidental publication of credentials that could grant “god‑tier” read‑write access to internal systems.
Background – According to Wired, the UK government has, for roughly a decade, defaulted to publishing the source code it develops with public money. The policy is intended to promote transparency, enable reuse across agencies, and reduce costs. Departments that have embraced this approach include the Department of Health and Social Care, the Home Office, and numerous local authorities.
Funding pressures and maintenance gaps – As reported by Wired, recent funding squeezes have left many departments unable to keep their technology estates up to date. The lack of resources, the article notes, has resulted in neglected maintenance and limited improvement of the publicly released code.
Research methodology – ControlPlane security researcher Chris Nesbitt‑Smith conducted the audit using Claude’s Opus and Sonnet AI models. He performed the scans on a standard laptop with consumer‑grade AI tools, according to Wired. Nesbitt‑Smith said many of the identified issues could have been caught by a routine IT health check and described the flaws as “daft stuff,” emphasizing that they do not represent the sophisticated attacks often highlighted in the media.
Most critical finding: Planning Inspectorate – The most alarming vulnerability, Wired reports, was found in the Planning Inspectorate, the agency responsible for land‑use decisions across England. The inspectorate had inadvertently committed a login credential to a public GitHub repository and failed to fully remove it. The exposed Microsoft Entra ID would have provided “god‑tier” read‑write access to all SharePoint sites, private employee OneDrive accounts, HR records, and sensitive libraries that hold evidence under legal hold for statutory planning inquiries and appeals. Nesbitt‑Smith warned that the situation “made it particularly dangerous” and that the agency could have faced ransomware, data theft, or widespread encryption.
Agency response – A spokesperson for the Planning Inspectorate told Wired that its cyber‑monitoring tools detected the researcher’s activity in August and that the incident was already being handled as a cyber incident when ControlPlane made contact. The agency reportedly fixed the vulnerability within 20 minutes of the report, verified that no data breach occurred, and subsequently reviewed and strengthened its systems and processes. The spokesperson expressed gratitude to the researcher for alerting them.
Industry perspective – Amanda Brock, chief executive officer of the nonprofit industry group OpenUK, commented to Wired that the Planning Inspectorate issue “isn’t about open source but internal housekeeping when using public tools.” She added that the exposure resulted from a failure to follow good processes rather than an inherent open‑source security problem.
Scope of the audit – According to Wired, Nesbitt‑Smith scanned 349 public‑sector codebases across 33 organisations. He found vulnerabilities in roughly two‑thirds of those repositories. Notable examples include:
- The Department of Education’s procurement service used by schools.
- A teacher‑application service that stores personal details, qualifications, employment history, and identity documents.
- England’s central register of government‑funded training providers and apprenticeships.
- A Scottish Government open‑data portal that would have allowed any visitor to read administrative account information and alter site configuration.
Debate over open‑source publishing – The findings have reignited arguments about whether public‑sector departments should continue publishing source code openly, especially as AI‑driven tools accelerate vulnerability discovery. Wired notes that the NHS reportedly ordered its technology teams to transition away from open‑source code in May, citing security concerns related to AI models.
Potential risks of code removal without remediation – Nesbitt‑Smith cautioned, as reported by Wired, that simply removing public repositories without first fixing the underlying flaws could be the “worst case scenario.” He explained that doing so would prevent researchers from discovering problems while adversaries may have already mirrored the repositories, preserving their access. “Unless you’re going to go and fix all of the problems, if anything, you’re probably drawing more attention to it by closing it,” he said, likening the situation to “Here be dragons over this space. Don’t look here though, please.”
Analysis (opinion) – The audit underscores a tension between transparency and security. While open‑source publishing can foster collaboration and cost savings, the lack of dedicated resources for ongoing code maintenance creates a fertile ground for exploitable weaknesses. As AI tools lower the barrier for vulnerability discovery, government bodies may need to reassess their open‑source strategies, balancing public accountability with robust cyber‑hygiene practices.
Conclusion – The discovery of over a hundred critical vulnerabilities across UK government codebases highlights systemic challenges in maintaining secure open‑source assets under fiscal constraints. Prompt remediation by the Planning Inspectorate demonstrates that rapid response can mitigate potential damage, but the broader issue of sustained code stewardship remains. Ongoing dialogue between policymakers, security experts, and open‑source advocates will be essential to ensure that transparency does not come at the expense of national cyber resilience.
Source: Wired
Frequently Asked Questions
How many vulnerabilities did the researcher find in UK government code?**
The researcher identified more than 100 serious vulnerabilities across publicly available UK government codebases. **Q: Which agency had the most severe exposure, and what could the compromised credentials access?** A: The Planning Inspectorate had the most severe exposure; the leaked Microsoft Entra ID could grant read‑write access to all SharePoint sites, private employee OneDrive accounts, HR records, and evidence libraries under legal hold. **Q: What was the government’s response to the Planning Inspectorate vulnerability?** A: The Planning Inspectorate detected the activity in August, fixed the vulnerability within 20 minutes of being notified, confirmed no data breach occurred, and strengthened its systems and processes.