Quick answers
- Is CVE-2026-85448 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85448 being exploited in the wild.
- How severe is CVE-2026-85448?
- High severity, with a CVSS score of 7.5, published 3 September 2026.
- Which products and versions are affected?
- MOOS-IvP uFldShoreBroker through 24.8.1.
- Is there a fix for CVE-2026-85448?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-85448 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85448?
- Check whether you run MOOS-IvP uFldShoreBroker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in ShoreBroker::handleMailNodePing() which stores claimed community names in parallel vectors without enforcing any upper limit. An attacker (or a malicious publisher on the network) can send messages with an unbounded number of distinct community names, causing the broker to retain this state indefinitely. The attack requires network access to the MOOS-IvP broker and does not require authentication. Successful exploitation leads to memory exhaustion, CPU performance degradation, and potential denial of service. A fix implementing resource limits is expected in a future patch.
Affected products
- MOOS-IvP uFldShoreBroker through 24.8.1
Timeline
- 2026-09-03: disclosed