CVE-2026-8744

MEDIUMNVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-05-17. NVD baseline CVSS 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-30690 (ENISA EUVD) · GHSA-pch7-6gr4-gw9w (GitHub Security Advisories)Source: ENISA EUVD

4.3EG
EchelonGraph verdictPlan mitigationThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A vulnerability was determined in Open5GS up to 2.7.7. Affected is the function ogs_sbi_subscription_data_add/ogs_sbi_nf_service_add in the library /lib/sbi/context.c of the component NRF. Executing a manipulation can lead to denial of service. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. This patch is called 819db11a08b9736a3576c4f99ceb28f7eb99523a. A patch should be applied to remediate this issue.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 17, 2026

Last Modified

May 18, 2026

Advisory Details (5)

Auto-updated Jun 18, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
GitHub pull request

[SBI] Replace nf_service_pool assert with graceful cap-and-break

Upstream fix in progress (PR #4534 · open5gs/open5gs, state=open)

https://github.com/open5gs/open5gs/pull/4534
Web page

[Bug]: NRF crash in `ogs_sbi_nf_service_add()` by exhausting the NF service pool · Issue #4466 · open5gs/open5gs · GitHub

https://github.com/open5gs/open5gs/issues/4466
Web page

[Bug]: NRF crash on `POST /nnrf-nfm/v1/subscriptions` by exhausting the subscription pool · Issue #4465 · open5gs/open5gs · GitHub

https://github.com/open5gs/open5gs/issues/4465
GitHub commit

commit 819db11a08b9 (open5gs/open5gs)

Fix landed in open5gs/open5gs commit 819db11a08b9 — awaiting tagged release

https://github.com/open5gs/open5gs/commit/819db11a08b9736a3576c4f99ceb28f7eb99523a
Web page

GitHub - open5gs/open5gs: Open5GS is a C-language Open Source implementation for 5G Core and EPC, i.e. the core network of LTE/NR network (Release-17) · GitHub

https://github.com/open5gs/open5gs/

Vendor Advisories for CVE-2026-8744(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 228 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-29 23:25 UTCOSV refresh
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-25 13:54 UTCEG score recompute
  12. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  15. 2026-10-22 12:39 UTCEG score recompute
  16. 2026-10-22 12:39 UTCGHSA enrichmentGHSA-pch7-6gr4-gw9w · GitHub severity LOW · GitHub CVSS 4.3
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  18. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  20. 2026-10-18 03:04 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  22. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  23. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  24. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.8% · 55th percentile
Show 72 more
  1. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  2. 2026-10-12 14:50 UTCEG score recompute
  3. 2026-10-11 19:16 UTCEG score recompute
  4. 2026-10-11 16:33 UTCEG score recompute
  5. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  6. 2026-10-11 13:49 UTCEG score recompute
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  9. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  12. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  14. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  15. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  16. 2026-09-30 03:40 UTCOSV refresh
  17. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  18. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  19. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  20. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  21. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  26. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  27. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  28. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  29. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  30. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  31. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  32. 2026-09-11 09:38 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  33. 2026-09-11 06:23 UTCOSV refresh
  34. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  35. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  36. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  37. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  38. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  39. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  40. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  41. 2026-08-30 19:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  42. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  43. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  45. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  46. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  47. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  48. 2026-08-23 17:20 UTCEG score recompute
  49. 2026-08-23 17:20 UTCGHSA enrichmentGHSA-pch7-6gr4-gw9w · GitHub severity LOW · GitHub CVSS 4.3
  50. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  51. 2026-08-22 00:47 UTCEG score recompute
  52. 2026-08-22 00:47 UTCGHSA enrichmentGHSA-pch7-6gr4-gw9w · GitHub severity LOW · GitHub CVSS 4.3
  53. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  54. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  55. 2026-08-20 19:14 UTCEG score recompute
  56. 2026-08-20 19:14 UTCGHSA enrichmentGHSA-pch7-6gr4-gw9w · GitHub severity LOW · GitHub CVSS 4.3
  57. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  58. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  59. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  60. 2026-08-17 10:10 UTCEG score recompute
  61. 2026-08-17 10:10 UTCGHSA enrichmentGHSA-pch7-6gr4-gw9w · GitHub severity LOW · GitHub CVSS 4.3
  62. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  63. 2026-08-16 03:42 UTCEG score recompute
  64. 2026-08-16 03:42 UTCGHSA enrichmentGHSA-pch7-6gr4-gw9w · GitHub severity LOW · GitHub CVSS 4.3
  65. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  66. 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  67. 2026-08-14 02:15 UTCEG score recompute
  68. 2026-08-14 02:15 UTCGHSA enrichmentGHSA-pch7-6gr4-gw9w · GitHub severity LOW · GitHub CVSS 4.3
  69. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  70. 2026-08-12 14:43 UTCEG score recompute
  71. 2026-08-12 14:43 UTCGHSA enrichmentGHSA-pch7-6gr4-gw9w · GitHub severity LOW · GitHub CVSS 4.3
  72. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile

Frequently asked(5)

What is CVE-2026-8744?
CVE-2026-8744 is a medium-severity vulnerability; its CVE record was published on May 17, 2026. A vulnerability was determined in Open5GS up to 2.7.7. Affected is the function ogs_sbi_subscription_data_add/ogs_sbi_nf_service_add in the library /lib/sbi/context.c of the component NRF. Executing a manipulation can lead to denial of service. It is possible to launch the attack remotely. The…
When was the CVE record for CVE-2026-8744 published?
The CVE record for CVE-2026-8744 was published on May 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 18, 2026; the record at its source may have been updated since.
Is CVE-2026-8744 actively exploited?
CVE-2026-8744 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8744?
CVE-2026-8744 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-8744?
An upstream fix for CVE-2026-8744 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-8744 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-8744

Explore →

Is Your Infrastructure Affected by CVE-2026-8744?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.