National Science Foundation
By U.S. National Science Foundation Vulnerability disclosure program on Self-hosted nsf.gov
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 8
- 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 by email
- [email protected]
- 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
By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against the U.S. Government related to your submission.
- Response
-
Within 3 days
Researcher submissions are acknowledged within three business days of submission.
- Safe harbor
-
Full
NSF will not recommend or pursue legal action related to the research.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
8 assets you may test, 1 excluded.
Domains 4
- nsf.gov
- research.gov
- sac.gov
- usap.gov
Wildcard domains 4
- *.nsf.gov
- *.research.gov
- *.sac.gov
- *.usap.gov
Out of scope (1)
- systems from NSF vendors
Rules
What the policy asks of you, and the bug types it won't reward, quoted from National Science Foundation's policy.
While testing
-
Ensure test methods do not include unauthorized activities described below.
-
Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
-
Only use exploits to the extent necessary to confirm a vulnerability's presence.
-
Will not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to pivot to other systems.
-
Allow NSF 90 business days to resolve the issue before disclosing the vulnerability publicly.
-
Agree not to submit a high volume of low-quality reports.
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 6 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.