Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated party able to send node-ping messages to MOOS-IvP’s uFldShoreBroker can allegedly redirect bridged data to an address they control. This could expose or alter sensitive operational information without user interaction. The supplied record rates the issue 9.3 critical, but the affected-version metadata is internally inconsistent.
Executive priority
Treat exposed uFldShoreBroker deployments as an immediate investigation and containment priority because compromise could redirect sensitive operational data remotely. Prioritize systems bridging mission-critical or confidential variables. Do not assume a supported patch exists: the cited change is proposed and unmerged, while the version metadata needs clarification.
Technical view
uFldShoreBroker reportedly trusts NODE_BROKER_PING HostRecord data without authenticating its source, then uses that data to establish outbound bridge routes. Crafted messages can therefore redirect bridged variables, affecting confidentiality and integrity. The description says versions through 24.8.1 are affected; however, the structured affected entry lists version “0” and defaults other versions to unaffected.
Likely exposure
Highest risk applies where uFldShoreBroker through 24.8.1 is deployed and untrusted systems can publish NODE_BROKER_PING messages. Exposure depends on messaging and network boundaries, broker configuration, and whether bridged variables contain sensitive or operationally important data. The supplied affected-version record requires vendor confirmation.
Exploitation context
The CVSS 4.0 vector indicates remote, low-complexity, unauthenticated exploitation requiring no user interaction. The bundle does not establish active exploitation, and the CVE is not identified as KEV. A proposed fix exists in an unmerged pull request, so remediation availability and production readiness remain uncertain.
Researcher notes
CWE-345 fits the reported failure to verify message authenticity. The cited ShoreBroker.cpp location and proposed commit provide technical context, but this bundle does not confirm a merged release, exploitation in the wild, or a complete affected-version range. Validate reachability, publisher trust boundaries, route creation, and vendor disposition without testing against production systems.
Mitigation direction
- Identify deployments running uFldShoreBroker and record their exact MOOS-IvP versions.
- Restrict NODE_BROKER_PING publishing and broker network access to explicitly trusted systems.
- Limit outbound broker connectivity to approved destinations where operationally feasible.
- Review vendor guidance and Pull Request #123 before applying any proposed code change.
- Reduce sensitive variable bridging until an authoritative, supported remediation is available.
Validation and detection
- Confirm whether uFldShoreBroker is enabled and reachable from untrusted network or messaging participants.
- Inventory accepted NODE_BROKER_PING publishers and verify each is authorized.
- Review broker records and logs for unexpected host addresses or route changes.
- Check outbound connections from the broker against approved destinations.
- Confirm the installed version and reconcile applicability with updated vendor or CVE guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-85434 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Pull Request #123CVE reference, VulnCheck · issue-tracking, patch
- Proposed fix commit (pull request not merged)CVE reference, VulnCheck · patch
- https://github.com/moos-ivp/moos-ivpCVE reference, VulnCheck · product
- ShoreBroker.cpp (verified sink)CVE reference, VulnCheck · technical-description
- VulnCheck Advisory: MOOS-IvP through 24.8.1 uFldShoreBroker Bridge Route Injection via Unverified Node PingCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.