CVE-2026-85437
No exploitation reported by the sources we read.
- Published2026-09-03
- Fixed in24.8.1
- WeaknessCWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
MOOS-IvP through 24.8.1 contains multiple buffer overflow vulnerabilities in IvP function string decoders that trust attacker-controlled length fields without validation. Attackers can craft malicious encoded strings with mismatched declared and actual field lengths to overflow heap and stack buffers, potentially achieving remote code execution through MOOS variables or alog files.
Timeline
dates in UTC- 2026-09-0323:17CVE publishedNVD
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 24.8 | < 24.8.1 | 24.8.1 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As VulnCheck, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- moos-ivpother versions: not affectedAffected
- ≤ 24.8.1no fix statedcustom
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-09-03
Fix
- Update Mit moos-ivp to 24.8.1
Advisories and patches
- github.comPatch
- github.comPatch
- github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2026-09-04
- CNACVSS 4.09.3known since 2026-10-23
- CNACVSS 3.19.8known since 2026-10-23
- CNAweakness (CWE)CWE-787known since 2026-10-23
- FIRST EPSSEPSS score1.4 %2026-11-18
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-70803same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-g7c8-266j-mgr2same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CVSS 4.0 vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published
- 2026-09-03
- Last Modified
- 2026-10-14
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-g7c8-266j-mgr2
Frequently asked questions
What is CVE-2026-85437?
Is CVE-2026-85437 actively exploited?
What is the CVSS score for CVE-2026-85437?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-g7c8-266j-mgr2
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- CISA Vulnrichment · CC0-1.0