⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 5.3

How to Fix CVE-2026-8779: Memory Corruption in amf

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 5.3 - Medium
Actively exploited?Not currently listed in CISA KEV
Affected2.1.3-dev
Fixed in2.2.0
Type (CWE)CWE-119: Memory Corruption

What is CVE-2026-8779?

CVE-2026-8779 is a memory corruption flaw in amf. A malformed input corrupts memory state in a way that leads to remote code execution under realistic conditions. Vendor description: A vulnerability was determined in omec-project amf up to 2.1.3-dev. Impacted is the function NGSetupRequest of the file ngap/handler.go.

Why this CVE matters

Memory-corruption flaws in a network-facing service are a perennial target for exploit developers. Modern mitigations slow but rarely stop a determined attacker, especially against embedded or appliance-class targets.

For deployments of amf that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open amf's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-8779

  1. Read the vendor advisory in full: https://vuldb.com/vuln/364403
  2. Upgrade amf to 2.2.0 or a later version listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Open-source library upgrade

The vendor advisory (https://github.com/omec-project/amf/pull/666) names the patched release as amf 2.2.0. Pull the

fixed version through whichever ecosystem actually ships amf.


# Vendor advisory: https://vuldb.com/vuln/364403
# npm / pnpm / yarn
npm install amf@latest
npm ls amf

# Or pin to the patched version named in the advisory
npm install amf@<patched-version>

# pip / Poetry
pip install --upgrade "amf"
pip show amf | grep -i version
poetry add "amf@^<patched-version>"

# Go modules
go get example.com/amf@<patched-version>
go mod tidy

# Rust crates
cargo update -p amf

# Composer
composer require vendor/amf:^<patched-version>


# Vendor advisory: https://vuldb.com/vuln/364403
# Container image: rebuild against the patched base and roll the deployment.
docker pull <your-registry>/amf:<patched-tag>
docker stop <app> && docker rm <app>
docker run -d --name <app> <your-registry>/amf:<patched-tag>

# Kubernetes
kubectl set image deployment/<deployment-name> <container>=<your-registry>/amf:<patched-tag>
kubectl rollout status deployment/<deployment-name>

Linux package upgrade

The vendor advisory (https://github.com/omec-project/amf/pull/666) names the patched build as amf 2.2.0.


# Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade amf
dpkg -s amf | grep -i version

# RHEL / Rocky / AlmaLinux / Fedora
sudo dnf upgrade --refresh amf -y
rpm -q amf

# openSUSE
sudo zypper refresh && sudo zypper update amf

# Restart the service that loads the patched binary
sudo systemctl restart amf 2>/dev/null || true
sudo systemctl status amf --no-pager 2>/dev/null || true


# Vendor advisory: https://vuldb.com/vuln/364403
# Container deployments: rebuild with the patched package layer, then roll the workload.
docker pull <your-registry>/amf:<patched-tag>
docker stop <app> && docker rm <app>
docker run -d --name <app> <your-registry>/amf:<patched-tag>

# Kubernetes
kubectl set image deployment/<deployment-name> amf=<your-registry>/amf:<patched-tag>
kubectl rollout status deployment/<deployment-name>

Verify the fix landed


# Vendor advisory: https://vuldb.com/vuln/364403
# 1. Compare the running version against the fixed build named above.
#    (Replace the version probe with the platform-specific command from the block above.)

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag this CVE on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you cannot patch immediately

Block network reachability to the vulnerable service from untrusted networks and apply the patched build. Memory-corruption bugs cannot be reliably mitigated at the network layer; the patch is the fix.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for repeated service restarts, crash logs from the affected daemon, and core files generated around the time of any anomalous traffic. A memory-corruption flaw used for exploitation often leaves a trail of failed attempts before the successful one.

Frequently asked questions

Is CVE-2026-8779 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-8779?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for amf run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*