How severe is CVE-2026-30057?

CVE-2026-30057 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-30057 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-30057?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-30057 published?

CVE-2026-30057 was published on 2026-08-27 and last updated on 2026-08-31.

CVE-2026-30057

CVE-2026-30057 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-770.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (26th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-770
Published: 2026-08-27
Last modified: 2026-08-31

Description

An issue in the CreateUEContext handler component of free5gc v4.1.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted request.

Frequently asked questions

What is CVE-2026-30057?: An issue in the CreateUEContext handler component of free5gc v4.1.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted request.
How severe is CVE-2026-30057?: CVE-2026-30057 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-30057 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-30057?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-30057 published?: CVE-2026-30057 was published on 2026-08-27 and last updated on 2026-08-31.

References

https://github.com/free5gc/free5gc/issues/755

Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities

CVE-2026-63299 — Critical (CVSS 9.9): An authorization bypass vulnerability in LXD allows an authenticated user to bypass project-level disk and volume…
CVE-2026-82439 — Critical (CVSS 9.8): Description The DRPC server kept a map from function name to request queue and created an entry the first time…
CVE-2026-47891 — Critical (CVSS 9.8): A Spring WebFlux application that relies on the Aalto XML processor to parse XML input does not correctly enforce the…
CVE-2026-74878 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 use an in-memory rate limiter for TOTP brute-force protection that is not shared…
CVE-2026-31283 — Critical (CVSS 9.8): In Totara LMS v19.1.5 and before, the forgot password API does not implement rate limiting for the target email…
CVE-2020-37067 — Critical (CVSS 9.8): Filetto 1.0 FTP server contains a denial of service vulnerability in the FEAT command processing that allows attackers…

Browse all CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities →