CVE-2026-46680

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% 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
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

containerd is an open-source container runtime. In versions prior to 1.7.32, 2.0.9, 2.2.4 and 2.3.1, containers launched with a numeric User directive that cannot be parsed as a 32-bit integer are incorrectly treated as a username, leading to runAsNonRoot evasion. If a crafted image provides an /etc/passwd file mapping this large numeric string to root, the container ultimately runs as root (UID 0). This allows the Kubernetes runAsNonRoot restriction to be bypassed, causing unexpected behavior for environments that require containers to run as a non-root user. This issue has been fixed in versions 1.7.32, 2.0.9, 2.2.4 and 2.3.1.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 21, 2026

Last Modified

July 3, 2026

Advisory Details (1)

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

containerd user ID handling bypass allows runAsNonRoot evasion · Advisory · containerd/containerd · GitHub

https://github.com/containerd/containerd/security/advisories/GHSA-fqw6-gf59-qr4w

Vendor Advisories for CVE-2026-46680(2)

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 / EcosystemFixed in / PatchReleasedSource
redhattrivy-main-0.72.0-0.1.hum12026-07-02redhat

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

(6 across 5 ecosystems)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/containerd/containerd—1.7.32—
github.com/containerd/containerd/v2—2.3.1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
containerd1.4.12~ds1-1~deb11u1 ... 2.1.9+ds1-1 (82 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
containerd1.6.20~ds1-1 ... 2.1.9+ds1-2 (42 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
containerd1.7.24~ds1-10 ... 2.1.9+ds1-2 (16 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
containerd1.7.24~ds1-10 ... 2.1.9+ds1-2 (15 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 31× 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 129 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46680?
CVE-2026-46680 is a high vulnerability published on May 21, 2026. containerd is an open-source container runtime. In versions prior to 1.7.32, 2.0.9, 2.2.4 and 2.3.1, containers launched with a numeric User directive that cannot be parsed as a 32-bit integer are incorrectly treated as a username, leading to runAsNonRoot evasion. If a crafted image provides an…
When was CVE-2026-46680 disclosed?
CVE-2026-46680 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on July 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46680 actively exploited?
CVE-2026-46680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.1% of all scored CVEs.
What is the CVSS score of CVE-2026-46680?
CVE-2026-46680 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46680?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46680, 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-46680

Explore →

Is Your Infrastructure Affected by CVE-2026-46680?

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

Start Free Scan →Browse All CVEs