CVE-2022-46169

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-02-16), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2022-48996 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 99.8%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

Cacti is an open source platform which provides a robust and extensible operational monitoring and fault management framework for users. In affected versions a command injection vulnerability allows an unauthenticated user to execute arbitrary code on a server running Cacti, if a specific data source was selected for any monitored device. The vulnerability resides in the remote_agent.php file. This file can be accessed without authentication. This function retrieves the IP address of the client via get_client_addr and resolves this IP address to the corresponding hostname via gethostbyaddr. After this, it is verified that an entry within the poller table exists, where the hostname corresponds to the resolved hostname. If such an entry was found, the function returns true and the client is authorized. This authorization can be bypassed due to the implementation of the get_client_addr function. The function is defined in the file lib/functions.php and checks serval $_SERVER variables to determine the IP address of the client. The variables beginning with HTTP_ can be arbitrarily set by an attacker. Since there is a default entry in the poller table with the hostname of the server running Cacti, an attacker can bypass the authentication e.g. by providing the header Forwarded-For: . This way the function get_client_addr returns the IP address of the server running Cacti. The following call to gethostbyaddr will resolve this IP address to the hostname of the server, which will pass the poller hostname check because of the default entry. After the authorization of the remote_agent.php file is bypassed, an attacker can trigger different actions. One of these actions is called polldata. The called function poll_for_data retrieves a few request parameters and loads the corresponding poller_item entries from the database. If the action of a poller_item equals POLLER_ACTION_SCRIPT_PHP, the function proc_open is used to execute a PHP script. The attacker-controlled parameter $poller_id is retrieved via the function get_nfilter_request_var, which allows arbitrary strings. This variable is later inserted into the string passed to proc_open, which leads to a command injection vulnerability. By e.g. providing the poller_id=;id the id command is executed. In order to reach the vulnerable call, the attacker must provide a host_id and local_data_id, where the action of the corresponding poller_item is set to POLLER_ACTION_SCRIPT_PHP. Both of these ids (host_id and local_data_id) can easily be bruteforced. The only requirement is that a poller_item with an POLLER_ACTION_SCRIPT_PHP action exists. This is very likely on a productive instance because this action is added by some predefined templates like Device - Uptime or Device - Polling Time.

This command injection vulnerability allows an unauthenticated user to execute arbitrary commands if a poller_item with the action type POLLER_ACTION_SCRIPT_PHP (2) is configured. The authorization bypass should be prevented by not allowing an attacker to make get_client_addr (file lib/functions.php) return an arbitrary IP address. This could be done by not honoring the HTTP_... $_SERVER variables. If these should be kept for compatibility reasons it should at least be prevented to fake the IP address of the server running Cacti. This vulnerability has been addressed in both the 1.2.x and 1.3.x release branches with 1.2.23 being the first release containing the patch.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
84
EG Risk 84/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
99.8%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
99.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://github.com/Cacti/cacti/security/advisories/GHSA-6p93-p743-35gf · https://nvd.nist.gov/vuln/detail/CVE-2022-46169

Published

December 5, 2022

Last Modified

October 24, 2025

Advisory Details (5)

Auto-updated Oct 30, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: github_commit, github, cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-46169
GitHub advisoryMentions a patch (unverified)

Unauthenticated Command Injection · Advisory · Cacti/cacti · GitHub

https://github.com/Cacti/cacti/security/advisories/GHSA-6p93-p743-35gf
GitHub commit

commit b43f13ae7f1e (Cacti/cacti)

Fix landed in Cacti/cacti commit b43f13ae7f1e — awaiting tagged release

https://github.com/Cacti/cacti/commit/b43f13ae7f1e6bfe4e8e56a80a7cd867cf2db52b
GitHub commit Patch Available

commit a8d59e8fa5f0 (Cacti/cacti)

Patch available: Cacti/cacti release/1.2.23 (contains commit a8d59e8fa5f0)

https://github.com/Cacti/cacti/commit/a8d59e8fa5f0054aa9c6981b1cbe30ef0e2a0ec9
GitHub commit Patch Available

commit 7f0e16312dd5 (Cacti/cacti)

Patch available: Cacti/cacti release/1.2.23 (contains commit 7f0e16312dd5)

https://github.com/Cacti/cacti/commit/7f0e16312dd5ce20f93744ef8b9c3b0f1ece2216

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntucacti (1.1.38+ds1-1ubuntu0.1~esm4) @ bionic2026-11-01ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
cacti1.2.2+ds1-2, 1.2.2+ds1-2+deb10u1, 1.2.2+ds1-2+deb10u2, 1.2.2+ds1-2+deb10u3, 1.2.2+ds1-2+deb10u4
  • every version up to 1.2.2+ds1-2+deb10u5: fixed in 1.2.2+ds1-2+deb10u5
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
cacti1.2.16+ds1-2
  • every version up to 1.2.16+ds1-2+deb11u1: fixed in 1.2.16+ds1-2+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
