CVE-2026-2522
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 · uneditedA security vulnerability has been detected in Open5GS up to 2.7.6. Impacted is an unknown function of the file /src/mme/esm-build.c of the component MME. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
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 · moderate confidenceMemory corruption vulnerability in Open5GS MME component's ESM (EPS Session Management) build function in /src/mme/esm-build.c allows remote attackers to potentially execute arbitrary code or cause denial of service via malformed session management 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.7.6CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 installed Open5GS versionRun 'open5gs --version' or check package manager: 'dpkg -l | grep open5gs' (Debian) or 'rpm -qa | grep open5gs' (RHEL). Alternatively, check /usr/local/bin/open5gs-mmed --version if installed.Affected if Version is 2.7.6 or lower, or version cannot be determined (implies unpatched)
-
Confirm MME component is presentVerify the open5gs-mmed binary exists: 'ls /usr/local/bin/open5gs-mmed' or 'which open5gs-mmed'. Check for MME configuration in /etc/open5gs/mme.yaml or /etc/open5gs/mme/*.yaml.Affected if MME binary or configuration files exist, indicating MME component is installed
-
Verify MME service is enabled or runningCheck service status: 'systemctl status open5gs-mmed' or check running processes: 'ps aux | grep mmed'. Check if MME is referenced in main config /etc/open5gs.yaml.Affected if MME service is active, enabled at startup, or configured in the main Open5GS configuration
-
Assess MME network exposureCheck listening ports for MME S1-MME interface: 'ss -tlnp | grep 36412' or 'netstat -tlnp | grep 36412'. Review firewall rules and network interfaces the MME binds to in /etc/open5gs/mme.yaml.Affected if MME is listening on a network-accessible IP (not localhost/127.0.0.1 only), especially on default S1-MME port 36412
Environment is affected if Open5GS version is 2.7.6 or lower, the MME component is installed and enabled, and the MME service is exposed to network access.
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 Open5GS beyond version 2.7.6 once patch is available; as interim measure, restrict network exposure of MME component and implement monitoring for indicators of compromise given public exploit existence.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2522 — 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-2522 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