CVE-2023-49899

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

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

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

An unauthenticated remote attacker can execute any command on the affected device due to not correctly verifying the origin of a communication channel.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 18, 2026

Advisory Details (1)

Auto-updated Jul 25, 2026
No patch confirmed yet.
generic

CVE-2023-49899 | Claroty

https://claroty.com/team82/disclosure-dashboard/cve-2023-49899

Vendor Advisories for CVE-2023-49899(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 24× in last 7d / 38× 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-28 01:03 UTCGHSA enrichment
  2. 2026-07-27 20:55 UTCGHSA enrichment
  3. 2026-07-27 16:45 UTCEG score recompute
  4. 2026-07-27 16:45 UTCGHSA enrichment
  5. 2026-07-27 14:10 UTCEPSS rescore
  6. 2026-07-27 12:24 UTCGHSA enrichment
  7. 2026-07-27 08:14 UTCGHSA enrichment
  8. 2026-07-27 04:06 UTCGHSA enrichment
  9. 2026-07-26 23:56 UTCGHSA enrichment
  10. 2026-07-26 19:46 UTCGHSA enrichment
  11. 2026-07-26 15:37 UTCEG score recompute
  12. 2026-07-26 15:37 UTCGHSA enrichment
  13. 2026-07-26 14:52 UTCEPSS rescore
  14. 2026-07-26 11:27 UTCEG score recompute
  15. 2026-07-26 11:26 UTCGHSA enrichment
  16. 2026-07-25 14:16 UTCEPSS rescore
  17. 2026-07-24 14:16 UTCEPSS rescore
  18. 2026-07-24 14:16 UTCEPSS rescore
  19. 2026-07-23 14:16 UTCEPSS rescore
  20. 2026-07-23 02:28 UTCEG score recompute
  21. 2026-07-22 23:15 UTCEG score recompute
  22. 2026-07-22 14:06 UTCEPSS rescore
  23. 2026-07-21 15:23 UTCEPSS rescore
  24. 2026-07-21 15:23 UTCEPSS rescore
  25. 2026-07-20 17:06 UTCEPSS rescore
Show 13 more
  1. 2026-07-19 14:29 UTCEPSS rescore
  2. 2026-07-19 14:29 UTCEPSS rescore
  3. 2026-07-19 02:35 UTCEG score recompute
  4. 2026-07-19 02:35 UTCGHSA enrichment
  5. 2026-07-19 02:27 UTCEPSS rescore
  6. 2026-07-18 10:03 UTCEPSS rescore
  7. 2026-07-18 10:03 UTCEPSS rescore
  8. 2026-07-17 02:53 UTCGHSA enrichment
  9. 2026-07-16 22:44 UTCGHSA enrichment
  10. 2026-07-16 18:35 UTCGHSA enrichment
  11. 2026-07-16 14:27 UTCGHSA enrichment
  12. 2026-07-16 10:19 UTCEG score recompute
  13. 2026-07-16 10:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2023-49899?
CVE-2023-49899 is a critical vulnerability published on July 16, 2026. An unauthenticated remote attacker can execute any command on the affected device due to not correctly verifying the origin of a communication channel.
When was CVE-2023-49899 disclosed?
CVE-2023-49899 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-49899 actively exploited?
CVE-2023-49899 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 88.6% of all scored CVEs.
What is the CVSS score of CVE-2023-49899?
CVE-2023-49899 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-49899?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-49899, 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-2023-49899

Explore →

Is Your Infrastructure Affected by CVE-2023-49899?

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

Start Free Scan →Browse All CVEs