Skip to content
Applications

CVE-2026-85448

8.7
High
EPSS 0.35%Patch availableSep 4, 2026

Unbounded community names in MOOS-IvP ShoreBroker allow memory exhaustion.

common questions

Is CVE-2026-85448 being exploited?

Not confirmed. CVE-2026-85448 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.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-85448?

CVE-2026-85448 is rated High with a CVSS score of 8.7. 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-85448?

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

What does CVE-2026-85448 affect?

CVE-2026-85448 affects MOOS-IvP uFldShoreBroker, moos-ivp <= 24.8.1, Autonomy middleware on marine/robotic platforms. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-85448?

Upgrade to the patched moos-ivp release/commit or block/untrust publishers and rate-limit community claims.

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

executive summary
technical analysis
affected
MOOS-IvP uFldShoreBrokermoos-ivp <= 24.8.1Autonomy middleware on marine/robotic platforms
impact

A publisher can send unlimited distinct community names to exhaust memory/CPU, causing denial-of-service and retained state bloat.

action required

Patch when possible

affected versions
moos-ivp moos-ivp
  • affected<= 24.8.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