CVE-2022-29173

HIGHNVD 8.08.0
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.0 under NVD CVSS v3. EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week
8.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

go-tuf is a Go implementation of The Update Framework (TUF). go-tuf does not correctly implement the client workflow for updating the metadata files for roles other than the root role. Specifically, checks for rollback attacks are not implemented correctly meaning an attacker can cause clients to install software that is older than the software which the client previously knew to be available, and may include software with known vulnerabilities. In more detail, the client code of go-tuf has several issues in regards to preventing rollback attacks: 1. It does not take into account the content of any previously trusted metadata, if available, before proceeding with updating roles other than the root role (i.e., steps 5.4.3.1 and 5.5.5 of the detailed client workflow). This means that any form of version verification done on the newly-downloaded metadata is made using the default value of zero, which always passes. 2. For both timestamp and snapshot roles, go-tuf saves these metadata files as trusted before verifying if the version of the metafiles they refer to is correct (i.e., steps 5.5.4 and 5.6.4 of the detailed client workflow). A fix is available in version 0.3.0 or newer. No workarounds are known for this issue apart from upgrading.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
36
EG Risk 36/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)
Severity80% × 45%
Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.
EPSS PROB
0.6%
EPSS %ILE
46th
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 (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.

EG Severity
8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). 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: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: 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 none (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (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

Published

May 5, 2022

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Sep 20, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

No protection against rollback attacks for roles other than root · Advisory · theupdateframework/go-tuf · GitHub

https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-66x3-6cw3-v5gj
GitHub commit

commit ed6788e710fc (theupdateframework/go-tuf)

Fix landed in theupdateframework/go-tuf commit ed6788e710fc — awaiting tagged release

https://github.com/theupdateframework/go-tuf/commit/ed6788e710fc3093a7ecc2d078bf734c0f200d8d

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatadvanced-cluster-security/rhacs-roxctl-rhel8:3.71.0-52022-07-25redhat

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/theupdateframework/go-tuf—
  • every version up to 0.3.0: fixed in 0.3.0
—

Weakness Classification(1)

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 11× in last 7d / 37× 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 97 of 206 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-29173?
CVE-2022-29173 is a high-severity vulnerability; its CVE record was published on May 5, 2022. go-tuf is a Go implementation of The Update Framework (TUF). go-tuf does not correctly implement the client workflow for updating the metadata files for roles other than the root role. Specifically, checks for rollback attacks are not implemented correctly meaning an attacker can cause clients to…
When was the CVE record for CVE-2022-29173 published?
The CVE record for CVE-2022-29173 was published on May 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-29173 actively exploited?
CVE-2022-29173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-29173?
CVE-2022-29173 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2022-29173?
A fix for CVE-2022-29173 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-29173

Explore →

Is Your Infrastructure Affected by CVE-2022-29173?

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

Book a Demo →Browse All CVEs