dbcve.org
Open5gsApplication

CVE-2025-15529

HIGH · 7.5 CVSS v3.1 Published 2026-01-16
Fix available
A fix is available. Upgrade to after 2.7.6 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
A vulnerability was found in Open5GS up to 2.7.6. Affected by this issue is the function sgwc_s5c_handle_create_session_response of the file src/sgwc/s5c-handler.c. Performing a manipulation results in denial of service. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The patch is named b19cf6a2dbf5d30811be4488bf059c865bd7d1d2. To fix this issue, it is recommended to deploy a patch.

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

A detailed technical summary for this CVE is being prepared.

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
Open5gsApplication
Affected:<= 2.7.6

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

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.7.6
Vendor patch github.com →
Recommended fix High confidence

Open5GS version 2.7.7 or later (or git commit b19cf6a2dbf5d30811be4488bf059c865bd7d1d2 and newer)

  1. 1. Identify current Open5GS version by running 'open5gs -v' or checking the installed package version
  2. 2. Check the Open5GS releases page at https://github.com/open5gs/open5gs/releases for versions newer than 2.7.6 that contain the security fix
  3. 3. If a newer stable release (e.g., 2.7.7 or later) is available, upgrade by following the official upgrade guide at https://open5gs.org/open5gs/docs/guide/02-building-open5gs/
  4. 4. Alternatively, apply the vendor patch by checking out commit b19cf6a2dbf5d30811be4488bf059c865bd7d1d2: 'git cherry-pick b19cf6a2dbf5d30811be4488bf059c865bd7d1d2' or manually apply the changes to src/sgwc/s5c-handler.c
  5. 5. Rebuild and restart the Open5GS services after applying the fix
  6. 6. Verify the fix is applied by checking the S5C handler code no longer contains the vulnerable code pattern
Caveat Minor version upgrade should have minimal breaking changes; review release notes for any configuration or behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15529 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15529 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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