{"resourceId":"wired-uk-government-code-flaws-claude-researcher-planning-inspectorate-20261110","versions":[{"version":"external-cae271e231a4798197f30637bee0329e6e0fe56438c3fb268b7490b9aaaa8660","resource":{"id":"wired-uk-government-code-flaws-claude-researcher-planning-inspectorate-20261110","title":"WIRED: researcher using consumer-grade Claude models found vulnerabilities in about two-thirds of 349 UK public-sector codebases; most were basic hygiene failures","organization":"WIRED (reporting on ControlPlane research)","sector":"Technology press","geography":"United Kingdom","publishedAt":"November 10, 2026","publicationDate":"2026-11-10","eventDate":null,"sourceName":"WIRED","sourceLabel":"Investigative technology report","sourceUrl":"https://www.wired.com/story/security-flaws-across-uk-government-sites-exposed-god-tier-information/","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["data-security","developers-agents","governance-procurement"],"finding":"WIRED reports that ControlPlane researcher Chris Nesbitt-Smith, using consumer-grade Claude Opus and Sonnet models on a laptop, found vulnerabilities in about two-thirds of 349 UK public-sector codebases across 33 organizations, including a Planning Inspectorate credential committed to GitHub that would have given broad SharePoint and OneDrive access. The Planning Inspectorate said its monitoring detected the activity, it fixed the issue within 20 minutes of the report and found no breach. The researcher says many issues could have been caught by a routine IT health check and warns that closing public repositories without fixing flaws is the worst outcome.","sledRelevance":"Interpretation: an independent account of how cheaply Claude-class models can audit public-sector code, and of agency responses. U.S. state, local and education agencies that publish code, or use contractors who do, should expect AI-assisted researchers and attackers to find credential leaks and access-control gaps, and should prepare disclosure handling rather than retreat from open code.","evidence":"Credible investigative reporting with agency responses and an independent industry comment (OpenUK); quantitative claims originate from the researcher.","architectureImplications":"Interpretation: credential hygiene (short-lived, least-privilege secrets; history scanning) matters more than the AI tool; deleting a secret from a branch does not revoke it.","governanceImplications":"Interpretation: policy debates about withdrawing open code (the NHS reportedly ordered a move away in May) should weigh the researcher's warning that mirrored repositories remain exposed.","securityPrivacyImplications":"Exposed Entra ID credential with broad permissions; access-control gaps in Department for Education services; Scottish Government portal flaw exposing administrative account information; all dealt with per WIRED.","caveats":"Journalistic account relying on the researcher and agency statements; numbers not independently verified; does not detail AI false positives. Cross-tagged state-government and local-government: report covers UK departments and notes local authorities publish code; lessons transfer to U.S. agencies publishing code.","streamIds":["anthropic","state-government","local-government"],"roles":{"sales":"Use this as an urgency signal about basics, not exotic AI threats. WIRED reports a researcher with consumer-grade Claude models found flaws in about two-thirds of 349 UK public codebases, mostly routine mistakes. For agency CISOs and open-source program leads, ask how secrets are rotated and how researcher reports are handled. Offer a code and credential hygiene assessment. Do not claim Claude creates new attack types or that closing repos removes risk.","engineering":"Engineering takeaways are concrete: scan full git history for secrets, revoke at the identity provider rather than deleting files, enforce least privilege on app registrations, and add access checks to request-ID endpoints. Consider running the same Claude-assisted review internally before outsiders do. Validate with a controlled scan of agency repositories and confirm monitoring would detect unauthorized credential use, as the Planning Inspectorate reports it did.","delivery":"Delivery would combine a repository and credential audit with a disclosure-response runbook: inventory public repos, scan history, rotate exposed secrets, fix access-control gaps, and test detection of credential misuse. Dependencies are identity-provider administration and vendor cooperation. Owner is the security office. Risks are long-lived credentials with broad permissions, slow vendor fixes, and policy pressure to close repositories without remediation. Acceptance would be a clean history scan plus a tested canary-credential alert."},"roleDetails":{"sales":{"customerProblem":"Agencies publishing code have exposed secrets and access-control gaps that AI-assisted researchers can now find cheaply.","stakeholders":["Agency CISO","Identity and access management lead","Open-source program office","Vendor management"],"discoveryQuestions":["When did you last scan repository history for secrets?","How are app registration permissions scoped?","Do you have a vulnerability disclosure policy?","Would you detect use of a leaked credential?"],"valueHypothesis":"A hygiene assessment could close common, high-impact exposures before outside researchers or attackers find them.","potentialEngagement":"A repository and credential hygiene assessment with a disclosure runbook.","unsupportedClaims":["That Claude enables novel attacks","That closing repositories removes exposure","Independent verification of all counts"]},"engineering":{"fit":"Applies to any agency or university with public code.","architectureIntegration":"Secret scanning in CI; identity provider rotation; access-control tests.","prerequisites":["Repository inventory","Identity provider admin access"],"constraints":["Researcher-reported numbers","UK context"],"security":"Least-privilege credentials, rotation on exposure, monitoring for misuse.","proofOfValue":["Run history scan on all public repos","Test detection of a canary credential","Verify access checks on request-ID endpoints"]},"delivery":{"work":"Audit repos and credentials and prepare disclosure response.","dependencies":["Identity team","Vendors","Code owners"],"ownership":"Agency security office.","skillsAdoption":"Developers trained on secret handling.","governanceCheckpoints":["Disclosure policy published","Credential rotation verified","Quarterly scan review"],"acceptanceCriteria":["Proposed: zero valid secrets in public repo history after remediation","Proposed: canary credential use detected within one hour"],"risks":["Long-lived broad credentials","Slow vendor fixes","Closing repos without fixes"]}},"retrievedAt":"2026-11-11T04:22:56Z","enrichedAt":"2026-11-11T04:32:28Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Not addressed in the source.","procurementImplications":"Interpretation: contracts with software vendors should require secret scanning and vulnerability disclosure handling for code published on the agency's behalf.","operatingModelImplications":"Interpretation: agency monitoring that detects researcher activity (as the Planning Inspectorate reports) is part of the response model.","sourceVerification":{"openedUrl":"https://www.wired.com/story/security-flaws-across-uk-government-sites-exposed-god-tier-information/","referenceExcerpt":"he used consumer-grade models on a laptop and that many of the issues could have been caught by a routine IT health check","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}