**NOTE** This is an issue template to standardise our process for responding to and fixing critical security and privacy vulnerabilities, exploits, etc.
- [ ] Next scheduled alpha, then backport to stable
- [ ] Next major release
- [ ] Other (please explain)
#### Justification
<!-- Provide some paragraph here justifying the logic behind our estimated urgency -->
### Side-Effects: Who will be affected by a fix for this?
Sometimes fixes have side-effects: users lose their data, roadmaps need to be adjusted, services have to be upgraded, etc. Please enumerate the known downstream consequences a fix to this issue will likely incur.
- [ ] End-Users (please list)
- [ ] Internal Partners (please list)
- [ ] External Partners (please list)
## Todo:
### Communications
- [ ] Start an initial email thread with the following people:
- [ ] **bella**
- [ ] Relevant Applications Developers
- [ ] **(Optional)****micah**
- if there are considerations or asks outside the Applications Team
- [ ] **(Optional)** Other Team Leads
- if there are considerations or asks outside the Applications Team
- [ ] **(Optional)****gazebook**
- if there are consequences to the organisation or partners beyond a browser update, then a communication plan may be needed