CVE-2026-107446 json
containerd overlaybd through 1.0.18 has a do_load_index (LSMT index loading) integer overflow (and resultant out-of-bounds heap access) for…
published last mo. modified last mo. also EUVD-2026-94691
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
containerd overlaybd through 1.0.18 has a do_load_index (LSMT index loading) integer overflow (and resultant out-of-bounds heap access) for index_bytes, if an untrusted overlaybd blob from a registry is used in a scenario with multiple overlaybd-backed containers.
Patch / fix
- github.com/containerd/overlaybd@a536e33 commit
- github.com/containerd/overlaybd@d80c179 commit
- github.com/containerd/overlaybd#438 pull request
Is CVE-2026-107446 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H |
Affected products
- containerd overlaybd
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
- github.com /containerd/overlaybd/pull/438
- github.com /containerd/overlaybd/commit/a536e3341c82517268b5ce32375b36faecb1fb40
- github.com /containerd/overlaybd/commit/d80c1790920a17e84da025675530624aee753f1b
- github.com /containerd/overlaybd/blob/58f1508f4c841fe27da428f54d987000f7dae4de/src/overlaybd/lsmt/file.cpp
- github.com /containerd/overlaybd/blob/58f1508f4c841fe27da428f54d987000f7dae4de/src/image_file.cpp
Sources
- CVE List CVE-2026-107446
- NVD CVE-2026-107446
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.