CVE-2026-30080
Auth Bypass in Openairinterface Oai-Cn5G-Amf 2.2.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NSummary
CVE-2026-30080 is a high-severity Authentication Bypass by Capture-replay (CWE-294) vulnerability in Openairinterface Oai-Cn5G-Amf. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SC-23 (Session Authenticity) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-30080 is a vulnerability in OpenAirInterface version 2.2.0, specifically within the CN5G AMF (Access and Mobility Management Function) component. The issue arises because the software accepts a Security Mode Complete message without any integrity protection, even though its configuration supports integrity algorithms NIA1 and NIA2. If a UE (User Equipment) sends an initial registration request advertising only the IA0 security capability (indicating no integrity), OpenAirInterface accepts it and proceeds, establishing a downgraded security context. This flaw is classified under CWE-294 and carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).
An unauthenticated remote attacker can exploit this vulnerability by impersonating a UE and transmitting an initial registration request limited to IA0 integrity capability. With network accessibility, low attack complexity, and no required privileges or user interaction, the attacker tricks the AMF into activating a security context devoid of integrity protection. This enables replay attacks, where malicious messages can be captured and resent, resulting in high integrity impacts such as unauthorized modifications or repetitions of critical signaling messages.
The vulnerability is tracked in a GitLab issue for the oai-cn5g-amf repository at https://gitlab.eurecom.fr/oai/cn5g/oai-cn5g-amf/-/issues/78, where security practitioners can review details on potential mitigations, patches, or workarounds.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-20503
Vulnerability Data
OpenAirInterface v2.2.0 accepts Security Mode Complete without any integrity protection. Configuration has supported integrity NIA1 and NIA2. But if an UE sends initial registration request with only security capability IA0, OpenAirInterface accepts and proceeds. This downgrade security context can lead…
more
to the possibility of replay attack.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V10.4.16V10.5.1
Mitigating Controls (NIST 800-53 r5) AI
Session authenticity mechanisms directly stop replay of captured authentication traffic by enforcing freshness or cryptographic binding.
Transmission integrity (with anti-replay) stops captured messages from being accepted as valid later.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Protecting and verifying identity assertions prevents replay of captured authentication material.
Encryption and integrity protections for data-in-transit directly block capture-replay of credentials or tokens.
Network monitoring may detect anomalous replays after the fact but does not prevent the design flaw.
Strong authentication methods can reduce replay risk but do not inherently address captured messages.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Cryptographic protections (e.g., nonces, timestamps, message authentication codes) make captured authentication messages unusable for replay.
Secure authentication mechanisms directly prevent replay attacks by requiring fresh, non-replayable credentials or tokens.
Network security controls such as encryption and integrity protection reduce the feasibility of capturing and replaying authentication traffic.
Application security requirements can mandate replay-resistant authentication designs, but the control itself does not prescribe the technical measures.