CVE-2026-85432

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

MOOS core-moos through 10.4.0 fails to validate client identity in MOOSDB message processing, allowing authenticated attackers to attribute writes to other clients by supplying arbitrary source identifiers in serialized messages. Attackers can forge message origins and cancel third-party subscriptions by exploiting the disconnect between authenticated connection identity and wire-supplied source attribution.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
52(Track)
EG Risk 52/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 computed
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 8, 2026

Advisory Details (5)

Auto-updated Sep 3, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

MOOS core-moos through 10.4.0 MOOSDB Message Source Spoofing via Wire Identity | Advisories | VulnCheck

https://www.vulncheck.com/advisories/moos-core-moos-through-10.4.0-moosdb-message-source-spoofing-via-wire-identity
generic

core-moos/Core/libMOOS/DB/MOOSDB.cpp at ec9c77c68fcbdef8f5e4c60fe243acd223433f0c · themoos/core-moos · GitHub

https://github.com/themoos/core-moos/blob/ec9c77c68fcbdef8f5e4c60fe243acd223433f0c/Core/libMOOS/DB/MOOSDB.cpp#L748
generic

GitHub - themoos/core-moos: A very light weight, easy to use middleware. You will need core-moos above all other components · GitHub

https://github.com/themoos/core-moos
github_commit

commit 26308f0e393f (themoos/core-moos)

Fix landed in themoos/core-moos commit 26308f0e393f — awaiting tagged release

https://github.com/themoos/core-moos/commit/26308f0e393f0e80bfa09b275891e776b8dbf522
github_pr

Take a client's identity from its connection, not from its payload

Upstream fix in progress (PR #76 · themoos/core-moos, state=open)

https://github.com/themoos/core-moos/pull/76

Vendor Advisories for CVE-2026-85432(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 27× in last 7d / 64× 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.

  1. 2026-09-19 22:23 UTCEG score recompute
  2. 2026-09-19 22:23 UTCGHSA enrichment
  3. 2026-09-19 09:56 UTCGHSA enrichment
  4. 2026-09-18 21:28 UTCEG score recompute
  5. 2026-09-18 21:28 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 09:01 UTCGHSA enrichment
  8. 2026-09-17 20:33 UTCEG score recompute
  9. 2026-09-17 20:33 UTCGHSA enrichment
  10. 2026-09-17 19:32 UTCEPSS rescore
  11. 2026-09-17 06:59 UTCGHSA enrichment
  12. 2026-09-16 18:32 UTCEG score recompute
  13. 2026-09-16 18:31 UTCGHSA enrichment
  14. 2026-09-16 14:09 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-16 05:11 UTCGHSA enrichment
  17. 2026-09-15 16:44 UTCGHSA enrichment
  18. 2026-09-15 04:17 UTCEG score recompute
  19. 2026-09-15 04:17 UTCGHSA enrichment
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-14 15:49 UTCGHSA enrichment
  23. 2026-09-14 03:22 UTCEG score recompute
  24. 2026-09-14 03:22 UTCGHSA enrichment
  25. 2026-09-13 14:54 UTCGHSA enrichment
Show 39 more
  1. 2026-09-13 02:15 UTCEG score recompute
  2. 2026-09-13 02:15 UTCGHSA enrichment
  3. 2026-09-12 13:47 UTCGHSA enrichment
  4. 2026-09-12 01:20 UTCEG score recompute
  5. 2026-09-12 01:20 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 12:52 UTCEG score recompute
  9. 2026-09-11 12:52 UTCGHSA enrichment
  10. 2026-09-11 00:21 UTCGHSA enrichment
  11. 2026-09-10 11:53 UTCEG score recompute
  12. 2026-09-10 11:53 UTCGHSA enrichment
  13. 2026-09-09 23:26 UTCGHSA enrichment
  14. 2026-09-09 08:47 UTCEG score recompute
  15. 2026-09-09 08:47 UTCGHSA enrichment
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-08 20:20 UTCGHSA enrichment
  18. 2026-09-08 10:47 UTCGHSA enrichment
  19. 2026-09-08 10:44 UTCGHSA enrichment
  20. 2026-09-07 22:11 UTCEG score recompute
  21. 2026-09-07 22:11 UTCGHSA enrichment
  22. 2026-09-07 09:43 UTCGHSA enrichment
  23. 2026-09-06 21:11 UTCEG score recompute
  24. 2026-09-06 21:11 UTCGHSA enrichment
  25. 2026-09-06 13:48 UTCEPSS rescore
  26. 2026-09-06 08:43 UTCGHSA enrichment
  27. 2026-09-05 20:16 UTCEG score recompute
  28. 2026-09-05 20:15 UTCGHSA enrichment
  29. 2026-09-05 15:31 UTCEPSS rescore
  30. 2026-09-05 07:48 UTCGHSA enrichment
  31. 2026-09-04 19:21 UTCEG score recompute
  32. 2026-09-04 19:20 UTCGHSA enrichment
  33. 2026-09-04 18:41 UTCEG score recompute
  34. 2026-09-04 18:41 UTCGHSA enrichment
  35. 2026-09-04 11:57 UTCEG score recompute
  36. 2026-09-04 11:57 UTCGHSA enrichment
  37. 2026-09-03 23:30 UTCEG score recompute
  38. 2026-09-03 22:44 UTCEG score recompute
  39. 2026-09-03 22:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-85432?
CVE-2026-85432 is a high vulnerability published on September 3, 2026. MOOS core-moos through 10.4.0 fails to validate client identity in MOOSDB message processing, allowing authenticated attackers to attribute writes to other clients by supplying arbitrary source identifiers in serialized messages. Attackers can forge message origins and cancel third-party…
When was CVE-2026-85432 disclosed?
CVE-2026-85432 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85432 actively exploited?
CVE-2026-85432 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.7% of all scored CVEs.
What is the CVSS score of CVE-2026-85432?
CVE-2026-85432 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-85432?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85432, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-85432

Explore →

Is Your Infrastructure Affected by CVE-2026-85432?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs