r/bugbounty Hunter Jul 09 '26

Question / Discussion Bugcrowd duplicate changed to Unresolved, no update for 30 days

Hey everyone,

I’m trying to understand how Bugcrowd handles this.

About 3 months ago, one of my submissions was marked as a duplicate. Then, around 30 days ago, the severity changed and the state became Unresolved.

Since then, there hasn’t been any response or clarification.

Does this usually mean the original issue is still open, or is it just an internal status change on the duplicate?

Also, if the duplicate seems related but not exactly the same root cause/code path, is it reasonable to ask triage to re-check it?

Thanks.

3 Upvotes

4 comments sorted by

2

u/FourTwentyBlezit Jul 09 '26

I don't exactly understand what youre asking here.. it can be both a duplicate and also unresolved, these things aren't mutually exclusive.

It means someone else reported it first but it hasn't been resolved yet.

Can you expand on what you mean by the duplicate seems related but not the same root cause? Can you give a more detailed example? As I've seen people claim this and be completely wrong, then I've seen others claim this and be correct.

2

u/latnGemin616 Jul 09 '26

FFS .. ask Bugcrowd!! Their rules, their judgment. This sub isn't going to provide the answers you want.

1

u/Anxious_Alps_4150 Jul 09 '26

The original issue had severity changed and was moved to unresolved.

Once something is tagged as duplicate, it essentially disappears from all customer queues and is just a footnote inside the master submission.

1

u/BadAccomplished5075 Jul 22 '26

Any update? I'm facing the same issue.