VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

cacti: vulnerability history, versions and safety

cacti is a package in the Debian ecosystem. Vulert records 301 vulnerabilities for it across 31 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
301 vulnerabilities recorded U301
i
23 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
17 in the last 12 months

Most recent disclosure 05 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cacti vulnerabilities

Vulert verdict on cacti i

Updated on 23 Oct 2026

Careful: 23 of the 301 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 301 vulnerabilities on record across 2026 years, 17 in the last year.

What to do: Plan around the 23 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 301 over 2026 years · 17 in the last year i
  • Latest disclosure 05 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 23 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for cacti, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 31 of 31 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2003 6
  • 2004 4
  • 2005 10
  • 2006 10
  • 2007 6
  • 2008 8
  • 2009 4
  • 2010 14
  • 2011 2
  • 2012 2
  • 2013 8
  • 2014 20
  • 2015 16
  • 2016 7
  • 2017 32
  • 2018 6
  • 2019 14
  • 2020 18
  • 2021 4
  • 2022 11
  • 2023 38
  • 2024 30
  • 2025 13
  • 2026 17

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 17 of the 301 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for cacti

The 5 most severe of 301 vulnerabilities recorded for this package

Search all 301 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Remote Code Execution Vulnerability in Cacti (CVE-2017-12065) 9.8 critical 1.1.16+ds1-1 01 Aug 2017
Critical SQL Injection Vulnerability in Cacti Package 9.8 critical 1.2.16+ds1-2+deb11u2 05 Sep 2023
Cacti Authentication Bypass Vulnerability - CVE-2022-0730 9.8 critical 1.2.16+ds1-2+deb11u1 03 Mar 2022
Critical Command Injection Vulnerability in Cacti Allows Unauthenticated Remote Code Execution 9.8 critical 1.2.16+ds1-2+deb11u1 05 Dec 2022
Type Juggling Vulnerability in Cacti Password Verification 9.1 critical 1.2.16+ds1-2+deb11u4 14 May 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About cacti

Is cacti safe to use?

Vulert records 301 vulnerabilities for cacti in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 301 not yet rated. 23 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does cacti have?

301 vulnerabilities are recorded for cacti in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 301 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new cacti vulnerabilities disclosed?

17 vulnerabilities were recorded for cacti in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of cacti are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor cacti for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the cacti version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.