Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 2.24% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2021
CVE-2021-41190High confidence
Clarify Content-Type handling in OCI spec
opencontainers · distribution-spec
Official source article: GitHub GHSA-MC8V-MGRF-8F4M ↗. Check the applicable product and release in the original source.
3.0LowCVSS 3.1
Scheduled
Patch availableLow technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityLow→Operational priority:Low, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs opencontainers distribution-spec and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
15 package statesRelease-specific package status
Alpine findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | containerd | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.5.8-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | docker | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 20.10.11-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | podman | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.4.4-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | singularity | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.8.5-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | skopeo | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.5.2-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | containerd | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.5.8-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | docker | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 20.10.11-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | podman | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.4.4-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | singularity | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.8.5-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | skopeo | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.5.2-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.21v3.21 · community | containerd | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.5.8-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Alpine v3.21v3.21 · community | docker | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 20.10.11-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Alpine v3.21v3.21 · community | podman | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.4.4-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Alpine v3.21v3.21 · community | singularity | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.8.5-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Alpine v3.21v3.21 · community | skopeo | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.5.2-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2021-41190 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityopencontainers: OCI manifest and index parsing confusion
The vendor explicitly identifies these products as affected by this CVE.
- buildah-tests (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- buildah-tests (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- buildah.src (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- buildah.src (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- buildah (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- buildah (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- containers-common (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- containers-common (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman-catatonit (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman-catatonit (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman-docker (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman-docker (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- Summary
- The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content. In the OCI Image Specification, the manifest and index documents were not self-describing and documents with a single digest could be interpreted as either a manifest or an index. In the OCI Image Specification version 1.0.1 there is specified a recommendation that both manifest and index documents contain a `mediaType` field to identify the type of document.
- Remediation
- For OpenShift Container Platform 4.10 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.10/updating/updating-cluster-cli.html
Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content. In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently. The OCI Distribution Specification has been updated to require that a mediaType value present in a manifest or index match the Content-Type header used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields if they are unable to update to version 1.0.1 of the spec.
What
The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content. In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently. The OCI Distribution Specification has been updated to require that a mediaType value present in a manifest or index match the Content-Type header used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields if they are unable to update to version 1.0.1 of the spec.
Why
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content. In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently. The OCI Distribution Specification has been updated to require that a mediaType value present in a manifest or index match the Content-Type header used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields if they are unable to update to version 1.0.1 of the spec.
Why
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Access of Resource Using Incompatible Type ('Type Confusion') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- Required interaction required
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-843 ↗
CWE-843: Access of Resource Using Incompatible Type ('Type Confusion'). The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- buildah-tests (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- buildah-tests (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- buildah.src (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- buildah.src (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- buildah (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- buildah (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- containers-common (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- containers-common (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman-catatonit (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman-catatonit (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman-docker (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman-docker (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman-gvproxy (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman-gvproxy (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman-manpages (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman-manpages (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman-plugins (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman-plugins (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman-remote (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman-remote (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman-tests (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman-tests (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman.src (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman.src (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- podman (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- podman (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- skopeo-tests (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- skopeo-tests (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- skopeo.src (container-tools:2.0) as a component of Red Hat Enterprise Linux 8
- skopeo.src (container-tools:3.0) as a component of Red Hat Enterprise Linux 8
- and 39 more
- Fixed
- cri-o-0:1.23.0-92.rhaos4.10.gitdaab4d1.el7.src as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-0:1.23.0-92.rhaos4.10.gitdaab4d1.el7.x86_64 as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-debuginfo-0:1.23.0-92.rhaos4.10.gitdaab4d1.el7.x86_64 as a component of Red Hat OpenShift Container Platform 4.10
- oadp/oadp-registry-rhel8@sha256:fe55f8e6d08bed2bd5925d504fbbd3ab7aa60287ed2baff44c583b814505baf8_amd64 as a component of 8Base-OADP-1.0
- oadp/oadp-velero-plugin-rhel8@sha256:1cd2134419e7c7c1421ec68bbbe9a8b06da63b8221672a888d83056f02af16ed_amd64 as a component of 8Base-OADP-1.0
- advanced-cluster-security/rhacs-collector-rhel8@sha256:84d915c50ec190cbc5e718610437dbdd348e0a2e680f9d6c1a66cf181c5c4304_amd64 as a component of RHACS 3.70 for RHEL 8
- advanced-cluster-security/rhacs-docs-rhel8@sha256:dbbff8976b1a1648be50cb562a4d441d278bb79438e7b31758f161b8679e4ee0_amd64 as a component of RHACS 3.70 for RHEL 8
- advanced-cluster-security/rhacs-main-rhel8@sha256:2473ebee564f2915fb58029aabd8437f91e7222e1b145c672ed72df3e319bb02_amd64 as a component of RHACS 3.70 for RHEL 8
- advanced-cluster-security/rhacs-rhel8-operator@sha256:eeaa588e8d35639aca4a3d442808245284e37ff51d04e24ad9e57b041cdfa498_amd64 as a component of RHACS 3.70 for RHEL 8
- advanced-cluster-security/rhacs-roxctl-rhel8@sha256:4ba4c3b42b92dd8cb72c4e30167db269747f391332a8b0802680e56d44a00599_amd64 as a component of RHACS 3.70 for RHEL 8
- rhmtc/openshift-migration-controller-rhel8@sha256:e7f64457dc1a49e939eee2913365bf9d9f579f361dd4242d27cf53c9553ba027_amd64 as a component of 8Base-RHMTC-1.7
- cri-o-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.s390x as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.src as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-debuginfo-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-debuginfo-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-debuginfo-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.s390x as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-debuginfo-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-debugsource-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-debugsource-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-debugsource-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.s390x as a component of Red Hat OpenShift Container Platform 4.10
- cri-o-debugsource-0:1.23.1-9.rhaos4.10.gitbdffb9a.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.10
- openshift4/ose-docker-builder@sha256:5f9bf748cfb377b6b294d58b51afdb4cbc9d183d4c1f738816d433554a16f344_s390x as a component of Red Hat OpenShift Container Platform 4.11
- openshift4/ose-docker-builder@sha256:81d1916216d8c76af899caad7083afc492de8e7f9f4456d3c051444fa3c4c6bb_ppc64le as a component of Red Hat OpenShift Container Platform 4.11
- openshift4/ose-docker-builder@sha256:ca84d407cbe329b9efad6656408b6c6cade8899633305d6fe45d9aaf079cc45c_amd64 as a component of Red Hat OpenShift Container Platform 4.11
- openshift4/ose-docker-builder@sha256:f29d4e996745c69e11333a2435bfd91061a4b6280716b81e8e5b672aac7bc9ee_arm64 as a component of Red Hat OpenShift Container Platform 4.11
- aardvark-dns-2:1.1.0-4.module+el8.7.0+16772+33343656.aarch64 (container-tools:rhel8) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- aardvark-dns-2:1.1.0-4.module+el8.7.0+16772+33343656.ppc64le (container-tools:rhel8) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- and 267 more
- Action
- For OpenShift Container Platform 4.10 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.10/updating/updating-cluster-cli.html
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 17 Nov 2021 · Last source change 4 Aug 2024, 03:08 UTC · CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2021-2367
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- < 1.0.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- < 1.0.1 · Fixed: For OpenShift Container Platform 4.10 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.10/updating/updating-cluster-cli.html
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.