cacti—
  • every version up to 1.2.22+ds1-3: fixed in 1.2.22+ds1-3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
cacti—
  • every version up to 1.2.22+ds1-3: fixed in 1.2.22+ds1-3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
cacti—
  • every version up to 1.2.22+ds1-3: fixed in 1.2.22+ds1-3
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 86× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 760 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 660 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 15:05 UTCEG score recompute
  2. 2026-11-01 15:05 UTCVendor advisory
  3. 2026-10-31 15:56 UTCVendor advisory
  4. 2026-10-30 16:48 UTCEG score recompute
  5. 2026-10-29 17:39 UTCEG score recompute
  6. 2026-10-29 17:39 UTCVendor advisory
  7. 2026-10-29 16:29 UTCEPSS rescoreEPSS 99.8% · 99th percentile
  8. 2026-10-28 18:31 UTCEG score recompute
  9. 2026-10-27 19:21 UTCEG score recompute
  10. 2026-10-27 19:21 UTCVendor advisory
  11. 2026-10-26 20:12 UTCEG score recompute
  12. 2026-10-26 20:12 UTCVendor advisory
  13. 2026-10-25 21:01 UTCVendor advisory
  14. 2026-10-25 17:57 UTCEG score recompute
  15. 2026-10-25 16:29 UTCEPSS rescoreEPSS 99.8% · 99th percentile
  16. 2026-10-24 21:52 UTCEG score recompute
  17. 2026-10-24 21:52 UTCVendor advisory
  18. 2026-10-24 16:29 UTCEPSS rescoreEPSS 99.8% · 99th percentile
  19. 2026-10-23 22:44 UTCEG score recompute
  20. 2026-10-23 22:44 UTCVendor advisory
  21. 2026-10-22 23:35 UTCEG score recompute
  22. 2026-10-22 23:35 UTCVendor advisory
  23. 2026-10-22 00:26 UTCEG score recompute
  24. 2026-10-21 01:15 UTCEG score recompute
  25. 2026-10-21 01:15 UTCVendor advisory
Show 75 more
  1. 2026-10-20 02:06 UTCEG score recompute
  2. 2026-10-20 02:06 UTCVendor advisory
  3. 2026-10-19 02:56 UTCEG score recompute
  4. 2026-10-19 02:56 UTCVendor advisory
  5. 2026-10-18 03:47 UTCEG score recompute
  6. 2026-10-18 03:47 UTCVendor advisory
  7. 2026-10-17 04:36 UTCEG score recompute
  8. 2026-10-17 04:36 UTCVendor advisory
  9. 2026-10-16 05:26 UTCEG score recompute
  10. 2026-10-15 06:15 UTCEG score recompute
  11. 2026-10-15 06:15 UTCVendor advisory
  12. 2026-10-14 07:07 UTCEG score recompute
  13. 2026-10-14 07:07 UTCVendor advisory
  14. 2026-10-13 07:56 UTCVendor advisory
  15. 2026-10-12 18:44 UTCEG score recompute
  16. 2026-10-12 08:48 UTCVendor advisory
  17. 2026-10-12 04:57 UTCVendor advisory
  18. 2026-10-11 21:19 UTCEG score recompute
  19. 2026-10-11 17:29 UTCEG score recompute
  20. 2026-10-11 17:29 UTCVendor advisory
  21. 2026-10-11 13:36 UTCEG score recompute
  22. 2026-10-11 13:36 UTCVendor advisory
  23. 2026-10-11 09:46 UTCVendor advisory
  24. 2026-10-11 05:57 UTCVendor advisory
  25. 2026-10-10 22:19 UTCVendor advisory
  26. 2026-10-10 18:31 UTCVendor advisory
  27. 2026-10-10 14:43 UTCVendor advisory
  28. 2026-10-10 03:15 UTCVendor advisory
  29. 2026-10-09 23:26 UTCVendor advisory
  30. 2026-10-09 19:37 UTCVendor advisory
  31. 2026-10-09 11:58 UTCVendor advisory
  32. 2026-10-09 08:10 UTCVendor advisory
  33. 2026-10-09 04:21 UTCVendor advisory
  34. 2026-10-08 20:43 UTCVendor advisory
  35. 2026-10-08 16:54 UTCVendor advisory
  36. 2026-10-08 09:15 UTCVendor advisory
  37. 2026-10-08 05:25 UTCVendor advisory
  38. 2026-10-07 17:59 UTCVendor advisory
  39. 2026-10-07 10:22 UTCVendor advisory
  40. 2026-10-07 06:33 UTCVendor advisory
  41. 2026-10-07 02:43 UTCVendor advisory
  42. 2026-10-06 22:54 UTCVendor advisory
  43. 2026-10-06 19:06 UTCVendor advisory
  44. 2026-10-06 11:28 UTCVendor advisory
  45. 2026-10-06 07:39 UTCVendor advisory
  46. 2026-10-05 23:59 UTCVendor advisory
  47. 2026-10-05 20:10 UTCVendor advisory
  48. 2026-10-05 16:22 UTCVendor advisory
  49. 2026-10-05 12:34 UTCVendor advisory
  50. 2026-10-05 08:45 UTCVendor advisory
  51. 2026-10-05 04:57 UTCVendor advisory
  52. 2026-10-05 01:08 UTCEG score recompute
  53. 2026-10-05 01:08 UTCVendor advisory
  54. 2026-10-04 23:19 UTCEPSS rescoreEPSS 99.8% · 99th percentile
  55. 2026-10-04 21:20 UTCVendor advisory
  56. 2026-10-04 17:31 UTCVendor advisory
  57. 2026-10-04 13:42 UTCVendor advisory
  58. 2026-10-04 09:54 UTCVendor advisory
  59. 2026-10-04 06:05 UTCVendor advisory
  60. 2026-10-04 02:16 UTCVendor advisory
  61. 2026-10-03 14:46 UTCVendor advisory
  62. 2026-10-03 10:56 UTCVendor advisory
  63. 2026-10-03 07:07 UTCVendor advisory
  64. 2026-10-03 03:18 UTCVendor advisory
  65. 2026-10-02 19:41 UTCVendor advisory
  66. 2026-10-02 15:52 UTCVendor advisory
  67. 2026-10-02 12:04 UTCVendor advisory
  68. 2026-10-02 08:12 UTCVendor advisory
  69. 2026-10-02 04:21 UTCVendor advisory
  70. 2026-10-02 00:30 UTCVendor advisory
  71. 2026-10-01 20:41 UTCVendor advisory
  72. 2026-10-01 16:52 UTCVendor advisory
  73. 2026-10-01 13:00 UTCVendor advisory
  74. 2026-10-01 09:12 UTCVendor advisory
  75. 2026-10-01 05:23 UTCVendor advisory

