CVE-2022-41924

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2022-11-21. NVD baseline CVSS 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2022-7441 (ENISA EUVD) · GHSA-vqp6-rc3h-83cp (GitHub Security Advisories) · GO-2022-1120 (OSV.dev)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 9.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A vulnerability identified in the Tailscale Windows client allows a malicious website to reconfigure the Tailscale daemon tailscaled, which can then be used to remotely execute code. In the Tailscale Windows client, the local API was bound to a local TCP socket, and communicated with the Windows client GUI in cleartext with no Host header verification. This allowed an attacker-controlled website visited by the node to rebind DNS to an attacker-controlled DNS server, and then make local API requests in the client, including changing the coordination server to an attacker-controlled coordination server. An attacker-controlled coordination server can send malicious URL responses to the client, including pushing executables or installing an SMB share. These allow the attacker to remotely execute code on the node. All Windows clients prior to version v.1.32.3 are affected. If you are running Tailscale on Windows, upgrade to v1.32.3 or later to remediate the issue.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
1.9%
EPSS %ILE
79th
KEV
Not listed

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.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

Published

November 23, 2022

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Oct 2, 2026
Patch available. Sources: github.
Web pageMentions a patch (unverified)

Security Bulletins · Tailscale

https://tailscale.com/security-bulletins/#ts-2022-004
GitHub advisoryMentions a patch (unverified)

Tailscale Windows daemon is vulnerable to RCE via CSRF · Advisory · tailscale/tailscale · GitHub

https://github.com/tailscale/tailscale/security/advisories/GHSA-vqp6-rc3h-83cp
Web page

CVE-2022-41924 - RCE in Tailscale, DNS Rebinding, and You

https://emily.id.au/tailscale

