Published finding, Bugcrowd

$100 awarded on Aiven Managed Bug Bounty, against github.com/Aiven-Open.

low paid unresolved

The record

Everything Bugcrowd published about this

Program: Aiven Managed Bug Bounty In our directory, so it has reviews and a grade.
Platform handle: aiven-mbb-og
Asset: github.com/Aiven-Open The specific asset the finding landed against, as the platform named it.
Severity: low Bugcrowd rates P1–P5; this is that rating in HackerOne's words so the two feeds can sit in one table.
Award: $100 What the platform printed. Where a report carried more than one payment they are summed.
Found by: ucuping Named because the finder allowed the platform to name them.
State: unresolved: accepted, not yet fixed
Accepted: 6 October 2026 1 month ago. This is the date the program accepted the finding.
First seen here: 6 October 2026 When our sweep first read this entry. It says nothing about the finding, only about us.
Platform reference: 8ff6ffb8-3400-4c44-aa95-54685fa8966d

View the program on Bugcrowd ↗ Bugcrowd publishes the acceptance, not the submission. There is no public write-up for this finding anywhere, and no page for the entry itself, so this link goes to the program. Everything Bugcrowd did publish about it is already above.

Is this figure normal

Where this award sits

A single large number tells you nothing on its own. What matters is whether this program pays like this routinely or whether this was the one time it did.

#14 of 15 here

$825 this program's median

$15,000 its largest published

#1,636 of 1,879 awards we hold

It is the 14th largest of 15 awards this program has published. It sits below this program's median, so larger figures are routine here.

Every figure here is drawn only from awards a platform chose to publish, which is a minority of what gets paid. Read the median as "of the payouts made public", never as "what this program pays".

The finder

The only finding we hold from ucuping

This is the only published finding we hold from ucuping on Bugcrowd. That is a statement about our coverage, not about their record: we read a few pages of each feed per sweep, and most accepted work is never published at all.

Counted within Bugcrowd only. The same handle on another platform may or may not be the same person, and this page will not assume it is.

04, The program

What else Aiven Managed Bug Bounty has published

Aiven for Clickhouse high , unresolved , withheld, 3 days ago –
Third-party dependency versions critical , unresolved , withheld, 3 days ago –
Third-party dependency versions critical , unresolved , pseudmous, 15 days ago $1,000
github.com/Aiven-Open low , unresolved , oxidus_dods, 16 days ago –
Aiven for Clickhouse low , unresolved , Kuroo, 22 days ago –
api.aiven.io medium , unresolved , Kuroo, 25 days ago –
Third-party dependency versions critical , unresolved , withheld, 30 days ago –
Aiven for Clickhouse low , unresolved , marius_dp, 1 month ago $825

See Aiven Managed Bug Bounty's grade and researcher reviews

Where this came from. One row of a public platform feed, stored as published and never edited. We hold no report title, no write-up and no reproduction steps, because the feeds do not carry them and we do not go looking for them. A withheld name stays withheld; if a finder later asks the platform to un-name them, the next sweep un-names them here. Absence of an award figure is publication policy, not evidence a program did not pay.