- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 2
- 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 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.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Pays cash
-
Yes
where it may be eligible for a bounty payment
- Response
-
Within 5 days
Time to Triage | 5 bussiness 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
2 assets you may test.
Wildcard domains 2
- *.pubg.com Critical No bounty
- *.pubgesports.com Critical No bounty
Rules
What the policy asks of you, and the bug types it won't reward, quoted from PUBG (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact
-
When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced)
-
Multiple vulnerabilities caused by one underlying issue will be treated as one valid report
-
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
-
Do not use a discovered vulnerability to view, delete, alter, or publish user data
-
Disclosure, leaking and publication of any personal information accessed is also prohibited
Not accepted
-
Exposing Session Tokens in URLs without proof of exploitability
-
Clickjacking on pages with no sensitive actions
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions (Include Login/Logout CSRF)
-
Script executions that do not affect Users
-
Attacks requiring MITM or physical access to a user's device
-
Using a rooted device
-
Previously known vulnerable libraries without a working Proof of Concept
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability
-
Unsafe SSL/TLS cipher suites or protocol version
-
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 bruteforce issues on non-authentication endpoints
-
Missing best practices in Content Security Policy
-
Missing security header(s)
-
Missing HttpOnly or Secure flags on cookies
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc)
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors, etc)
-
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis
-
Reporting vulnerabilities related to Tabnabbing
-
Open redirect - unless an additional security impact can be demonstrated
-
Issues that require unlikely user interaction
-
Exposure of API keys with no security impact
-
Information disclosure via Wordpress REST API (`/wp/v2/users`)
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 17 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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
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.
KRAFTON looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
──────────────────────────────────────────────────────────────────────────
Response Targets
KRAFTON will make a best effort to meet the following SLAs for hackers participating in our program:
| Type of Response | SLA in business days |
|---|---|
| Time to Triage | 5 bussiness days |
| Time to Issue resolved | depends on severity and complexity |
| We’ll try to keep you informed about our progress throughout the process. |
──────────────────────────────────────────────────────────────────────────
Disclosure Policy
- Follow HackerOne's disclosure guidelines
──────────────────────────────────────────────────────────────────────────
Program Rules
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact
- When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced)
- Multiple vulnerabilities caused by one underlying issue will be treated as one valid report
- 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
- Do not use a discovered vulnerability to view, delete, alter, or publish user data
- Disclosure, leaking and publication of any personal information accessed is also prohibited
──────────────────────────────────────────────────────────────────────────
Private Bounty Program
Reports involving the PUBG/KRAFTON game client and servers are handled under a separate private program. To be invited to the private program simply submit your game client/server related report here and we'll invite you to resubmit it to the private program where it may be eligible for a bounty payment.
──────────────────────────────────────────────────────────────────────────
Out of scope vulnerabilities
For "event pages" that are temporarily open within the site, only "critical" vulnerabilities are eligible for rewards.
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- The PUBG/KRAFTON game servers are currently outside the scope of this program
- Exposing Session Tokens in URLs without proof of exploitability
- Clickjacking on pages with no sensitive actions
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions (Include Login/Logout CSRF)
- Script executions that do not affect Users
- Attacks requiring MITM or physical access to a user's device
- Using a rooted device
- Previously known vulnerable libraries without a working Proof of Concept
- Comma Separated Values (CSV) injection without demonstrating a vulnerability
- Unsafe SSL/TLS cipher suites or protocol version
- 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 bruteforce issues on non-authentication endpoints
- Missing best practices in Content Security Policy
- Missing security header(s)
- Missing HttpOnly or Secure flags on cookies
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc)
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors, etc)
- Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis
- Reporting vulnerabilities related to Tabnabbing
- Open redirect - unless an additional security impact can be demonstrated
- Issues that require unlikely user interaction
- Exposure of API keys with no security impact
- Information disclosure via Wordpress REST API (
/wp/v2/users)
You may submit a report for below the issue and it will be resolved.
- Broken link hijacking (e.g. social media account, etc)
- Status monitoring page with no disclosure of sensitive data (e.g. apache server status and internal metrics, etc)
- Subdomain Takeover is subject to reward only for domains currently in operation If a Subdomain Takeover problem Occurs for an unused domain (or an unmanaged domain), it is not eligible for reward
- Vulnerabilities only affecting a single browser or a single version only
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
──────────────────────────────────────────────────────────────────────────
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. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep Krafton and our users safe!