Clarify Content-Type handling

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.0 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N

EPSS

• CVE-2021-41190: 2.22% estimated exploitation activity in the next 30 days; percentile 82.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Patches The OCI Distribution Specification will be 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. Workarounds 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. References https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh For more information If you…

Published by the source

18 Nov 2021, 16:13 UTC

Last modified by the source

1 Feb 2023, 05:06 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mc8v-mgrf-8f4m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-41190

Advisory: Clarify Content-Type handling
IDs: CVE-2021-41190, GHSA-mc8v-mgrf-8f4m
Record: https://patchnext.com/advisories/cve-2021-41190 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/opencontainers/distribution-spec 1.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/opencontainers/distribution-spec: affected < 1.0.1; fixed in 1.0.1

## Suggested inspection (read-only)
- Go github.com/opencontainers/distribution-spec: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/opencontainers/distribution-spec.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mc8v-mgrf-8f4m (GitHub-reviewed advisory GHSA-mc8v-mgrf-8f4m lists affected ranges: Go github.com/opencontainers/distribution-spec >=0 <1.0.1)

Commands are suggestions: review each one before running it.