CVE-2026-64773: An attacker that can reach a container's published TCP port may be able to force the host's forwarding process

This month

HIGH 7.5REMOTEUPGRADE

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

An attacker that can reach a container's published TCP port may be able to force the host's forwarding process to buffer an unbounded amount of that client's data in memory, for as long as the backend container connection takes to complete — with no cap on how much accumulates or how long the wait can be stretched. This vulnerability is addressed in container version 1.2.0.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-770
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 22:17 UTCPublished CVE record published
2026-10-18 20:10 UTCUpdated Record last modified

apple container UPGRADE

Affected: >= 0.3.0 and < 1.2.0

Fixed in: 1.2.0

Safe to downgrade to: a release before 0.3.0

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.

3. If no update is available yet, DOWNGRADE to a release before 0.3.0 (Debian / Ubuntu)

apt-cache madison container sudo apt install container=<VERSION_BEFORE_0.3.0> sudo apt-mark hold container

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list container sudo dnf downgrade container-<VERSION_BEFORE_0.3.0> sudo dnf versionlock add container

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-64773?

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

Is CVE-2026-64773 being exploited?

CVE-2026-64773 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-64773 affect?

CVE-2026-64773 affects container. Severity is high (CVSS 7.5). An attacker that can reach a container's published TCP port may be able to force the host's forwarding process to buffer an unbounded amount of that client's data in memory, for as long as the backend container connection takes to complete

How urgent is CVE-2026-64773?

Priority 40/100. High severity; Remotely exploitable, no login, no user action

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-64777 MEDIUM 4.3 UPGRADE A malicious builder peer may be able to request an in-context file by name from the host and receive the conte

References

← Back to latest CVEs