Incorrect Calculation vulnerability in RTI Connext Professional (Core Libraries) allows Abuse Existing Functionality. This issue affects Connext Professional: from 7.4.0 before 7.7.0.1, from 7.0.0 before 7.3.1.6, from 6.1.0 before 6.1.*, from 6.0.0 before 6.0.*, from 5.3.0 before 5.3.*, from 5.2.0 before 5.2.*, from 4.1x before 5.1.*.
CVE-2026-18459
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 54(Track)EG Risk 54/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 computedSeverity87% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 37%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 22, 2026
Advisory Details (1)
Auto-updated Sep 22, 2026RTI Connext Security Bulletins and Advisories (last updated on 2026-09-22)
https://www.rti.com/vulnerabilities/#cve-2026-18459Vendor Advisories for CVE-2026-18459(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 10× in last 7d / 10× 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.
- 2026-09-23 21:34 UTCEG score recompute
- 2026-09-23 21:34 UTCGHSA enrichment
- 2026-09-23 08:36 UTCGHSA enrichment
- 2026-09-22 19:37 UTCEG score recompute
- 2026-09-22 19:37 UTCGHSA enrichment
- 2026-09-22 18:53 UTCEG score recompute
- 2026-09-22 18:53 UTCGHSA enrichment
- 2026-09-22 18:31 UTCEG score recompute
- 2026-09-22 17:53 UTCEG score recompute
- 2026-09-22 17:53 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-682
- CVE-2023-2163EG 10.0CRITICAL
- CVE-2026-16363EG 9.8CRITICAL
- CVE-2026-1229EG 9.8CRITICAL
- CVE-2024-36736EG 9.8CRITICAL
- CVE-2022-30600EG 9.8EPSS p92CRITICAL
- CVE-2021-44847EG 9.8EPSS p90CRITICAL
- CVE-2020-0221EG 9.8CRITICAL
- CVE-2018-8319EG 9.8EPSS p94CRITICAL
- CVE-2026-54754EG 9.6CRITICAL
- CVE-2026-53670EG 9.3CRITICAL
Frequently asked(5)
What is CVE-2026-18459?
When was CVE-2026-18459 disclosed?
Is CVE-2026-18459 actively exploited?
What is the CVSS score of CVE-2026-18459?
How do I remediate CVE-2026-18459?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18459
Is Your Infrastructure Affected by CVE-2026-18459?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.