CVE-2026-4967

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

In IMS, there is a possible out of bounds read due to a missing bounds check. This could lead to remote denial of service with no additional execution privileges needed.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
32.4%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 6, 2026

Advisory Details (1)

Auto-updated Jul 3, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-4967(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 19× 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-07 04:55 UTCEG score recompute
  2. 2026-07-07 04:55 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 15:43 UTCEG score recompute
  5. 2026-07-06 15:43 UTCGHSA enrichment
  6. 2026-07-06 02:31 UTCEG score recompute
  7. 2026-07-06 02:31 UTCGHSA enrichment
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 13:19 UTCEG score recompute
  10. 2026-07-05 13:18 UTCGHSA enrichment
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-05 00:05 UTCEG score recompute
  13. 2026-07-05 00:05 UTCGHSA enrichment
  14. 2026-07-04 10:52 UTCEG score recompute
  15. 2026-07-04 10:52 UTCGHSA enrichment
  16. 2026-07-03 21:39 UTCEG score recompute
  17. 2026-07-03 21:39 UTCGHSA enrichment
  18. 2026-07-03 08:27 UTCEG score recompute
  19. 2026-07-03 08:26 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-4967?
CVE-2026-4967 is a high vulnerability published on July 3, 2026. In IMS, there is a possible out of bounds read due to a missing bounds check. This could lead to remote denial of service with no additional execution privileges needed.
When was CVE-2026-4967 disclosed?
CVE-2026-4967 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4967 actively exploited?
CVE-2026-4967 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-4967?
CVE-2026-4967 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-4967?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4967, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-4967?

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