CVE-2022-46169

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

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_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 100%CVSS: 9.8Exploit: NoneExposed: 0

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.8(high)
EG Risk
84(Attend)
EG Risk 84/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
100.0%
KEV
⚠ Exploited

Published

December 5, 2022

Last Modified

October 24, 2025

Advisory Details (5)

Auto-updated May 25, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_commit, github, cisa.
cisa Patch Available🔴 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 Patch Available

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 / EcosystemFixed in / PatchReleasedSource
ubuntucacti (1.1.38+ds1-1ubuntu0.1~esm4) @ bionic2026-07-22ubuntu

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.

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 29× in last 7d / 143× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 274 total refreshes for this CVE.

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

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCFredBrave/CVE-2022-46169-CACTI-1.2.22
    First seen 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
    First seen May 1, 2023

    Exploit for cacti version 1.2.22

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

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

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

    Cacti v1.2.22 - Remote Command Execution (RCE)

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

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

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

    RCE POC for CVE-2022-46169

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

    Cacti: Unauthenticated Remote Code Execution Exploit in Ruby

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

    Exploit to CVE-2022-46169 vulnerability

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

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

    Open source ↗
  • GitHub PoCSystemVll/CVE-2022-46169
    First seen Jan 2, 2023

    Cacti Unauthenticated Command Injection

    Open source ↗

Frequently asked(6)

What is CVE-2022-46169?
CVE-2022-46169 is a critical vulnerability 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 CVE-2022-46169 disclosed?
CVE-2022-46169 was first published in the National Vulnerability Database on December 5, 2022, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 patching attention.
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 full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2022-46169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-46169, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.