Skip to content

Recreation.gov

Vulnerability disclosure program on HackerOne recreation.gov

Accepting reports
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
7
Public CVEs
0
Last change

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report on HackerOne
Submit through the program page.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

This program does not pay cash rewards.

Scope

7 assets you may test.

Web 5

  • cdn.recreation.gov Critical No bounty
  • manage-cdn.recreation.gov Critical No bounty
  • manage.recreation.gov Critical No bounty
  • recreation.gov Critical No bounty
  • www.recreation.gov Critical No bounty

Android apps 1

  • com.bah.r1smobile Critical No bounty

iOS apps 1

  • com.bah.r1s Critical No bounty

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Recreation.gov (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
  • Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only triage the first report received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
  • Social engineering (e.g., phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.

Not accepted

  • The following issues will be closed as invalid except in rare circumstances demonstrating clear security impact

Summarised with AI from the program policy on HackerOne, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 18 minutes ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope added

    cdn.recreation.gov

  2. Scope added

    com.bah.r1s

  3. Scope added

    com.bah.r1smobile

  4. Scope added

    manage-cdn.recreation.gov

  5. Scope added

    manage.recreation.gov

  6. Scope added

    recreation.gov

  7. Scope added

    www.recreation.gov

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Recreation.gov looks forward to working with the security community to find vulnerabilities in order to keep our visitors safe.

Disclosure Policy

  • Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program

Program Rules

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
  • Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only triage the first report received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
  • Social engineering (e.g., phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.

Core Ineligible Findings

When reporting potential vulnerabilities, please consider (1) realistic attack scenarios, and (2) the security impact of the behavior. Below, you will find the most common false positives we encounter. The following issues will be closed as invalid except in rare circumstances demonstrating clear security impact:

Check here for HackerOne’s Core Ineligible Findings

Thank you for helping keep Recreation.gov, our visitors, and the web safe!