An integer truncation vulnerability in the NAS decoder of OpenAirInterface (OAI) CN5G AMF v2.2.1 allows an unauthenticated remote attacker…
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts give no workaround. Limiting which networks can reach the AMF's N1/N2 interfaces is one way to reduce exposure, but this is not stated by the sources.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The OpenAirInterface 5G core network's Access and Mobility Management Function (AMF) component, which handles mobile device registration, is affected. A remote attacker who needs no login can send specially crafted registration messages with a malformed device identifier, causing the AMF process to crash and denying service to users.
Read the original description
An integer truncation vulnerability in the NAS decoder of OpenAirInterface (OAI) CN5G AMF v2.2.1 allows an unauthenticated remote attacker to cause a denial of service (DoS) via crafted NAS Registration Requests containing a malformed IMEISV in the 5GS Mobile Identity IE. The Type6NasIe::Validate() function truncates a 32-bit length value to 16 bits, bypassing length validation and causing an out-of-bounds heap read in DecodeImeisv(), which can crash the AMF process.
What to do
Workaround: The checked facts give no workaround. Limiting which networks can reach the AMF's N1/N2 interfaces is one way to reduce exposure, but this is not stated by the sources.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Evidence 2
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-117069
What does this mean?
A malformed 5G mobile identity field in a NAS Registration Request can make the AMF decoder truncate an integer, and the crafted message can terminate the AMF process. Repeated crafted requests can keep the AMF control-plane service down.Source: github.com
Am I affected, and how do I check?
The facts confirm the issue in the tested image oaisoftwarealliance/oai-amf:v2.2.1 of OAI CN5G AMF. Triggering it needs a Registration Request carrying a 5GS Mobile Identity IMEISV element with length indicator 65535. To check a deployment, look at the AMF image tag or version reported by the running AMF.Source: github.com
What should I do about it?
No fixed version is listed in the checked facts, so no specific upgrade target can be named from them. Check the OAI project for a later release that addresses this issue.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts give no workaround. Limiting which networks can reach the AMF's N1/N2 interfaces is one way to reduce exposure, but this is not stated by the sources.Source: github.com