CVE-2026-30077
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenAirInterface V2.2.0 AMF crashes when it fails to decode the message. Not all decode failures result in a crash. But the crash is consistent for particular inputs. An example input in hex stream is 80 00 00 0E 00 00 01 00 0F 80 02 02 40 00 58 00 01 88.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe OpenAirInterface AMF v2.2.0 contains a vulnerability where specifically crafted message inputs cause a crash during message decoding. The provided hex input (80 00 00 0E 00 00 01 00 0F 80 02 02 40 00 58 00 01 88) triggers a consistent crash, indicating missing or improper error handling in the decoding logic that fails to gracefully handle malformed ASN.1 or NAS messages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenAirInterface AMF installationLocate the OpenAirInterface AMF installation directory and confirm the presence of the AMF binary or service. Check system processes for running AMF-related processes.Affected if OpenAirInterface AMF version 2.2.0 is installed and running
-
Determine the exact AMF versionQuery the installed AMF version using the version flag or check the software manifest/binary metadata. Common methods include: oai-amf --version, checking docker image tags, or reviewing installation logs.Affected if The installed version is exactly 2.2.0 as reported in the affected versions
-
Verify message decoding functionality is exposedDetermine if the AMF is configured to accept external NAS or ASN.1 messages. Check configuration files for exposed interfaces (such as N1/N2 interfaces) that process incoming messages.Affected if The AMF has exposed interfaces that accept NAS or ASN.1 encoded messages from external sources
-
Monitor for crash behavior with malformed inputIf feasible, review application logs or system crash dumps for evidence of decoding-related crashes. The specific hex input (80 00 00 0E 00 00 01 00 0F 80 02 02 40 00 58 00 01 88) triggers the crash.Affected if Logs or crash dumps show decoding failures that result in process termination rather than graceful error handling
A system is affected if OpenAirInterface AMF version 2.2.0 is running and configured to process incoming NAS or ASN.1 messages, where malformed messages can crash the decoding routine.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of OpenAirInterface that properly handles decode failures without crashing, or implement input validation and exception handling around the message decoding routines to prevent denial of service.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30077 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data