CVE-2026-9300

MEDIUMNVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability has been found in omec-project amf up to 2.1.1. This affects an unknown part of the component NGSetupRequest Handler. Such manipulation leads to memory corruption. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. It is best practice to apply a patch to resolve this issue.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
—
EPSS
13.7%
KEV
Not listed

Published

May 23, 2026

Last Modified

May 26, 2026

Advisory Details (3)

Auto-updated Jun 13, 2026
Patch available. Sources: github_pr.
github_pr Patch Available

Address multiple cases of crashes due to malformed NGAP input

Patch available: omec-project/amf v2.2.0 (PR #666 merged 2026-04-21)

https://github.com/omec-project/amf/pull/666
generic

AMF crashes on handling RegistrationRequest · Issue #679 · omec-project/amf · GitHub

https://github.com/omec-project/amf/issues/679
generic

GitHub - omec-project/amf · GitHub

https://github.com/omec-project/amf/

Vendor Advisories for CVE-2026-9300(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/omec-project/amf—1.7.1-0.20260421213846-34bc6724acc9—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 04:24 UTCOSV refresh
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-13 22:31 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 02:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-01 15:07 UTCEPSS rescore
  25. 2026-06-30 23:22 UTCEPSS rescore
Show 61 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 02:52 UTCGHSA enrichment
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 19:19 UTCGHSA enrichment
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 19:06 UTCGHSA enrichment
  8. 2026-06-25 13:50 UTCGHSA enrichment
  9. 2026-06-25 13:50 UTCEPSS rescore
  10. 2026-06-24 14:05 UTCEPSS rescore
  11. 2026-06-23 21:33 UTCEPSS rescore
  12. 2026-06-22 14:25 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-19 19:26 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-17 19:54 UTCGHSA enrichment
  18. 2026-06-17 17:53 UTCEPSS rescore
  19. 2026-06-16 19:18 UTCGHSA enrichment
  20. 2026-06-16 17:53 UTCEPSS rescore
  21. 2026-06-15 17:49 UTCEPSS rescore
  22. 2026-06-15 17:49 UTCEPSS rescore
  23. 2026-06-15 14:51 UTCGHSA enrichment
  24. 2026-06-14 23:18 UTCEPSS rescore
  25. 2026-06-14 14:01 UTCGHSA enrichment
  26. 2026-06-13 23:00 UTCEPSS rescore
  27. 2026-06-13 14:46 UTCGHSA enrichment
  28. 2026-06-12 23:12 UTCEPSS rescore
  29. 2026-06-12 23:12 UTCEPSS rescore
  30. 2026-06-12 15:45 UTCGHSA enrichment
  31. 2026-06-11 16:42 UTCGHSA enrichment
  32. 2026-06-11 14:00 UTCEPSS rescore
  33. 2026-06-10 22:19 UTCEPSS rescore
  34. 2026-06-10 17:17 UTCGHSA enrichment
  35. 2026-06-10 13:22 UTCEPSS rescore
  36. 2026-06-09 18:17 UTCGHSA enrichment
  37. 2026-06-08 19:17 UTCGHSA enrichment
  38. 2026-06-08 14:17 UTCEPSS rescore
  39. 2026-06-07 19:28 UTCGHSA enrichment
  40. 2026-06-07 15:25 UTCEPSS rescore
  41. 2026-06-06 20:28 UTCGHSA enrichment
  42. 2026-06-06 13:47 UTCEPSS rescore
  43. 2026-06-05 22:47 UTCEPSS rescore
  44. 2026-06-05 21:28 UTCGHSA enrichment
  45. 2026-06-05 06:10 UTCEPSS rescore
  46. 2026-06-04 22:28 UTCGHSA enrichment
  47. 2026-06-04 13:12 UTCEPSS rescore
  48. 2026-06-03 23:28 UTCGHSA enrichment
  49. 2026-06-03 00:28 UTCGHSA enrichment
  50. 2026-06-02 20:13 UTCEPSS rescore
  51. 2026-06-02 01:28 UTCGHSA enrichment
  52. 2026-06-01 13:52 UTCEPSS rescore
  53. 2026-06-01 02:28 UTCGHSA enrichment
  54. 2026-05-31 22:30 UTCEPSS rescore
  55. 2026-05-31 00:16 UTCEPSS rescore
  56. 2026-05-29 13:44 UTCEPSS rescore
  57. 2026-05-28 13:44 UTCEPSS rescore
  58. 2026-05-27 13:40 UTCEPSS rescore
  59. 2026-05-26 13:44 UTCEPSS rescore
  60. 2026-05-26 07:18 UTCEPSS rescore
  61. 2026-05-23 12:02 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9300?
CVE-2026-9300 is a medium vulnerability published on May 23, 2026. A vulnerability has been found in omec-project amf up to 2.1.1. This affects an unknown part of the component NGSetupRequest Handler. Such manipulation leads to memory corruption. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. It is best practice…
When was CVE-2026-9300 disclosed?
CVE-2026-9300 was first published in the National Vulnerability Database on May 23, 2026, with the most recent update on May 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9300 actively exploited?
CVE-2026-9300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9300?
CVE-2026-9300 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-9300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9300, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9300

Explore →

Is Your Infrastructure Affected by CVE-2026-9300?

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

Start Free Scan →Browse All CVEs