Publicly available exploits

(14 references, 10 shown)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 11 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/linux/http/cacti_unauthenticated_cmd_injection✓ verified
    Published Jan 23, 2023

    Cacti 1.2.22 unauthenticated command injection

    Open source ↗
  • GitHub PoCFredBrave/CVE-2022-46169-CACTI-1.2.22
    Published May 1, 2023

    This is a exploit of CVE-2022-46169 to cacti 1.2.22. This exploit allows through an RCE to obtain a reverse shell on your computer.

    Open source ↗
  • GitHub PoCruycr4ft/CVE-2022-46169
    Published May 1, 2023

    Exploit for cacti version 1.2.22

    Open source ↗
  • GitHub PoCicebreack/CVE-2022-46169
    Published Apr 13, 2023

    Fixed exploit for CVE-2022-46169 (originally from https://www.exploit-db.com/exploits/51166)

    Open source ↗
  • Exploit-DBEDB-51166
    Published Mar 31, 2023

    Cacti v1.2.22 - Remote Command Execution (RCE)

    Open source ↗
  • GitHub PoCariyaadinatha/cacti-cve-2022-46169-exploit
    Published Mar 11, 2023

    This is poc of CVE-2022-46169 authentication bypass and remote code execution

    Open source ↗
  • GitHub PoCN1arut/CVE-2022-46169_POC
    Published Jan 16, 2023

    RCE POC for CVE-2022-46169

    Open source ↗
  • GitHub PoCHabib0x0/CVE-2022-46169
    Published Jan 15, 2023

    Cacti: Unauthenticated Remote Code Execution Exploit in Ruby

    Open source ↗
  • GitHub PoCc3rrberu5/CVE-2022-46169
    Published Jan 13, 2023

    Exploit to CVE-2022-46169 vulnerability

    Open source ↗
  • GitHub PoCsAsPeCt488/CVE-2022-46169
    Published Jan 5, 2023

    PoC for CVE-2022-46169 - Unauthenticated RCE on Cacti <= 1.2.22

    Open source ↗

Frequently asked(6)

What is CVE-2022-46169?
CVE-2022-46169 is a critical-severity vulnerability; its CVE record was published on December 5, 2022. Cacti is an open source platform which provides a robust and extensible operational monitoring and fault management framework for users. In affected versions a command injection vulnerability allows an unauthenticated user to execute arbitrary code on a server running Cacti, if a specific data…
When was the CVE record for CVE-2022-46169 published?
The CVE record for CVE-2022-46169 was published on December 5, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2025; the record at its source may have been updated since.
Is CVE-2022-46169 actively exploited?
Yes. CISA added CVE-2022-46169 to the Known Exploited Vulnerabilities catalog on February 16, 2023, affecting Cacti Cacti. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2022-46169?
CVE-2022-46169 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2022-46169?
CVE-2022-46169 affects Cacti Cacti. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2022-46169?
A fix for CVE-2022-46169 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-46169

Explore →

Is Your Infrastructure Affected by CVE-2022-46169?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.