# שקיפות רבה יותר לגבי חומרת בעיות אבטחה

**URL:** <https://meta.discourse.org/t/greater-transparency-over-severity-of-security-issues/185241>\
**Category:** Product Support\
**Created:** [2 באפריל,‏ 2021,‏ 12:34pm UTC](https://meta.discourse.org/t/greater-transparency-over-severity-of-security-issues/185241 "2021-04-02T12:34:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**Post date:** [2 באפריל,‏ 2021,‏ 2:55pm UTC](https://meta.discourse.org/t/greater-transparency-over-severity-of-security-issues/185241/2 "2021-04-02T14:55:07Z")

</div>

Hey @core,

The security fix info is intentionally non-detailed. Sites upgrade at different speeds, while we want to share that there was a security fix, we don’t want to provide detail to allow malicious actors to easily exploit it. The security fix is the commit message, so you can always look at [our GitHub repo](https://github.com/discourse/discourse/search?o=desc&q=SECURITY&s=committer-date&type=Commits) for security commits to see the code changes if you like.

> [@core](#):
>
> Ideally the release would include a link to the HackerOne report

We do not make our HackerOne reports public. While we previously allowed hackers to request disclosure of their reports, due to abuse received after doing so on multiple occasions we discontinued that.

---

_[View the full topic](https://meta.discourse.org/t/greater-transparency-over-severity-of-security-issues/185241)._
