CVE-2026-53492

CRITICALNVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% 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
Trending — Patch released this week
9.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.6Exploit: NoneExposed: 0

A fix is available — apply it.

containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.

CVSS v3
9.6
EG Score
9.6(medium)
EPSS
33.7%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 1, 2026
Patch available. Sources: github.
github Patch Available

CDI annotation smuggling during CRI checkpoint restore · Advisory · containerd/containerd · GitHub

https://github.com/containerd/containerd/security/advisories/GHSA-33vj-92qq-66hc

Vendor Advisories for CVE-2026-53492(9)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-globalhub/multicluster-globalhub-rhel9-operator:17840605152026-07-16redhat
ubuntucontainerd-stable (2.2.2-0ubuntu1.1) @ resolute2026-07-16ubuntu
ubuntucontainerd (2.2.2-0ubuntu1.1) @ resolute2026-07-16ubuntu
redhatrhacm2/submariner-rhel9-operator:17829331932026-07-08redhat
redhatgrype-main-0.115.0-0.1.hum12026-06-29redhat
redhatsyft-main-1.46.0-0.1.hum12026-06-29redhat
redhattrivy-main-0.69.3-1.2.hum12026-05-09redhat

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/containerd/containerd/v2—2.3.2—

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 17× in last 7d / 122× 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 123 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53492?
CVE-2026-53492 is a critical vulnerability published on June 19, 2026. containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a…
When was CVE-2026-53492 disclosed?
CVE-2026-53492 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53492 actively exploited?
CVE-2026-53492 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53492?
CVE-2026-53492 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-53492?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53492, 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-2026-53492

Explore →

Is Your Infrastructure Affected by CVE-2026-53492?

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

Start Free Scan →Browse All CVEs