UK government guidance keeps publicly funded code open by default, with justified exceptions and security controls. WIRED reported on November 10, 2026, that ControlPlane researcher Chris Nesbitt-Smith found more than 100 vulnerabilities in public UK government code, including exposed credentials at the Planning Inspectorate.
Public code can stay open only when teams also protect secrets, maintain services and fix vulnerabilities promptly.
What the reported scan found
Nesbitt-Smith reported vulnerabilities in around two-thirds of 349 public-sector codebases across 33 organizations, according to WIRED. He said he used Claude Opus and Sonnet models on a laptop. WIRED also described findings involving Department of Education services, an England register of government-funded training providers and apprenticeships, and a Scottish Government open-data portal.
What the Planning Inspectorate credentials could have exposed
The most serious example involved login credentials accidentally committed to a public GitHub repository and not fully removed. Nesbitt-Smith said they could have enabled broad read-and-write access to SharePoint sites and employees’ OneDrive accounts, including HR records and evidence libraries used in planning inquiries and appeals.
The Planning Inspectorate said it detected Nesbitt-Smith’s activity, fixed the vulnerability within 20 minutes of ControlPlane’s report and verified that no data breach had occurred. The credentials’ potential permissions and the agency’s account of the outcome are distinct: the researcher described what access they could have enabled, while the agency said no breach took place.
Why UK guidance keeps public code open
The UK government’s guidance on AI, open code and vulnerability risk says publicly funded code should remain open by default, with narrow, justified exceptions. The guidance says publishing code can modestly speed up analysis, but does not create the weaknesses in a system. Its focus is on how services are built, maintained and secured.
For public systems, the guidance calls for:
- An accountable owner and a maintenance plan.
- A route for reporting vulnerabilities.
- Keeping secrets and materially sensitive operational details out of public repositories.
- Secure-by-design practices and automated scans for dependencies, vulnerabilities and exposed secrets.
- Agreed timelines for security fixes, plus a safe plan for code that is no longer maintained.
The reported credential exposure illustrates why removing secrets and maintaining operational controls matter alongside decisions about code visibility.