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

Vodafone Oman

Bug bounty on HackerOne vodafone.om

Accepting reports Full safe harbor
Go to program Website
Top reward
$10,000
Top severity paid
Critical
Assets in scope
7
Public CVEs
2
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $10,000
for critical bugs.
Report on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

Severity Reward
Critical $10,000 from $6,000
High $5,000 from $3,000
Medium $1,500 from $1,000
Low $500 from $300
Response
Within 5 days | First Response | 5 days |
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

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

Scope

7 assets you may test.

Web 5

  • apix.vodafone.om Critical
  • vfo01.vodafone.om Critical
  • vfo02.vodafone.om Critical
  • vfo03.vodafone.om Critical
  • www.vodafone.om Critical

Android apps 1

  • om.vodafone.mva Critical

iOS apps 1

  • 1589071345 Critical

Rules

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

While testing

  • Do submit your reports in English
  • Do provide Proof-of-Concept or sufficient information to enable reproduction of the vulnerability, so that it can be verified, reproduced, and possible remedies identified.
  • Do not abuse the vulnerability by causing disruption through your actions.
  • Do not share information about the vulnerability with others until it has been resolved.
  • Do submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • 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.
  • Please set a custom header or user agent on every single request that you send.
  • Please append your user agent header value with “h1.replace-with-your-hackerone-username”

Not accepted

  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Attacks requiring MITM or physical access to a user’s device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices in SSL/TLS configuration.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or brute force issues on non-authentication endpoints
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Vulnerabilities only affecting users of outdated or unpatched browsers
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Tabnabbing
  • Open redirect – unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction
  • Static resources / public information “exposed”
  • Leaked credentials.
  • Cache poisoning
  • Physical attacks towards any Vodafone property
  • CORS Vulnerabilities (cross-origin resource sharing)
  • Identical vulnerability but on a different asset (code-base is shared between multiple subdomains)
  • Vulnerabilities affecting end users such as Reflected XSS

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

Changes

Tracked since 11 Nov 2026. Last checked 3 minutes 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
CVESeverityPublished
CVE-2014-6891 Medium 5.4 11 Oct 2014
CVE-2014-5932 Medium 5.4 18 Sep 2014

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.

Vodafone Oman looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

Response Targets

Vodafone Oman will make a best effort to meet the following SLAs for hackers participating in our program:

Type of Response SLA in business days
First Response 5 days
Time to Triage 10 days
Time to Bounty 30 days
Time to Resolution depends on severity and complexity

Disclosure Policy

  • As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from Vodafone Oman.
  • Follow Vodafone Oman disclosure guidelines.

Program Rules

  • Do submit your reports in English
  • Do exercise caution and restraint with regard to personal data and do not intentionally engage in attacks against third parties, social engineering, denial-of-service attacks, physical attacks on any Vodafone property or spamming or otherwise causing a nuisance to other users.
  • Do provide Proof-of-Concept or sufficient information to enable reproduction of the vulnerability, so that it can be verified, reproduced, and possible remedies identified. Generally, identification of the vulnerable target, a description of the vulnerability and operations carried out to exploit the vulnerability are sufficient, but more details and information might be required in the case of complex vulnerabilities.
  • Do not abuse the vulnerability by causing disruption through your actions.
  • Do not share information about the vulnerability with others until it has been resolved.
  • Do submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • 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.

Test Plan

  • Please set a custom header or user agent on every single request that you send. This will help Vodafone team identify that the activity is coming from a hacker on the program and ensure that your testing is not blocked or interrupted.
  • Please append your user agent header value with “h1.replace-with-your-hackerone-username”

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Attacks requiring MITM or physical access to a user’s device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices in SSL/TLS configuration.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or brute force issues on non-authentication endpoints
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Vulnerabilities only affecting users of outdated or unpatched browsers
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Tabnabbing
  • Open redirect – unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction
  • Static resources / public information “exposed”
  • Leaked credentials.
  • Cache poisoning
  • Physical attacks towards any Vodafone property
  • CORS Vulnerabilities (cross-origin resource sharing)
  • Identical vulnerability but on a different asset (code-base is shared between multiple subdomains)
  • Vulnerabilities affecting end users such as Reflected XSS

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Thank you for helping keep Vodafone Oman and our users safe!

If you have any questions please reach out to security(at)vodafone(dot)om