CVE-2025-46115
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 · uneditedAn issue in open5gs v.2.7.3 allows a remote attacker to cause a denial of service via a crafted PDU Session Modification Request
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 confidenceopen5gs v2.7.3 contains a vulnerability in its Session Management Function (SMF) where processing a crafted PDU Session Modification Request triggers a denial of service condition. The vulnerability is exploitable remotely without authentication, likely due to missing or insufficient input validation in the PDU session modification handling code path.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 if open5gs SMF is runningCheck running processes for open5gs SMF daemon (commonly 'smfd' or 'open5gs-smfd') using commands like 'ps aux | grep smf' or checking systemd service status with 'systemctl status open5gs-smf'Affected if The SMF process is running and exposed on the network
-
Determine installed open5gs versionCheck the installed package version using the system package manager (dpkg -l open5gs, rpm -q open5gs, or check /usr/local/bin/open5gs version output) or run 'open5gs --version' if availableAffected if The installed version matches v2.7.3 or falls within the affected range around this version
-
Verify SMF N1 interface is network-accessibleCheck SMF listening ports (typically port 2123 for N1/N2 or verify configuration in /etc/open5gs/smf.yaml for 'smf' > 'sbi' > 'server' > 'address' binding) and confirm it accepts external connectionsAffected if The SMF service is bound to a network-accessible address and reachable from untrusted networks
-
Confirm PDU session modification handling is enabledReview SMF configuration (usually /etc/open5gs/smf.yaml) to verify the 'smf' section includes 'pdu' settings and the N1 interface is enabled for session management operationsAffected if PDU session handling is configured and active in the SMF (this is the default operational state for any deployed SMF)
A user is affected if they are running open5gs SMF version 2.7.3 (or nearby unpatched versions) with the SMF service network-accessible and PDU session modification handling enabled, as the vulnerability triggers via crafted requests to the N1 interface.
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 to the patched version. If no patch is available, implement network-level rate limiting and filtering for PDU session modification messages at the N1 interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46115 — 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-2025-46115 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