Skip to content
VulniPulse
Medium4.2Red Hat Linux

Medium [CVE-2026-87054] containers-policy.json defaults to insecureAcceptAnything for non-Red Hat registries

This medium-severity Red Hat Linux advisory covers CVE-2026-87054.

CVE-2026-87054 Published Sep 8, 2026Updated by vendor Sep 8, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A flaw was found in operator-sdk-builder. The containers-policy.json configuration file defaults to insecureAcceptAnything for container image registries that are not explicitly listed.

This default setting causes signature verification to be entirely skipped for images pulled from these unlisted registries, which could allow for the use of untrusted or malicious container images. This could enable the use of untrusted container images if not explicitly configured, increasing the risk of supply chain attacks.

Red Hat severity: Moderate — CVSS 4.2 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N). Weakness: CWE-345.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To prevent the use of untrusted container images, configure the `containers-policy.json` to reject unsigned images by default. Set the `default` policy to `{"type": "reject"}` and add explicit `signedBy` or `sigstoreSigned` entries for all trusted registries. This policy should be mounted when invoking `opm` or `operator-sdk` against third-party registries. A restart of the `operator-sdk-builder` or related services may be required for the new policy to be enforced.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.