Summary
CVE-2026-58437 describes an access-control weakness involving Git push options that can manipulate repository visibility. If an attacker can submit specially crafted push options with sufficient repository interaction privileges, the issue may cause repository access settings to change unexpectedly and expose restricted content.
Affected context
The vulnerability may occur in Git hosting or repository-management components that accept and process push options to control repository state or visibility. Risk depends on whether push options are exposed to users, whether visibility changes are insufficiently authorized, and whether repository policies permit the relevant operation.
Exploit preconditions
- Attack surface: Git push handling and server-side processing of push options
- Required access: An account or integration permitted to push to an affected repository or invoke the relevant repository operation
- Trigger point: Processing of a push request containing visibility-related options
- Why exploitation is possible: The server may apply a visibility change without adequately verifying that the requesting principal is authorized to modify repository access settings
Why this happens
The underlying issue is an authorization failure in the handling of Git push options. A repository-management component may treat client-controlled push metadata as sufficient authority to alter visibility instead of independently enforcing permissions for that sensitive operation. This behavior maps to CWE-284: Improper Access Control, where access restrictions are missing, incomplete, or incorrectly applied.
Potential impact
- A repository may become visible to users or groups that should not have access
- Sensitive source code, configuration, or development history could be disclosed
- Repository confidentiality controls could be weakened without administrator approval
- Attackers could use exposed repository data to support further compromise or supply-chain attacks
General mitigation guidance
Mitigation generally focuses on separating repository visibility changes from ordinary push permissions and enforcing authorization at the server-side operation boundary.
Common defensive patterns include:
- Treating push options as untrusted client input rather than an authorization grant
- Requiring explicit, independently evaluated permissions for visibility changes
- Applying secure-by-default private visibility and deny-by-default access policies
- Restricting repository-management privileges through least-privilege roles
- Recording and reviewing visibility changes with audit trails and administrative approval where appropriate
- Validating that integrations and automation identities cannot modify visibility unless explicitly required
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis and code review checks for authorization decisions based directly on push-option values
- Review of server-side handlers that mutate repository visibility during push processing
- Tests verifying that ordinary push permissions cannot implicitly grant repository-management privileges
- Policy enforcement requiring explicit authorization checks for confidentiality or access-control changes
- Audit monitoring for unexpected repository visibility transitions, especially when initiated by non-administrative identities
Neutral automated code-review and security-scanning tools may help identify missing authorization checks and unsafe trust boundaries.

