containerd CRI checkpoint restore CDI annotation smuggling
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-53492
Publishedcontainerd 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.
- Source published
- 1 Jul 2026 17:59:12 UTC
- Source modified
- 2 Jul 2026 12:50:43 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · 8.4 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N
euvd · EUVD-2026-41109
Publishedcontainerd 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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jul 1, 2026, 5:59:12 PM
dateUpdated: Jul 2, 2026, 12:50:43 PM
23 related source bulletins · separate from aliases
RHSA-2026:52946: Red Hat Security Advisory: Multicluster Global Hub 1.8.1 security update
CVE-2026-27145 · CVE-2026-33376 · CVE-2026-33377 · CVE-2026-53492 · CVE-2026-55677 · CVE-2026-55969 · CVE-2026-66801
RHSA-2026:56366: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.19.22 security, enhancement & bug fix update
CVE-2025-61726 · CVE-2025-61729 · CVE-2026-6321 · CVE-2026-6322 · CVE-2026-6734 · CVE-2026-9697 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33186 · CVE-2026-34986 · CVE-2026-42342 · CVE-2026-44740 · CVE-2026-45736 · CVE-2026-48779 · CVE-2026-53488 · CVE-2026-53489 · CVE-2026-53492 · CVE-2026-59869
RHSA-2026:15862: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
CVE-2026-40898 · CVE-2026-44432 · CVE-2026-45287 · CVE-2026-53489 · CVE-2026-53492
RHSA-2026:42852: Red Hat Security Advisory: Multicluster Global Hub 1.5.6 security update
CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33376 · CVE-2026-33377 · CVE-2026-33811 · CVE-2026-39821 · CVE-2026-41567 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-43870 · CVE-2026-46384 · CVE-2026-46385 · CVE-2026-53488 · CVE-2026-53492
RHSA-2026:62260: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.30.0 Release.
CVE-2025-55163 · CVE-2026-8286 · CVE-2026-9277 · CVE-2026-9547 · CVE-2026-9563 · CVE-2026-10050 · CVE-2026-10051 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-13149 · CVE-2026-15075 · CVE-2026-15076 · CVE-2026-27136 · CVE-2026-34986 · CVE-2026-39820 · CVE-2026-39831 · CVE-2026-39835 · CVE-2026-40898 · CVE-2026-40983 · CVE-2026-40984 · CVE-2026-41242 · CVE-2026-41695 · CVE-2026-41716 · CVE-2026-42264 · CVE-2026-42499 · CVE-2026-44705 · CVE-2026-45149 · CVE-2026-45416 · CVE-2026-45623 · CVE-2026-45674 · CVE-2026-46597 · CVE-2026-46681 · CVE-2026-47691 · CVE-2026-48020 · CVE-2026-48068 · CVE-2026-48491 · CVE-2026-49978 · CVE-2026-50010 · CVE-2026-50193 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-53622 · CVE-2026-54399 · CVE-2026-54428 · CVE-2026-54512 · CVE-2026-54513 · CVE-2026-54763 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56745 · CVE-2026-56746 · CVE-2026-56819 · CVE-2026-59296 · CVE-2026-59869 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59877 · CVE-2026-59888 · CVE-2026-59899 · CVE-2026-65600 · CVE-2026-65601 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-68494 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-73086 · CVE-2026-73566 · CVE-2026-73646 · CVE-2026-75838
RHSA-2026:32974: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
CVE-2026-44740 · CVE-2026-47262 · CVE-2026-53489 · CVE-2026-53492
openSUSE-SU-2026:21072-1: Security update for trivy
CVE-2026-44740 · CVE-2026-46680 · CVE-2026-47262 · CVE-2026-50195 · CVE-2026-53488 · CVE-2026-53489 · CVE-2026-53492
RHSA-2026:53530: Red Hat Security Advisory: Multicluster Global Hub 1.7.2 security update
CVE-2026-27145 · CVE-2026-33376 · CVE-2026-33377 · CVE-2026-33811 · CVE-2026-39821 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-42306 · CVE-2026-43870 · CVE-2026-46384 · CVE-2026-46385 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-55677 · CVE-2026-55969 · CVE-2026-66801
RHSA-2026:36873: Red Hat Security Advisory: Submariner v0.20 security fixes and container updates
CVE-2025-47950 · CVE-2025-59530 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-68121 · CVE-2025-68151 · CVE-2026-26017 · CVE-2026-26018 · CVE-2026-44740 · CVE-2026-53488 · CVE-2026-53492
RHSA-2026:47149: Red Hat Security Advisory: Multicluster Global Hub 1.7.2 security update
CVE-2026-27145 · CVE-2026-33376 · CVE-2026-33377 · CVE-2026-33811 · CVE-2026-39821 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-43870 · CVE-2026-46384 · CVE-2026-46385 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-55677
RHSA-2026:71177: Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.7 Container Release Update
CVE-2025-57847 · CVE-2025-66418 · CVE-2026-49825 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-54284 · CVE-2026-59893 · CVE-2026-71458 · CVE-2026-71459 · CVE-2026-71460 · CVE-2026-71461 · CVE-2026-71462 · CVE-2026-71463 · CVE-2026-71464 · CVE-2026-71465 · CVE-2026-71491 · CVE-2026-75884 · CVE-2026-76218 · CVE-2026-76219 · CVE-2026-76220 · CVE-2026-76221 · CVE-2026-76222 · CVE-2026-76648 · CVE-2026-78679 · CVE-2026-84292 · CVE-2026-84394 · CVE-2026-84470 · CVE-2026-84474 · CVE-2026-84475 · CVE-2026-84486 · CVE-2026-84499 · CVE-2026-84502 · CVE-2026-84638 · CVE-2026-84643 · CVE-2026-84644 · CVE-2026-84678 · CVE-2026-84680 · CVE-2026-84683 · CVE-2026-84684 · CVE-2026-84686 · CVE-2026-84689 · CVE-2026-84691 · CVE-2026-84692 · CVE-2026-84703 · CVE-2026-84706 · CVE-2026-84707 · CVE-2026-84708 · CVE-2026-84709 · CVE-2026-84711 · CVE-2026-84712 · CVE-2026-84713 · CVE-2026-84714 · CVE-2026-84716 · CVE-2026-84717 · CVE-2026-84718 · CVE-2026-84719 · CVE-2026-84720 · CVE-2026-84721 · CVE-2026-84724 · CVE-2026-85475 · CVE-2026-87817
RHSA-2026:57013: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.20.17 security, enhancement & bug fix update
CVE-2025-61726 · CVE-2026-6321 · CVE-2026-6322 · CVE-2026-6734 · CVE-2026-9697 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-34986 · CVE-2026-44740 · CVE-2026-45736 · CVE-2026-48779 · CVE-2026-53488 · CVE-2026-53489 · CVE-2026-53492 · CVE-2026-59869
RHSA-2026:32963: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
CVE-2026-44740 · CVE-2026-47262 · CVE-2026-53489 · CVE-2026-53492
RHSA-2026:59467: Red Hat Security Advisory: Red Hat OpenShift API for Data Protection
CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33811 · CVE-2026-39820 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39835 · CVE-2026-42306 · CVE-2026-42499 · CVE-2026-42502 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-71235
RHSA-2026:66022: Red Hat Security Advisory: Red Hat OpenShift API for Data Protection
CVE-2026-15792 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-32283 · CVE-2026-33811 · CVE-2026-33818 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39833 · CVE-2026-39835 · CVE-2026-41178 · CVE-2026-42499 · CVE-2026-42502 · CVE-2026-42504 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-56852 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-71235 · CVE-2026-75593
RHSA-2026:48872: Red Hat Security Advisory: RHACS 4.9.10 security and bug fix update
CVE-2026-13149 · CVE-2026-41889 · CVE-2026-49478 · CVE-2026-49978 · CVE-2026-50163 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-59869
RHSA-2026:51033: Red Hat Security Advisory: Red Hat OpenShift API for Data Protection
CVE-2024-25621 · CVE-2025-61726 · CVE-2025-61728 · CVE-2025-61729 · CVE-2025-66506 · CVE-2025-68121 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33810 · CVE-2026-33811 · CVE-2026-34986 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39835 · CVE-2026-42306 · CVE-2026-42499 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-53488 · CVE-2026-53492
RHSA-2026:71179: Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.6 Container Release Update
CVE-2025-57847 · CVE-2025-66418 · CVE-2026-12564 · CVE-2026-14257 · CVE-2026-15307 · CVE-2026-33818 · CVE-2026-42215 · CVE-2026-42284 · CVE-2026-42504 · CVE-2026-44244 · CVE-2026-49825 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-54284 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-59877 · CVE-2026-59893 · CVE-2026-67322 · CVE-2026-67323 · CVE-2026-67325 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69244 · CVE-2026-71458 · CVE-2026-71459 · CVE-2026-71460 · CVE-2026-71462 · CVE-2026-71463 · CVE-2026-71464 · CVE-2026-71465 · CVE-2026-71491 · CVE-2026-73086 · CVE-2026-73620 · CVE-2026-73622 · CVE-2026-73623 · CVE-2026-73624 · CVE-2026-73625 · CVE-2026-75884 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-76172 · CVE-2026-76218 · CVE-2026-76219 · CVE-2026-76220 · CVE-2026-76221 · CVE-2026-76222 · CVE-2026-78676 · CVE-2026-78679 · CVE-2026-82417 · CVE-2026-84292 · CVE-2026-84375 · CVE-2026-84394 · CVE-2026-84470 · CVE-2026-84474 · CVE-2026-84486 · CVE-2026-84499 · CVE-2026-84502 · CVE-2026-84638 · CVE-2026-84643 · CVE-2026-84644 · CVE-2026-84679 · CVE-2026-84680 · CVE-2026-84683 · CVE-2026-84684 · CVE-2026-84686 · CVE-2026-84689 · CVE-2026-84691 · CVE-2026-84692 · CVE-2026-84703 · CVE-2026-84706 · CVE-2026-84707 · CVE-2026-84708 · CVE-2026-84709 · CVE-2026-84711 · CVE-2026-84712 · CVE-2026-84714 · CVE-2026-84716 · CVE-2026-84717 · CVE-2026-84718 · CVE-2026-84719 · CVE-2026-84720 · CVE-2026-84724 · CVE-2026-85393 · CVE-2026-87817
RHSA-2026:44622: Red Hat Security Advisory: Multicluster Global Hub 1.6.4 security update
CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-33376 · CVE-2026-33377 · CVE-2026-33811 · CVE-2026-39821 · CVE-2026-41567 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-43870 · CVE-2026-46384 · CVE-2026-46385 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-55677
WID-SEC-W-2026-2009: Google Cloud Platform (GKE containerd): Mehrere Schwachstellen
CVE-2026-47262 · CVE-2026-50195 · CVE-2026-53488 · CVE-2026-53489 · CVE-2026-53492
openSUSE-SU-2026:11102-1: trivy-0.71.2-1.1 on GA media
CVE-2026-47262 · CVE-2026-50195 · CVE-2026-53488 · CVE-2026-53489 · CVE-2026-53492
RHSA-2026:41030: Red Hat Security Advisory: Multicluster Global Hub 1.4.7 security update
CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-33811 · CVE-2026-39821 · CVE-2026-41567 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-43870 · CVE-2026-46384 · CVE-2026-46385 · CVE-2026-53488 · CVE-2026-53492
RHSA-2026:48913: Red Hat Security Advisory: RHACS 4.10.6 security and bug fix update
CVE-2026-13149 · CVE-2026-41889 · CVE-2026-49478 · CVE-2026-49978 · CVE-2026-50163 · CVE-2026-53492 · CVE-2026-59869
- Source published
- Jul 1, 2026, 5:59:12 PM (timezone not stated)
- Source modified
- Jul 2, 2026, 12:50:43 PM (timezone not stated)
- Saved here
- 14 Nov 2026 01:17:56 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 4.0 · 8.4 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N
nvd · CVE-2026-53492
Publishedcontainerd 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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-20 · CWE-863
Original publisher date fields
published: 2026-07-01T19:16:54.510
lastModified: 2026-07-02T19:33:00.930
1 source CPE criteria · context only
- cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 1 Jul 2026 19:16:54 UTC
- Source modified
- 2 Jul 2026 19:33:00 UTC
- Saved here
- 25 Oct 2026 13:17:16 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · [email protected] · Secondary · 8.4 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 · [email protected] · Primary · 9.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
osv · GHSA-33vj-92qq-66hc
Published### Impact containerd's 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. ### Patches This bug has been fixed in the following containerd versions: * 2.3.2 * 2.2.5 * 2.1.9 Users should update to these versions to resolve the issue. Recreating existing containers restored from untrusted checkpoints may be necessary to remove smuggled configuration. ### Workarounds Users can mitigate this issue by restricting the restoration of containers from untrusted checkpoint images. If Container Device Interface (CDI) capabilities are not utilized on the node, removing or temporarily relocating host CDI specifications from the default directories (`/etc/cdi` and `/var/run/cdi`) will eliminate the reachability of this vulnerability. ### Credits The containerd project would like to thank Robert Prast (@robertprast) for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md). ### For more information If you have any questions or comments about this advisory: * Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose) * Email us at [[email protected]](mailto:[email protected]) To report a security issue in containerd: * [Report a new vulnerability](https://github.com/containerd/containerd/security/advisories/new) * Email us at [[email protected]](mailto:[email protected])
- Source published
- 19 Jun 2026 19:35:40 UTC
- Source modified
- 10 Sep 2026 03:51:07 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N
Publisher rating · HIGH
osv · GO-2026-5064
Publishedcontainerd CRI checkpoint restore CDI annotation smuggling in github.com/containerd/containerd
- Source published
- 22 Jun 2026 19:28:57 UTC
- Source modified
- 26 Jun 2026 06:29:23 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.