NASA VDP
By National Aeronautics and Space Administration Vulnerability disclosure program on Self-hosted nasa.gov
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 5
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report through their form
- bugcrowd.com/engagements/nasa-vdp
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
No compensation is available, other than NASA’s gratitude for your help in advancing the NASA Mission.
- Response
-
Within 3 days
We will acknowledge receipt of your report within three business days.
- Safe harbor
-
Full
NASA will not recommend or pursue legal action related to the research.
- Hall of fame
-
Yes
LORs are awarded exclusively for P1-P4 rated reports that have been validated, accepted, and confirmed as fixed.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
5 assets you may test, 3 excluded.
Domains 5
- globe.gov
- nasa.gov
- nsc.nasa.gov
- nspires.nasaprs.com
- usgeo.gov
Out of scope (3)
- NASA internal-only services
- non-federal systems from our vendors and contractors
- third-party services
Rules
What the policy asks of you, and the bug types it won't reward, quoted from NASA VDP's policy.
While testing
-
Avoid impacting the availability of production systems.
-
If a non‑production or public test environment is available, all testing must be performed exclusively in that environment.
-
Keep information about discovered vulnerabilities confidential for a reasonable time to allow NASA time to resolve the issue before making a public disclosure.
-
Only use exploits to the extent necessary to confirm the presence of a vulnerability.
-
Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or leverage the exploit to “pivot” to other systems.
-
NASA requests that researchers refrain from sharing vulnerability reports with others for 90 days following the submission of the initial report
Not accepted
-
Social engineering-based attacks (e.g., getting a user to click an attacker-controlled link).
-
Denial of Service, Rate Limiting, or Spamming issues (e.g., layer 7 DOS attacks, Slowloris, etc.).
-
Clickjacking on pages with no sensitive actions.
-
Any reports with the endpoint /wp-json/wp/v2/users
-
Any reports with the endpoint xmlrpc.php
-
Attacks requiring physical access to a user’s device
-
Previously known vulnerable libraries without a working proof of concept.
-
Content spoofing or text injection
-
Reports from automated tools or scans without accompanying demonstration of exploitability
-
Software version disclosure without accompanying demonstration of exploitability.
-
Use of a known-vulnerable library without evidence of exploitability.
-
Missing best practices. (Missing security headers, missing captcha, insecure certs)
-
Insecure SSL or TLS issues (e.g., ciphers, certificates, etc.).
-
Missing security headers (e.g., HTTP Strict-Transport-Security (HSTS), Content Security Policy (CSP), etc.) that do not lead directly to a vulnerability.
-
Presence of the “autocomplete” attribute on web forms.
-
Host header injections unless you can show how they can lead to stealing data
-
Insecure cookie settings for non-sensitive cookies.
-
Directory Listing
-
Vulnerabilities affecting users of outdated browsers or platforms.
-
Issues related to descriptive or verbose error messages.
-
Any other non-technical vulnerability testing
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.