CVE-2022-41540

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2022-10-18. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The web app client of TP-Link AX10v1 V1_211117 uses hard-coded cryptographic keys when communicating with the router. Attackers who are able to intercept the communications between the web client and router through a man-in-the-middle attack can then obtain the sequence key via a brute-force attack, and access sensitive information.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

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
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
61.7%
KEV
Not listed

Published

October 18, 2022

Last Modified

May 15, 2025

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 39× 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.

  1. 2026-07-23 14:16 UTCEPSS rescore
  2. 2026-07-23 02:14 UTCEG score recompute
  3. 2026-07-22 23:01 UTCEG score recompute
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-21 15:23 UTCEPSS rescore
  7. 2026-07-20 17:05 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 01:58 UTCEPSS rescore
  16. 2026-07-13 22:28 UTCEPSS rescore
  17. 2026-07-13 06:11 UTCEPSS rescore
  18. 2026-07-12 05:44 UTCEPSS rescore
  19. 2026-07-11 08:25 UTCEPSS rescore
  20. 2026-07-11 08:25 UTCEPSS rescore
  21. 2026-07-09 19:08 UTCEPSS rescore
  22. 2026-07-08 15:12 UTCEPSS rescore
  23. 2026-07-07 13:44 UTCEPSS rescore
  24. 2026-07-06 16:25 UTCEPSS rescore
  25. 2026-07-06 02:21 UTCEPSS rescore
Show 60 more
  1. 2026-07-05 02:28 UTCEPSS rescore
  2. 2026-07-04 06:29 UTCEPSS rescore
  3. 2026-07-02 16:58 UTCEPSS rescore
  4. 2026-07-01 15:04 UTCEPSS rescore
  5. 2026-06-30 23:20 UTCEPSS rescore
  6. 2026-06-30 23:20 UTCEPSS rescore
  7. 2026-06-28 14:06 UTCEPSS rescore
  8. 2026-06-28 04:54 UTCEPSS rescore
  9. 2026-06-28 04:54 UTCEPSS rescore
  10. 2026-06-27 03:07 UTCEPSS rescore
  11. 2026-06-27 03:07 UTCEPSS rescore
  12. 2026-06-25 13:48 UTCEPSS rescore
  13. 2026-06-25 13:48 UTCEPSS rescore
  14. 2026-06-24 14:03 UTCEPSS rescore
  15. 2026-06-23 21:31 UTCEPSS rescore
  16. 2026-06-23 21:31 UTCEPSS rescore
  17. 2026-06-22 14:24 UTCEPSS rescore
  18. 2026-06-21 14:55 UTCEPSS rescore
  19. 2026-06-21 14:55 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-21 01:58 UTCEPSS rescore
  22. 2026-06-19 19:24 UTCEPSS rescore
  23. 2026-06-19 19:24 UTCEPSS rescore
  24. 2026-06-18 17:51 UTCEPSS rescore
  25. 2026-06-18 17:51 UTCEPSS rescore
  26. 2026-06-17 17:51 UTCEPSS rescore
  27. 2026-06-17 17:51 UTCEPSS rescore
  28. 2026-06-16 17:51 UTCEPSS rescore
  29. 2026-06-15 17:46 UTCEPSS rescore
  30. 2026-06-13 22:59 UTCEPSS rescore
  31. 2026-06-12 23:10 UTCEPSS rescore
  32. 2026-06-12 23:10 UTCEPSS rescore
  33. 2026-06-10 22:17 UTCEPSS rescore
  34. 2026-06-10 13:21 UTCEPSS rescore
  35. 2026-06-10 13:21 UTCEPSS rescore
  36. 2026-06-07 15:23 UTCEPSS rescore
  37. 2026-06-07 15:23 UTCEPSS rescore
  38. 2026-06-05 22:46 UTCEPSS rescore
  39. 2026-06-05 22:46 UTCEPSS rescore
  40. 2026-06-05 06:09 UTCEPSS rescore
  41. 2026-06-05 06:09 UTCEPSS rescore
  42. 2026-06-04 13:11 UTCEPSS rescore
  43. 2026-06-02 20:12 UTCEPSS rescore
  44. 2026-06-02 20:11 UTCEPSS rescore
  45. 2026-06-01 13:50 UTCEPSS rescore
  46. 2026-06-01 13:50 UTCEPSS rescore
  47. 2026-05-31 22:29 UTCEPSS rescore
  48. 2026-05-31 22:29 UTCEPSS rescore
  49. 2026-05-31 00:15 UTCEPSS rescore
  50. 2026-05-31 00:15 UTCEPSS rescore
  51. 2026-05-29 13:43 UTCEPSS rescore
  52. 2026-05-28 13:43 UTCEPSS rescore
  53. 2026-05-28 13:43 UTCEPSS rescore
  54. 2026-05-27 13:39 UTCEPSS rescore
  55. 2026-05-27 13:39 UTCEPSS rescore
  56. 2026-05-26 07:17 UTCEPSS rescore
  57. 2026-05-26 07:17 UTCEPSS rescore
  58. 2026-05-26 07:17 UTCEPSS rescore
  59. 2026-05-25 13:33 UTCEG score recompute
  60. 2026-05-25 13:33 UTCGHSA enrichment

Publicly available exploits

(1 reference)

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

  • GitHub PoCefchatz/easy-exploits
    First seen May 27, 2022

    Exploits of different CVE IDs (CVE-2021-37910, CVE-2021-40288, CVE-2021-41435, CVE-2021-41436, CVE-2021-41437, CVE-2021-41441, CVE-2021-41442, CVE-2021-41445, CVE-2021-41449, CVE-2021-41450, CVE-2021-41451, CVE-2021-41753, CVE-2021-41788, CVE-2021-46353, CVE-2022-41540, CVE-2022-41541)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-41540?
CVE-2022-41540 is a medium vulnerability published on October 18, 2022. The web app client of TP-Link AX10v1 V1_211117 uses hard-coded cryptographic keys when communicating with the router. Attackers who are able to intercept the communications between the web client and router through a man-in-the-middle attack can then obtain the sequence key via a brute-force…
When was CVE-2022-41540 disclosed?
CVE-2022-41540 was first published in the National Vulnerability Database on October 18, 2022, with the most recent update on May 15, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-41540 actively exploited?
CVE-2022-41540 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 61.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-41540?
CVE-2022-41540 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2022-41540?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-41540, 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-41540

Explore →

Is Your Infrastructure Affected by CVE-2022-41540?

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

Start Free Scan →Browse All CVEs