Vulnerability Database

326,895

Total vulnerabilities in the database

Vulnerabilities for products matching "cacti"

Found 2 matching products. Filters apply to all results.

You can search for specific versions with /product/cacti/1.2.3

the_cacti_group / cacti

15 vulnerabilities found
Title Severity Exploit Date Affected Version
High June 7, 2007 6/7/07
<= 0.8.6i
Medium June 7, 2007 6/7/07
<= 0.8.6i
High December 28, 2006 12/28/06
<= 0.8.6i
High January 9, 2006 1/9/06
== 0.8.6g
High January 9, 2006 1/9/06
== 0.8.6g
High July 6, 2005 7/6/05
== 0.8.5
== 0.8.6b
== 0.8.6c
== 0.8.6a
== 0.8.2a
== 0.8.3a
== 0.8
== 0.8.5a
== 0.8.4
== 0.8.6
== 0.8.3
== 0.8.1
== 0.8.2
== 0.8.6d
== 0.8.6e
High July 6, 2005 7/6/05
== 0.8.5
== 0.8.6b
== 0.8.6c
== 0.8.6a
== 0.8.2a
== 0.8.3a
== 0.8
== 0.8.5a
== 0.8.4
== 0.8.6
== 0.8.3
== 0.8.1
== 0.8.2
== 0.8.6d
== 0.8.6e
Medium June 22, 2005 6/22/05
== 0.5
== 0.6.7
== 0.8.2a
== 0.6.4
== 0.6.1
== 0.6
== 0.8.3a
== 0.8
== 0.6.6
<= 0.8.6d
== 0.6.5
== 0.8.5a
== 0.8.4
== 0.8.3
== 0.8.1
== 0.8.2
== 0.6.3
== 0.6.8
== 0.6.8a
== 0.6.2
High June 22, 2005 6/22/05
== 0.5
== 0.6.7
== 0.8.2a
== 0.6.4
== 0.6.1
== 0.6
== 0.8.3a
== 0.8
== 0.6.6
<= 0.8.6d
== 0.6.5
== 0.8.5a
== 0.8.4
== 0.8.3
== 0.8.1
== 0.8.2
== 0.6.3
== 0.6.8
== 0.6.8a
== 0.6.2
High June 22, 2005 6/22/05
== 0.5
== 0.6.7
== 0.8.2a
== 0.6.4
== 0.6.1
== 0.6
== 0.8.3a
== 0.8
== 0.6.6
<= 0.8.6d
== 0.6.5
== 0.8.5a
== 0.8.4
== 0.8.3
== 0.8.1
== 0.8.2
== 0.6.3
== 0.6.8
== 0.6.8a
== 0.6.2
Medium December 31, 2004 12/31/04
== 0.8.5a
High August 16, 2004 8/16/04
== 0.8.5
== 0.6.7
== 0.8.2a
== 0.6.4
== 0.6.1
== 0.6
== 0.8.3a
== 0.8
== 0.6.6
== 0.6.5
== 0.8.5a
== 0.8.4
== 0.8.3
== 0.8.1
== 0.8.2
== 0.6.3
== 0.6.8
== 0.6.8a
== 0.6.2
High April 22, 2003 4/22/03
== 0.5
== 0.6.7
== 0.6.4
== 0.6.1
== 0.6
== 0.6.6
== 0.6.5
== 0.6.3
== 0.6.8
== 0.6.2
High April 22, 2003 4/22/03
== 0.5
== 0.6.7
== 0.6.4
== 0.6.1
== 0.6
== 0.6.6
== 0.6.5
== 0.6.3
== 0.6.8
== 0.6.2
Low April 22, 2003 4/22/03
== 0.5
== 0.6.7
== 0.6.4
== 0.6.1
== 0.6
== 0.6.6
== 0.6.5
== 0.6.3
== 0.6.8
== 0.6.2

cacti / cacti

137 vulnerabilities found
Title Severity Exploit Date Affected Version
High December 2, 2025 12/2/25
< 1.2.29
High August 30, 2025 8/30/25
< 0.8.6d
High February 12, 2025 2/12/25
< 1.2.29
High January 27, 2025 1/27/25
< 1.2.29
High January 27, 2025 1/27/25
< 1.2.29
Critical January 27, 2025 1/27/25
< 1.2.29
Medium January 27, 2025 1/27/25
< 1.2.29
High January 27, 2025 1/27/25
< 1.2.29
Medium January 27, 2025 1/27/25
< 1.2.29
Medium October 7, 2024 10/7/24
< 1.2.28
Medium October 7, 2024 10/7/24
== 1.2.27
High October 7, 2024 10/7/24
< 1.2.28
High October 7, 2024 10/7/24
< 1.2.28
Critical May 14, 2024 5/14/24
< 1.2.27
High May 14, 2024 5/14/24
< 1.2.27
Medium May 14, 2024 5/14/24
< 1.2.27
Low May 14, 2024 5/14/24
< 1.2.27
High May 14, 2024 5/14/24
< 1.2.27
Medium May 14, 2024 5/14/24
< 1.2.27
Low May 14, 2024 5/14/24
< 1.2.27
Medium May 14, 2024 5/14/24
< 1.2.27
High May 14, 2024 5/14/24
< 1.2.27
Critical May 14, 2024 5/14/24
< 1.2.27
High December 22, 2023 12/22/23
== 1.2.25
Medium December 22, 2023 12/22/23
== 1.2.25
Medium December 22, 2023 12/22/23
< 1.2.25
High December 22, 2023 12/22/23
<= 1.2.25
Medium December 22, 2023 12/22/23
== 1.2.25
High December 21, 2023 12/21/23
== 1.2.25
Medium October 27, 2023 10/27/23
== 1.2.25
Medium September 6, 2023 9/6/23
< 1.2.25
Medium September 5, 2023 9/5/23
< 1.2.25
Low September 5, 2023 9/5/23
< 1.2.25
High September 5, 2023 9/5/23
< 1.2.25
High September 5, 2023 9/5/23
< 1.2.25
High September 5, 2023 9/5/23
== 1.2.24
High September 5, 2023 9/5/23
< 1.2.25
Low September 5, 2023 9/5/23
< 1.2.25
Low September 5, 2023 9/5/23
== 1.2.24
Medium September 5, 2023 9/5/23
< 1.2.25
Medium September 5, 2023 9/5/23
< 1.2.25
Medium September 5, 2023 9/5/23
< 1.2.25
Medium September 5, 2023 9/5/23
< 1.2.25
Medium September 5, 2023 9/5/23
< 1.2.25
Medium September 5, 2023 9/5/23
>= 1.2.0 < 1.2.25
Critical September 5, 2023 9/5/23
== 1.2.24
Medium September 5, 2023 9/5/23
== 1.2.24
High September 5, 2023 9/5/23
< 1.2.25
Medium August 22, 2023 8/22/23
<= 0.8.7g
Medium August 22, 2023 8/22/23
== 1.2.19

Showing vulnerabilities for 2 products matching "cacti". Each product has independent pagination.

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.