# Finding the Signal in the Vulnerability Noise | IFIN

**URL:** <https://ifin.network/t/finding-the-signal-in-the-vulnerability-noise-ifin/870>\
**Category:** General\
**Tags:** blog-post\
**Created:** [September 29, 2026, 6:27am UTC](https://ifin.network/t/finding-the-signal-in-the-vulnerability-noise-ifin/870 "2026-09-29T06:27:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chilly](https://ifin.network/user_avatar/ifin.network/chilly/32/114_2.png) [@chilly](https://ifin.network/u/chilly)\
**Post date:** [September 29, 2026, 6:27am UTC](https://ifin.network/t/finding-the-signal-in-the-vulnerability-noise-ifin/870/1 "2026-09-29T06:27:33Z")

</div>

by James "Chilly" Harshaw

As Artificial Intelligence-assisted vulnerability hunting has become more commonplace, we have seen a flood of new vulnerabilities across our feeds and attackers taking advantage of them. In fact, there were 48,000+ CVEs in 2025 alone with vulnerabilities rising to become the top initial access vector in the [Verizon 2026 DBIR report](https://www.verizon.com/business/resources/reports/dbir/). It can make the task of keeping up feel impossible and even encourage [dangerous attitudes](https://commons.erau.edu/cgi/viewcontent.cgi?article=1677&context=ijaaa) like resignation or impulsivity. Our human brains can only receive so much before they start tuning things out due to [alert fatigue](https://en.wikipedia.org/wiki/Alarm_fatigue). Are we approaching the "vulnerabilities that cried wolf" moment?

* * *
This is a companion discussion topic for the original entry at [https://ifin-intel.org/blog/vuln-flood/](https://ifin-intel.org/blog/vuln-flood/)

---

<div class="post-metadata">

**Author:** ![mttaggart](https://ifin.network/user_avatar/ifin.network/mttaggart/32/7_2.png) [@mttaggart](https://ifin.network/u/mttaggart)\
**Post date:** [September 29, 2026, 6:27am UTC](https://ifin.network/t/finding-the-signal-in-the-vulnerability-noise-ifin/870/2 "2026-09-29T06:27:57Z")

</div>

Listed on September 29, 2026, 6:27am UTC



---

<div class="post-metadata">

**Author:** ![Shecky](https://ifin.network/user_avatar/ifin.network/shecky/32/408_2.png) [@Shecky](https://ifin.network/u/Shecky)\
**Post date:** [September 29, 2026, 2:45pm UTC](https://ifin.network/t/finding-the-signal-in-the-vulnerability-noise-ifin/870/3 "2026-09-29T14:45:35Z")

</div>

I think we are beyond the vulnerabilities that cried wolf problem. It comes down to a couple things:

1. CVSS Score is used as a risk score. Management/Executives see/hear of a high CVSS score and automatically freak out about a patch. We need to set time to see what our actual risk is on it

2. Freaking out about items a company doesn’t have. This boils down to a poor inventory system to do a quick search if a company has software X or hardware Y and what version it is on. Inventory has always been an issue from a security standpoint and as far as vulns go, it is even worse.

So for #1 the obvious way to work it is to build a trust level with the Management/Execs on risk assessment for CVEs. The more they trust that we will give a proper assessment and take care of high priority issues fast the better.

#2 is obviously having a good Inventory management system complete with SBOMS that is searchable so we know what we are dealing with( this also helps with #1) .

-Shecky

---

<div class="post-metadata">

**Author:** ![ajn142](https://ifin.network/user_avatar/ifin.network/ajn142/32/1443_2.png) [@ajn142](https://ifin.network/u/ajn142)\
**Post date:** [September 29, 2026, 5:30pm UTC](https://ifin.network/t/finding-the-signal-in-the-vulnerability-noise-ifin/870/4 "2026-09-29T17:30:15Z")

</div>

I know some folks at work are considering the use of EPSS for prioritization rather than CVSS. I’m still personally on the fence, as I’ve seen stuff that was zero-day/straight to the KEV maintain a low EPSS score. That might accurately reflect the risk for any random case where the vulnerability is present, but it doesn’t necessarily match _our_ risk.

[Exploit Prediction Scoring System (EPSS)](https://www.first.org/epss/)
