Published finding · Bugcrowd

Atlassian A finding accepted against Jira Service Management Cloud (bugbounty-test-<bugcrowd-name>.atlassian.net). Bugcrowd published no award figure for it.

low unresolved

01 · The record

Everything Bugcrowd published about this

Programme: Atlassian In our directory, so it has reviews and a grade.
Platform handle: atlassian
Asset: Jira Service Management Cloud (bugbounty-test-<bugcrowd-name>.atlassian.net) 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: Not published This does not mean nothing was paid. Both platforms let a programme accept a finding without publishing the figure, and most do.
Found by: MRA14 Named because the finder allowed the platform to name them.
State: unresolved — accepted, not yet fixed
Accepted: 19 August 2026 1 month ago. This is the date the programme accepted the finding.
First seen here: 19 August 2026 When our sweep first read this entry. It says nothing about the finding, only about us.
Platform reference: 17136e54-5e85-4249-8113-4800bdbd315b

View the programme 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 programme. Everything Bugcrowd did publish about it is already above.

03 · The finder

What else MRA14 has published on Bugcrowd

9published findings

1programme

0critical

not setpublished awards

Atlassian medium · Jira Service Management Cloud (bugbounty-test-<bugcrowd-name>.atlassian.net) · today —
Atlassian low · Any associated *.atlassian.com or *.atl-paas.net domain that can be exploited DIRECTLY from the *.atlassian.net instance · 2 months ago —
Atlassian medium · Jira Software Cloud (bugbounty-test-<bugcrowd-name>.atlassian.net) · 3 months ago —
Atlassian medium · Jira Service Management Cloud (bugbounty-test-<bugcrowd-name>.atlassian.net) · 3 months ago —
Atlassian medium · Any associated *.atlassian.com or *.atl-paas.net domain that can be exploited DIRECTLY from the *.atlassian.net instance · 3 months ago —
Atlassian medium · Jira Software Cloud (bugbounty-test-<bugcrowd-name>.atlassian.net) · 3 months ago —
Atlassian low · Jira Software Cloud (bugbounty-test-<bugcrowd-name>.atlassian.net) · 3 months ago —
Atlassian medium · Jira Product Discovery · 6 months ago —

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 programme

What else Atlassian has published

Jira Service Management Cloud (bugbounty-test-<bugcrowd-name>.atlassian.net) medium · unresolved · MRA14 · today —
Bamboo medium · unresolved · Badai · yesterday $175
Jira Service Management Cloud (bugbounty-test-<bugcrowd-name>.atlassian.net) medium · unresolved · 0xJad · yesterday —
Bamboo high · unresolved · withheld · yesterday —
Bamboo critical · unresolved · withheld · 2 days ago —
Confluence Data Center high · unresolved · optional_ · 3 days ago —
Confluence Data Center medium · unresolved · withheld · 7 days ago —
Any associated *.atlassian.com or *.atl-paas.net domain that can be exploited DIRECTLY from the *.atlassian.net instance medium · unresolved · withheld · 7 days ago —

See Atlassian'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 programme did not pay.