vulns.co
/
GKData.io MCP and API Buy me a coffee

Wiz Research

GitHub internal metadata: preserve the boundary between user data and service authority

GitHub's backend treated user-controlled operation metadata as trusted configuration in downstream services. Wiz's CVE-2026-3854 research demonstrated code execution on Enterprise Server and hosted infrastructure. Cross-tenant content checks used Wiz's own accounts; wider repository exposure was an inferred capability, not demonstrated theft of customer content.

Open the referenceResearch PaperReviewed 2026-10-06

How to use this reference

Editorial lessons: preserve provenance when internal services exchange mixed-trust data, keep policy decisions independent of user-controlled metadata, and remove environment-inappropriate execution paths. GitHub confirms input sanitization and removal of unnecessary code paths as remediation. Review the vendor's maintained release guidance rather than treating a researcher version table as definitive.

Before reading

  • Familiarity with service-to-service trust boundaries
  • Basic authorization and serialization concepts

Context and limits

  • Technical precondition: an authenticated user needed repository push permission (vendor). Learning prerequisites above are editorial.
  • Wiz reports controlled cross-tenant validation with its own accounts and says it did not access other tenants' repository contents. GitHub's investigation attributes observed activity to the researchers and reports no customer-data access, modification or exfiltration.
  • Wiz dates reporting and hosted remediation to March 4, 2026, Enterprise Server patch release to March 10, and disclosure to April 28. GitHub corroborates hosted remediation on March 4; its article was updated April 29.
  • Remediation-version disagreement: Wiz lists 3.19.3 among fixed versions, while GitHub's updated guidance recommends 3.19.4 or later and newer patch levels across other branches. The difference is preserved rather than resolved by inference; no independent patch verification was performed.
  • Wiz's July 27, 2026 Atlas article (source: atlas-payment) identifies CVE-2026-3854 in its Results paragraph and reports that the bounty was paid out. This is researcher-reported payment, without independent vendor confirmation of settlement. The exact amount, currency and settlement date remain unknown; the superlative supplies no numerical amount or threshold. The award-report candidate remains excluded, and the April 28, 2026 technical publication date is unchanged.

Sources

  1. Securing GitHub: Wiz Research uncovers Remote Code Execution in GitHub.com and GitHub Enterprise Server (CVE-2026-3854)Wiz Research · reviewed 2026-10-03
  2. Securing the git push pipeline: Responding to a critical remote code execution vulnerabilityGitHub · reviewed 2026-10-03
  3. Atlas: Wiz's autonomous AI Agent for vulnerability research, ranked #1 on CyberGymWiz Research · reviewed 2026-10-06

Record reviewed 2026-10-06. Snapshot a066321c166a. Open the complete JSON contract.

Library synced 2026-11-19 · cases last reviewed 2026-10-05

a066321c166a · JSON exports & schemas · CC BY 4.0 content / MIT software