Skip to content

The Texas A&M University System

Vulnerability disclosure program on security.txt tamus.edu

Accepting reports Full safe harbor security.txt expired
Top reward
No cash rewards
Top severity paid
Not published
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 by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
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 We do not directly reward bounties, award certificates, or provide documentary notifications to other parties for disclosing vulnerabilities, but certain vendor products may be bounty-eligible and you are encouraged to also report the vulnerability to the affected vendor(s).
Safe harbor
Full If you make a good faith effort to comply with this program policy during your security research, we will consider your research to be authorized and we will work with you to understand and resolve the issue quickly.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

7 assets you may test, 3 excluded.

Domains 6

  • agrilife.org
  • pvamu.edu
  • tamiu.edu
  • tamuc.edu
  • tamu.edu
  • tamus.edu

Products and areas 1

  • all internet-accessible systems or services that (1) do not require the use of a VPN or other gateway service to access, and (2) are under domains owned or operated by the Texas A&M University System
Out of scope (3)
  • any connected services not hosted by the Texas A&M University System
  • services which require access from within a Texas A&M University System member network
  • vulnerabilities found in systems from our vendors (to include cloud service (SaaS/PaaS/IaaS) providers)

Rules

What the policy asks of you, and the bug types it won't reward, quoted from The Texas A&M University System's policy. "We" in these lines means the program, not this site.

While testing

  • Notify us as soon as possible after you discover a real or potential security issue.
  • 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.
  • Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
  • Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Do not submit a high volume of low-quality reports.
  • Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
  • Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or 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 3 hours ago.

  1. Scope +

    Added to scope: agrilife.org

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.