Skip to content
Web

CVE-2026-7300

8.8
High
EPSS 0.25%Patch availableJun 18, 2026

Buffer overflow in RTI Connext Web Integration Service enables overflow via crafted input.

common questions

Is CVE-2026-7300 being exploited?

Not confirmed. CVE-2026-7300 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.

How severe is CVE-2026-7300?

CVE-2026-7300 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-7300?

Yes. A fix has been recorded for CVE-2026-7300. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-7300 affect?

CVE-2026-7300 affects RTI Connext Professional (Web Integration Service) - affected versions: 6.1.2 and earlier; 7.0.0 to 7.3.1.2; 7.4.0 to 7.x (pre-patch). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-7300?

Upgrade to fixed version when released; restrict exposure; monitor for exploitation

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
RTI Connext Professional (Web Integration Service) - affected versions: 6.1.2 and earlier; 7.0.0 to 7.3.1.2; 7.4.0 to 7.x (pre-patch)
impact

RCE or crash via crafted input in filter handling due to unchecked buffer size.

action required

Patch when possible

affected versions
RTI Connext Professional
  • affected>= 7.4.0 and < 7.*
  • affected>= 7.0.0 and < 7.3.1.3
  • affected>= 6.1.2 and < 6.1.*

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free