Repository navigation
Dependabot update jobs now enforce an outbound domain allowlist #16392
v-abhishekbhaskar
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone! We wanted to share a security change we've been rolling out to Dependabot update jobs: a network egress allowlist that restricts where a job can connect, as a defense-in-depth measure against exfiltration of repository contents and registry credentials.
What's changing
Every Dependabot update job runs behind an HTTP/HTTPS proxy. We have added an egress allowlist to that proxy: outbound requests made during a job are checked against a list of known package-ecosystem hosts, and requests to hosts that are not on the list are blocked.
What this means for you
Most jobs are unaffected. The allowlist already covers the public registries, mirrors, CDNs and download hosts for the supported ecosystems, as well as GitHub's own infrastructure.
There are two cases that may need action:
A public registry or download host we've missed. These belong in the allowlist, which lives in
internal/handlers/egress_allowlist_defaults.yamlin thedependabot/proxyrepository. Contributions are welcome — please open a PR adding the host under the relevant ecosystem, with a short note on what it serves. The comment at the top of that file explains the matching rules; entries should be as specific as possible, and we generally don't accept wildcards over shared, multi-tenant domains.A private or organisation-specific registry. These should not be added to the defaults. Declare them using the
registries:key in yourdependabot.ymland reference them from the relevantupdates:entry. Registries configured this way are allowlisted automatically for that job, so no change to the proxy is required. See Configuring access to private registries for Dependabot.Rollout
We are enabling enforcement progressively rather than all at once, so that we can catch gaps in the allowlist before they affect everyone.
While the rollout is in progress, an update job may fail if it needs a host that isn't allowlisted yet. If that happens, the job logs will show which host was blocked. Please open a PR against
dependabot/proxyfor a public host, or check yourregistries:configuration for a private one — and feel free to report it in this repository if you're unsure which applies.Thanks for your patience while we tighten this up.
All reactions