Vendor Advisories for CVE-2022-41924(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gotailscale.com @ 1.32.3 (fixes < 1.32.3)—ghsa

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

(8 across 8 ecosystems)
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
tailscale—
  • every version up to 1.32.3-r0: fixed in 1.32.3-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
tailscale—
  • every version up to 1.32.3-r0: fixed in 1.32.3-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
tailscale—
  • every version up to 1.32.3-r0: fixed in 1.32.3-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
tailscale—
  • every version up to 1.32.3-r0: fixed in 1.32.3-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
tailscale—
  • every version up to 1.32.3-r0: fixed in 1.32.3-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
tailscale—
  • every version up to 1.32.3-r0: fixed in 1.32.3-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
tailscale—
  • every version up to 1.32.3-r0: fixed in 1.32.3-r0
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
tailscale.com—
  • every version up to 1.32.3: fixed in 1.32.3
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 249 rows 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 149 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 09:52 UTCEchelonGraph re-scored
  2. 2026-11-13 09:52 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  3. 2026-11-12 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  4. 2026-11-12 11:21 UTCEchelonGraph re-scored
  5. 2026-11-12 11:21 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  6. 2026-11-11 16:33 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  7. 2026-11-11 12:50 UTCEchelonGraph re-scored
  8. 2026-11-11 12:50 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  9. 2026-11-10 16:36 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  10. 2026-11-10 14:19 UTCEchelonGraph re-scored
  11. 2026-11-10 14:19 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  12. 2026-11-09 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  13. 2026-11-09 15:48 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  14. 2026-11-08 17:17 UTCEchelonGraph re-scored
  15. 2026-11-08 17:17 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  16. 2026-11-08 16:34 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  17. 2026-11-07 18:46 UTCEchelonGraph re-scored
  18. 2026-11-07 18:46 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  19. 2026-11-07 16:34 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  20. 2026-11-06 20:14 UTCEchelonGraph re-scored
  21. 2026-11-06 20:14 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  22. 2026-11-06 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  23. 2026-11-05 21:43 UTCEchelonGraph re-scored
  24. 2026-11-05 21:43 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  25. 2026-11-05 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
Show 75 more
  1. 2026-11-04 23:12 UTCEchelonGraph re-scored
  2. 2026-11-04 23:12 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  3. 2026-11-04 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  4. 2026-11-04 06:55 UTCOSV refresh
  5. 2026-11-04 00:40 UTCEchelonGraph re-scored
  6. 2026-11-04 00:40 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  7. 2026-11-03 16:39 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  8. 2026-11-03 02:09 UTCEchelonGraph re-scored
  9. 2026-11-03 02:09 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  10. 2026-11-02 16:39 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  11. 2026-11-02 03:38 UTCEchelonGraph re-scored
  12. 2026-11-02 03:38 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  13. 2026-11-01 08:24 UTCGHSA enrichmentGHSA-vqp6-rc3h-83cp · GitHub severity CRITICAL · GitHub CVSS 9.6
  14. 2026-11-01 08:24 UTCEchelonGraph re-scored
  15. 2026-11-01 05:07 UTCEchelonGraph re-scored
  16. 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  17. 2026-10-31 06:35 UTCEchelonGraph re-scored
  18. 2026-10-30 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  19. 2026-10-30 08:04 UTCEchelonGraph re-scored
  20. 2026-10-29 16:29 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  21. 2026-10-29 09:33 UTCEchelonGraph re-scored
  22. 2026-10-28 16:28 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  23. 2026-10-28 11:03 UTCEchelonGraph re-scored
  24. 2026-10-27 16:28 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  25. 2026-10-27 11:42 UTCEchelonGraph re-scored
  26. 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  27. 2026-10-26 13:12 UTCEchelonGraph re-scored
  28. 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  29. 2026-10-25 14:31 UTCEchelonGraph re-scored
  30. 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  31. 2026-10-23 17:24 UTCEchelonGraph re-scored
  32. 2026-10-23 16:28 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  33. 2026-10-22 18:53 UTCEchelonGraph re-scored
  34. 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  35. 2026-10-21 20:21 UTCEchelonGraph re-scored
  36. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.8% · 78th percentile
  37. 2026-10-20 21:50 UTCEchelonGraph re-scored
  38. 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  39. 2026-10-19 23:19 UTCEchelonGraph re-scored
  40. 2026-10-19 16:28 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  41. 2026-10-18 22:44 UTCEchelonGraph re-scored
  42. 2026-10-18 16:28 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  43. 2026-10-18 08:26 UTCEchelonGraph re-scored
  44. 2026-10-17 23:52 UTCEchelonGraph re-scored
  45. 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  46. 2026-10-17 01:18 UTCEchelonGraph re-scored
  47. 2026-10-16 16:35 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  48. 2026-10-16 01:30 UTCEchelonGraph re-scored
  49. 2026-10-15 16:28 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  50. 2026-10-14 21:04 UTCEchelonGraph re-scored
  51. 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  52. 2026-10-13 16:54 UTCEchelonGraph re-scored
  53. 2026-10-13 16:29 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  54. 2026-10-12 18:03 UTCEchelonGraph re-scored
  55. 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  56. 2026-10-11 22:10 UTCEchelonGraph re-scored
  57. 2026-10-11 13:44 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  58. 2026-10-10 19:57 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  59. 2026-10-09 20:04 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  60. 2026-10-08 17:05 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  61. 2026-10-07 23:45 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  62. 2026-10-06 15:14 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  63. 2026-10-05 17:40 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  64. 2026-10-04 23:19 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  65. 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  66. 2026-10-02 16:23 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  67. 2026-10-01 19:47 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  68. 2026-09-30 16:06 UTCEchelonGraph re-scored
  69. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  70. 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  71. 2026-09-28 13:48 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  72. 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  73. 2026-09-26 15:55 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  74. 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.8% · 77th percentile
  75. 2026-09-24 05:15 UTCOSV refresh

Related CVEs(same product + same CWE)

Same product

2 shown

Go:tailscale.com

Frequently asked(5)

What is CVE-2022-41924?
CVE-2022-41924 is a critical-severity vulnerability; its CVE record was published on November 23, 2022. A vulnerability identified in the Tailscale Windows client allows a malicious website to reconfigure the Tailscale daemon tailscaled, which can then be used to remotely execute code. In the Tailscale Windows client, the local API was bound to a local TCP socket, and communicated with the Windows…
When was the CVE record for CVE-2022-41924 published?
The CVE record for CVE-2022-41924 was published on November 23, 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-41924 actively exploited?
CVE-2022-41924 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (79th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-41924?
CVE-2022-41924 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2022-41924?
A fix for CVE-2022-41924 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-41924 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-41924?

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

Book a Demo →Browse All CVEs