CVE-2026-64777: A malicious builder peer may be able to request an in-context file by name from the host and receive the conte

Q: How do I fix CVE-2026-64777?

container: upgrade to 1.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-64777 being exploited?

CVE-2026-64777 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-64777 affect?

CVE-2026-64777 affects container. Severity is medium (CVSS 4.3). A malicious builder peer may be able to request an in-context file by name from the host and receive the contents of whatever the name resolves to, even when it resolves outside the build context. This vulnerability is addressed in containe

Q: How urgent is CVE-2026-64777?

Priority 22/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2026-64777 is a medium-severity flaw (CVSS 4.3) affecting container. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A malicious builder peer may be able to request an in-context file by name from the host and receive the contents of whatever the name resolves to, even when it resolves outside the build context. This vulnerability is addressed in container version 1.2.0.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-08-20
Last modified	2026-10-18

Publisher (CNA): Apple Inc. · Vendor: apple

Last updated 2026-10-18 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-20 19:16 UTCPublished CVE record published
2026-10-18 20:10 UTCUpdated Record last modified

apple container UPGRADE

Affected: < 1.2.0

Fixed in: 1.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy container || rpm -q container || container --version

2. UPGRADE to 1.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade container

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade container

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-64777?

container: upgrade to 1.2.0. Exact commands for each OS are on this page.

Is CVE-2026-64777 being exploited?

CVE-2026-64777 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-64777 affect?

CVE-2026-64777 affects container. Severity is medium (CVSS 4.3). A malicious builder peer may be able to request an in-context file by name from the host and receive the contents of whatever the name resolves to, even when it resolves outside the build context. This vulnerability is addressed in containe

How urgent is CVE-2026-64777?

Priority 22/100. No elevated risk signals yet.

Related CVEs

CVE-2026-28909 MEDIUM 6.5 UPGRADE Users who connect to malicious registries with hostnames matching the bypass patterns will have their registry
CVE-2026-64773 HIGH 7.5 UPGRADE An attacker that can reach a container's published TCP port may be able to force the host's forwarding process

References

← Back to latest CVEs