Skip to content

Bug bounty program

Platform
HackerOne
Bounties
None
Assets in scope
4
Disclosed reports
31
Subdomains
49
RubyGems: its disclosed reports by weakness, then what it has in scope.Drag to move · Ctrl + scroll to zoom · a strip opens those reports

Most upvoted reports31

All reports
Most upvoted reports of RubyGems
ReportWeaknessDisclosedBountyVotes
Host Header AttacAnalysed#2627221No weakness recorded–74
Remote code execution on rubygems.orgAnalysed#274990Deserialization and Object Injection$1,50051
`/names.nsf` and all `/names*` files route to public API on rubygems.org#3097900Access Control–46
Server-side ReDoS via user-controlled regex in OIDC Access PolicyAnalysed#3542546Denial of Service–41
Unpacker improperly validates symlinks, allowing gems writes to arbitrary locationsAnalysed#270072File and Path Handling–35
Delete directory using symlink when decompressing tarAnalysed#317321File and Path Handling$50035
Memory leak in gem decode logic can allow attacker to take down Rubygems.org applicationAnalysed#3079931Denial of Service–33
Bundler's RCE with response using MarshalAnalysed#1119120Deserialization and Object Injection–28
An organization admin can create an attacker-controlled organization owner via the gem transfer flowAnalysed#3938927Access Control–27
DNS SRV lookup of file:// sources enables local hijacking of gemsAnalysed#411519File and Path Handling$50022

Subdomains49

Subdomains of RubyGems
NameScopeFirst seen
admin.rubygems.orgadminNot in the scope
api.rubygems.orgapiNot in the scope
au-m.rubygems.orgNot in the scope
aws-eu-cache01.rubygems.orgNot in the scope
bb-m.rubygems.orgNot in the scope
blog.rubygems.orgListed out of scope
bundler.rubygems.orgNot in the scope
production.cf.rubygems.orgNot in the scope
chef.rubygems.orgNot in the scope
monitoring01.common.rubygems.orgmonitoringNot in the scope
dev.rubygems.orgdevNot in the scope
dev-origin.rubygems.orgdevNot in the scope
docgem.rubygems.orgNot in the scope
docs.rubygems.orgNot in the scope
fastly.rubygems.orgNot in the scope
guides.rubygems.orgNot in the scope
help.rubygems.orgListed out of scope
index.rubygems.orgNot in the scope
m.rubygems.orgNot in the scope
mail.rubygems.orgmailNot in the scope
o1.mailer.rubygems.orgNot in the scope
cachefly.mirrors.rubygems.orgNot in the scope
monitoring.rubygems.orgmonitoringNot in the scope
oidc-api-token.rubygems.orgapi, authNot in the scope
oidc-api-token-origin.rubygems.orgapi, authNot in the scope
oidc-api-tokens.rubygems.orgapi, authNot in the scope
oidc-api-tokens-origin.rubygems.orgapi, authNot in the scope
origin.rubygems.orgNot in the scope
production-origin.rubygems.orgNot in the scope
lb03.production.rubygems.orgNot in the scope
rdf.rubygems.orgNot in the scope
production.s3.rubygems.orgdataNot in the scope
oregon.production.s3.rubygems.orgdataNot in the scope
shipit.rubygems.orgIn scope
staging.rubygems.orgstagingNot in the scope
staging-origin.rubygems.orgstagingNot in the scope
lb01.staging.rubygems.orgstagingNot in the scope
stats.rubygems.orgListed out of scope
status.rubygems.orgmonitoringListed out of scope
support.rubygems.orgListed out of scope
test.rubygems.orgtestNot in the scope
test2.rubygems.orgtestNot in the scope
test3.rubygems.orgtestNot in the scope
tokyo-m.rubygems.orgNot in the scope
uptime.rubygems.orgListed out of scope
webauthn-review.rubygems.orgNot in the scope
webauthn-review-origin.rubygems.orgNot in the scope
www.rubygems.orgNot in the scope
your.rubygems.orgNot in the scope

1 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 20 Nov 2026.