Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Australia Post

Vulnerability disclosure program on Self-hosted auspost.com.au

Accepting reports Full safe harbor security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
1
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 Please note that we do not compensate individuals or organisations for identifying potential or confirmed security vulnerabilities.
Response
Within 3 days Once you have reported a potential security vulnerability, we will contact you within 72 hours with an initial response.
Safe harbor
Full To encourage responsible disclosure, we will not take legal action against security researchers in relation to the discovery and reporting of a potential security vulnerability.
Hall of fame
Yes We thank the following researchers who have helped keep our products and services safe by reporting security vulnerabilities responsibly in accordance with our Responsible Disclosure Program:

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

Scope

1 asset you may test.

Domains 1

  • auspost.com.au No bounty

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Australia Post's policy. "We" in these lines means the program, not this site.

While testing

  • Accessing or attempting to access accounts or data that does not belong to you
  • Any attempt to modify or destroy any data
  • Executing or attempting to execute a denial of service (DoS) attack
  • Sending or attempting to send unsolicited or unauthorised email, spam or any other form of unsolicited messages
  • Conducting social engineering (including phishing) of Australia Post Group employees, contractors or customers or any other party
  • Any physical attempts against our property or data centres, including (but not limited to) distribution facilities, post offices and post boxes
  • Posting, transmitting, uploading, linking to, sending or storing malware, viruses or similar harmful software that could impact our services, products or customers or any other party
  • Testing third party websites, applications or services that integrate with our services or products
  • The use of automated vulnerability scanners
  • Exfiltrating any data under any circumstances

Not accepted

  • Reports from automated vulnerability scanners
  • Descriptive error messages such as stack traces, application or server errors
  • HTTP 404 codes or pages, or other HTTP non-200 codes or pages
  • Fingerprinting or banner disclosure on common and public services
  • Disclosure of known public files or directories, such as robots.txt
  • Clickjacking and other issues only exploitable through clickjacking
  • CSRF on forms that are available to anonymous users, such as contact, login and logout forms
  • CSRF with minimal security implications
  • Content spoofing or text injection
  • Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality
  • Lack of Secure or HTTPOnly flags on non-sensitive cookies
  • Login or Forgot Password page brute force and account lockout not enforced
  • Enabled HTTP methods (such as OPTIONS, TRACE, DELETE, PUT, WEBDAV, etc.) without a valid attack scenario
  • Missing HTTP security headers, such as Strict Transport Security, X-Frame-Options, X-SSS-Protection, etc
  • Host header or CSV injection without a valid attack scenario
  • HTTP or DNS cache poisoning
  • Missing best practices in SSL/TLS configuration without a working proof of concept
  • Self-exploitation issues (such as self XSS, cookie reuse, self denial of service, etc.)
  • Issues related to mobile applications that require the host device to be either rooted or jailbroken
  • Issues related to brute forcing, rate limiting and other denial of service type attacks
  • Weak password policy implementation
  • Use of a known-vulnerable libraries or frameworks (e.g. outdated JQuery or AngularJS) without a valid attack scenario
  • Issues that rely on outdated or unpatched browsers and platforms to be abused

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.

Search NVD

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