CVE-2022-29173

HIGHNVD 8.08.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.0 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.0Exploit: None knownExposed: 0

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.0(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity80% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

May 5, 2022

Last Modified

November 21, 2024

References (4)

Patch Availability(1)

Vendor / EcosystemFixed in / 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 rangeFixed inDependents
github.com/theupdateframework/go-tuf—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 13× in last 7d / 49× 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 117 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-29173?
CVE-2022-29173 is a high vulnerability 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 CVE-2022-29173 disclosed?
CVE-2022-29173 was first published in the National Vulnerability Database on May 5, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-29173 actively exploited?
CVE-2022-29173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.2% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-29173, 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

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.

Start Free Scan →Browse All CVEs