No technology is perfect, and pixiv believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you've found a security issue in our product or service, we encourage you to notify us. We welcome working with you to resolve the issue promptly.

Disclosure Policy

• Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.

• It is not permitted to publicly disclose reports without the express consent of pixiv's security team.

• 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.

Program Rules

While researching, we'd like to ask you to refrain from:

• Denial of service

• Spamming

• Social engineering (including phishing) of pixiv staff or contractors

• Any physical attempts against pixiv property or data centers

• Re-uploading other users' assets such as drawings and 3D models for testing of pixiv features

Out of Scope / Known Issues

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

• Hypothetical or theoretical vulnerabilities without actual verification code

• Insecure coding or design patterns without actual vulnerabilities

• Vulnerabilities with capability of brute force against password or tokens

• Password, email and account policies, such as email id verification, reset link expiration, password complexity

• Login/Logout CSRF

• CSRF on forms that are available to anonymous users (e.g. contact form)

• Vulnerabilities found in domains out-of-scope

• Vulnerabilities affecting outdated browsers or platforms

• Presence of autocomplete attribute on web forms

• Missing secure flags on non-sensitive cookies

• Reports of insecure SSL/TLS ciphers

• Vulnerabilities with capability of username/email enumeration

• Descriptive error messages (e.g. Stack traces, application or server errors)

• Banner disclosure on servers

• Misconfiguration of SPF record, DMARC and DKIM

• Lack of security headers without an actual attack scenario

• Phishing attack via registration email (e.g. making username a URL)

• Tabnabbing

• Disclosure of pixiv's numeric ID such as user ID and illustration ID (unless it compromises user privacy)

• Lack of rate limit

• Assets remaining visible on CDN after changing its visibility from public to private

• Manipulating number of views

• Insufficient session expiration

• Backup of app data

• Race conditions which do not involve privacy or monetary risk

• IDOR which do not involve privacy or monetary risk (e.g. bookmarking private contents while gaining no information about it)

• Lack of URL confirmation on outgoing links

• Broken link hijacking (social media account etc): You may submit a report for this issue and it will be resolved, but it will not be eligible for bounty

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 pixiv and our users safe!