CVE-2026-4757

HIGHPre-NVD 7.27.2—
EchelonGraph scoreHIGH confidence

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

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

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

A VAPIX API parameter had improper input validation which could allow code execution and potentially lead to a privilege escalation. This flaw can only be exploited after authenticating with an administrator-privileged service account.

CVSS v3
7.2
EG Score
7.2(high)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic
https://www.axis.com/dam/public/41/7d/0f/cve-2026-4757pdf-en-US-543642.pdf

Vendor Advisories for CVE-2026-4757(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 27× in last 7d / 42× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 22:06 UTCGHSA enrichment
  3. 2026-08-20 10:25 UTCGHSA enrichment
  4. 2026-08-19 22:49 UTCEG score recompute
  5. 2026-08-19 22:49 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 11:12 UTCGHSA enrichment
  8. 2026-08-18 23:32 UTCEG score recompute
  9. 2026-08-18 23:32 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 11:54 UTCGHSA enrichment
  12. 2026-08-18 00:18 UTCEG score recompute
  13. 2026-08-18 00:18 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 12:37 UTCGHSA enrichment
  16. 2026-08-17 01:01 UTCEG score recompute
  17. 2026-08-17 01:01 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 13:25 UTCEG score recompute
  20. 2026-08-16 13:25 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-16 01:49 UTCGHSA enrichment
  23. 2026-08-15 14:13 UTCGHSA enrichment
  24. 2026-08-15 02:36 UTCEG score recompute
  25. 2026-08-15 02:36 UTCGHSA enrichment
Show 17 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 15:00 UTCGHSA enrichment
  3. 2026-08-14 03:24 UTCEG score recompute
  4. 2026-08-14 03:24 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 15:48 UTCGHSA enrichment
  7. 2026-08-13 04:12 UTCGHSA enrichment
  8. 2026-08-12 16:36 UTCEG score recompute
  9. 2026-08-12 16:36 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 04:57 UTCEG score recompute
  12. 2026-08-12 04:57 UTCGHSA enrichment
  13. 2026-08-11 17:21 UTCEG score recompute
  14. 2026-08-11 17:20 UTCGHSA enrichment
  15. 2026-08-11 06:24 UTCEG score recompute
  16. 2026-08-11 05:58 UTCEG score recompute
  17. 2026-08-11 05:58 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-4757?
CVE-2026-4757 is a high vulnerability published on August 11, 2026. A VAPIX API parameter had improper input validation which could allow code execution and potentially lead to a privilege escalation. This flaw can only be exploited after authenticating with an administrator-privileged service account.
When was CVE-2026-4757 disclosed?
CVE-2026-4757 was first published in the National Vulnerability Database on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4757 actively exploited?
CVE-2026-4757 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.6% of all scored CVEs.
What is the CVSS score of CVE-2026-4757?
CVE-2026-4757 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-4757?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4757, 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-4757

Explore →

Is Your Infrastructure Affected by CVE-2026-4757?

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

Start Free Scan →Browse All CVEs