Text of bounty.github.com › ineligible.html as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Ineligible submissions | GitHub Bug Bounty

Ineligible submissions There are a handful of reports that we consider ineligible, either because the feature is working as intended or we accept the low risk as a security/usability tradeoff: All Targets OAuth client ID and secrets are publicly available in desktop and mobile apps Use of known-vulnerable software Vulnerability in upstream dependencies Clickjacking a static site Local Access Network Denial of Service Cache purging and cache eviction Content that stays cached after you delete it or make it private Git hooks, filters, and local repository configuration Attacks that require following an attacker's instructions Typosquatting Vulnerabilities identified in Open Source Repositories Assets that are not owned by GitHub Abuse of a service is not automatically a vulnerability Attacks that require intercepting or modifying traffic Dependabot Arbitrary code execution in dependency update jobs Showing code execution without showing the escape What Dependabot does with the repository it runs against Vulnerabilities in the packages themselves GitHub Gist Secret gists are accessible via URL without authentication Gist content rendered on githubusercontent.com Links and redirects in gist content Forks, revisions, and deletion GitHub Actions Steps within a job are not security boundaries Artifact upload and download paths Code Execution in Actions Bypassing build log secret redaction General abuse or exhaustion of resources Availability of resources inside a workflow run Access to build artifacts without user session GitHub API Write access to a repository includes configuring its secrets Data from public repositories returned by the API Repository and organization metadata Functionality disabled in the UI but reachable through the API Email addresses returned by the API GitHub CLI Anything that needs local access first Extensions, aliases, and anything you install Tokens sent to the host you configured Cloning or checking out an untrusted repository GitHub Codespaces Devcontainer configuration and the codespace token API scopes are not a second set of permissions Resource consumption within a user's own codespace Access to metadata services from within a codespace Vulnerabilities in third-party software within a codespace Privileged access within a user's own codespace GitHub Copilot Vulnerabilities in GitHub Copilot Chat extension and Inline Suggestions in Visual Studio Code Prompt Injections The security of code suggested by Copilot Tokens suggested by Copilot Prototype features Copilot quota, billing, and usage limits Changes you review and accept GitHub MCP Server Off topic conversation Copilot coding agent acting on a repository it was assigned to Who can assign the coding agent Agent output requires review GitHub Credentials Credentials which have been detected by GitHub Secret Scanning Credentials on GitHub Credentials you have not confirmed still work Values that are not secrets Secrets inside GitHub Actions GitHub Desktop Cloning a repository you do not trust Code execution that needs the user to be talked into it Anything that needs local access first The OAuth client identifier GitHub Enterprise Cloud Access that a role is supposed to grant Actions workflows behaving as configured IP allow lists and network controls Invitations, seats, and billing SSO redirects revealing that a resource exists Repository visibility policies, forks and transfers GitHub Enterprise Server Vulnerabilities caused by lack of subdomain isolation Escalation to the root user via sudo Access to sensitive configuration information with local access Bypassing source code de-obfuscation GitHub Mobile On-screen data is not hidden when backgrounding the app No jailbreak detection *.github.net Internal IP addresses and hostnames in public DNS Vulnerabilities in out-of-scope subdomains GitHub Pages Vulnerabilities in GitHub Pages hosted content Subdomain Takeover Code execution during your own build Domain verification and custom domains GitHub.com Including HTML in Markdown content Leaking email addresses via .patch links Phishing using Unicode homoglyphs, RTLO, or non-printable characters Email verification policy Email Invitations Impersonating a user through git email address DMARC, SPF and DKIM email policy Bypassing country restrictions for SMS two-factor authentication Vulnerabilities in repositories hosted on GitHub Host header injection Timing attacks which reveal a private repository or user 2FA does not invalidate existing sessions Enabling 2FA without a verified email Vulnerabilities caused by out-dated browsers Camo image proxy Lack of Sudo mode Community and safety bypasses that do not affect privacy Activity in archived repos Accessing certain disabled functionality Lack of rate limiting Email and Username Enumeration OAuth App Redirect Lack of Secret Scanning Alert Product bugs and input validation without a security impact Issue and pull request templates and prefilled query parameters Deploy keys and repository rulesets Impersonation through profile names and naming patterns *.githubapp.com Vulnerabilities in out-of-scope subdomains Subdomain takeovers that cannot actually be taken over Third party services hosted on the domain Content that is meant to be public *.githubusercontent.com User-content behavior without a CSP bypass Tokens in raw file URLs Attachments on private issues and pull requests Credentials found in user content npm CLI Project configuration in a repository you chose to run npm in Social engineering Local access Arbitrary code execution in commands that modify the package tree Upstream dependencies npm Registry Vulnerabilities in packages that are hosted on the registry Malicious packages Infrastructure vulnerabilities Timing attacks that reveal a private package Account takeover that depends on the victim acting Publicly available package and user data Organization invitations and membership changes Account ownership disputes Revoking a token you already know the identifier for All Targets OAuth client ID and secrets are publicly available in desktop and mobile apps It is expected that GitHub-owned clients, such as GitHub Mobile and GitHub CLI , include both the OAuth client ID and OAuth secret.

These are public clients, and a public client cannot hold a secret. Recovering one by unpacking an app, reading a binary, or watching traffic is not by itself a vulnerability, and a report that stops there is not eligible. A working chain that turns the secret into access to an account someone else owns is eligible, and we have rewarded reports of that kind. If you can intercept the OAuth callback from another application on the device and obtain a token for an account you do not control, we want to see it.

Tell us the platform and the exact redirect target you intercepted, because a custom URL scheme and a verified Universal Link or App Link do not give the same guarantees. Use of known-vulnerable software GitHub has a dedicated team responsible for tracking and remediating the use of known-vulnerable software. Submissions related to GitHub services using known-vulnerable software are only eligible 30 days after public disclosure of a vulnerability.

In addition, any submissions related to using known-vulnerable software must show evidence of exploitability. Simply demonstrating that GitHub is running a known vulnerable version is not sufficient, the submission must demonstrate an actual impact of exploitation like disclosing private data. Vulnerability in upstream dependencies Vulnerabilities that are due to a vulnerability in an upstream dependency are out of scope and should instead be disclosed to the upstream maintainers.

We may make exceptions for vulnerabilities that have a substantial impact to our production environment and customer data, however, issues should still be directed to the maintainers of the dependency upstream first. Clickjacking a static site Several GitHub owned sites are created using a static site generator and host

The rest of this page is on the live site.