free5GC: Missing Concurrent NAS SMC Validation During NGAP Handover
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-42082
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 09:46 UTC · Revision 1
Source evidence
free5GC: Missing Concurrent NAS SMC Validation During NGAP Handover
core-osv · Original sourcePublished 27 May 2026, 15:59 UTC
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.
osv:CVE-2026-42082
Complete source record
{
"id": "0a7c84f061e1fd476e6d0fcc19aadc38cda8ceecea30c7dba2f17cbd66a75f7f",
"url": "https://osv.dev/vulnerability/CVE-2026-42082",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "free5GC: Missing Concurrent NAS SMC Validation During NGAP Handover",
"summary": "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.",
"evidence": "osv:CVE-2026-42082",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2026-42082",
"aliases": [
"CVE-2026-42082",
"GHSA-vrrx-58h3-prmh",
"GO-2026-5673"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/free5gc/free5gc",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "8b0f4445fc931638fb624463ce3572a203517679"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "4.2.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"cpe": "cpe:2.3:a:free5gc:free5gc:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "4.2.2"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v4.2.1",
"v4.2.0",
"v4.1.0",
"v4.0.1",
"v4.0.0",
"v3.4.5",
"v3.4.4",
"v3.4.3",
"v3.4.2",
"v3.4.1",
"v3.4.0",
"v3.3.0",
"v3.2.1",
"v3.2.0",
"v3.1.1",
"v3.1.0",
"v3.0.7",
"v3.0.6",
"v3.0.5"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-42082.json"
}
}
],
"modified": "2026-10-28T02:30:27.897349323Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/42xxx/CVE-2026-42082.json",
"https://github.com/free5gc/free5gc/security/advisories/GHSA-vrrx-58h3-prmh",
"https://nvd.nist.gov/vuln/detail/CVE-2026-42082"
],
"provider_metadata": {
"cwe_ids": [
"CWE-358"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/42xxx/CVE-2026-42082.json"
}
},
"related_cves": [
{
"value": "CVE-2026-42082",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 494311,
"published_at": "2026-05-27T15:59:21.228+00:00"
}