Open5GS resource exhaustion in AMF session pool
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
Open5GS AMF has a resource leak that lets an authenticated device, reached remotely over the network, exhaust the session pool by repeatedly sending PDU session requests that fail DNN or S-NSSAI validation. The stale session contexts left behind degrade service for other subscribers.
Written by a model
Original description
Open5GS AMF through 2.8.0 contains a resource leak vulnerability that allows authenticated UEs to exhaust the session pool by triggering failed DNN or S-NSSAI validation. Attackers can repeat PDU Session Establishment Requests with different PDU Session Identity values, leaving stale amf_sess contexts that degrade service for other subscribers.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133703 (Open5GS AMF through 2.8.0 Session Pool Exhaustion via gmm_handle_ul_nas_transport), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133703 (entry last updated 2026-11-20):
Affected:
- open5gs open5gs: through 2.8.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133703 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133703 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/open5gs/open5gs/security/advisories/GHSA-ch5j-wv55-jmr6
- https://github.com/open5gs/open5gs/commit/f746810744d8d95563a17a49e711e2c4c408d1e4
- https://github.com/open5gs/open5gs/blob/v2.8.0/src/amf/gmm-handler.c
- https://www.vulncheck.com/advisories/open5gs-amf-through-2.8.0-session-pool-exhaustion-via-gmm-handle-ul-nas-transport
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133703
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133703"}.Affected versions
- open5gs open5gsthrough 2.8.0
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · open5gs/open5gs · Advisory GHSA-ch5j-wv55-jmr6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133703 |
| Record | NVD · CVE-2026-133703 |
| Other links 3 | |
| Patch | GitHub · open5gs/open5gs · Commit f7468107 |
| Repository | GitHub · open5gs/open5gs · src/amf/gmm-handler.c |
| Link | vulncheck.com · advisories/open5gs-amf-through-2.8.0-session-pool-exhaustion-via-gmm-handle-ul-nas-transport |
Questions about CVE-2026-133703
Is CVE-2026-133703 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133703?
open5gs: through 2.8.0.
Source: cve.now feed data
Related
- CVE-2026-116543Open5GS 1.3.0 through 2.8.0 Heap Out-of-Bounds Write via SBI Multipart Parser
- CVE-2026-15720Pre-auth heap out-of-bounds read in the AMF NAS 5GS mobile-identity handler
- CVE-2026-108105Open5GS through 2.8.0 MME Reachable Assertion via GTPv1 SGSN Context Request
- CVE-2023-4883Multiple vulnerabilities in Open5GS
- CVE-2023-4882Multiple vulnerabilities in Open5GS
- CVE-2023-23846Due to insufficient length validation in the Open5GS GTP library versions prior to versions 2.4.13 and 2.5.7, when parsing extension headers
No corrections so far. Something wrong on this page? Report an error.