Apple does not use a third-party platform. Reports go directly to Apple Security Research and are triaged by Apple's own engineers. There is no profile to claim here, by design.
Reports are judged on demonstrated, reproducible impact. A primitive on its own is usually closed; show the whole chain on current, shipping software.
Featured write-up
“Hunting on Apple requires patience, but verifying a successful fix makes the wait worthwhile. I reported a vulnerability on *.apple.com where a advance client-side response manipulation allowed a complete bypass of the authentication gate. Tracking the status took some proactive follow-up. While their initial response times can feel slug…”
Getting credit
Credit publishes in Apple’s own advisories, often months after the report. We index those, so it is waiting for you, including recognitions that carry no CVE and appear nowhere else.
Found a vulnerability?
Apple runs its own vulnerability reporting process. Here are your two ways to report it. We recommend the first.
Private. The report body is encrypted at rest; BugRater holds the key, so the analyst working it can read it. Every read is logged.
HackerOne’s own figures for this program, read from its public page, not reported by researchers and not part of the BugRater grade. Captured 24 Sep 2026.
What it pays, by severity
Intake & responsiveness · last 90 days
Getting in the door
Open to submit. Nothing HackerOne publishes stands between a hunter and a first report here.
Over 35 days (19 snapshots): no change on the figures worth watching.
No reviews yet.
Facts published by HackerOne on the program's own page, not reported by researchers, and not part of the BugRater grade. Last checked 20 Sep 2026.
Think different