themoos core-moos up to 10.4.0 Serial Port GetTelegram off-by-one

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.2$0-$5k2.17

Summaryinfo

A vulnerability classified as problematic has been found in themoos core-moos up to 10.4.0. This impacts the function CMOOSSerialPort::GetTelegram of the component Serial Port. Performing a manipulation results in off-by-one. This vulnerability is cataloged as CVE-2026-85454. The attack must be initiated from a local position. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in themoos core-moos up to 10.4.0. This affects the function CMOOSSerialPort::GetTelegram of the component Serial Port. The manipulation with an unknown input leads to a off-by-one vulnerability. CWE is classifying the issue as CWE-193. A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value. This is going to have an impact on integrity, and availability. The summary by CVE is:

MOOS core-moos through 10.4.0 contains a buffer overflow vulnerability in CMOOSSerialPort::GetTelegram() that writes a NUL terminator one byte past the serial telegram stack buffer. Attackers controlling the serial line can send a full-length telegram to trigger the off-by-one write, corrupting the stack and potentially enabling code execution.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-85454 since 09/03/2026. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 5.2
VulDB Meta Temp Score: 5.2

VulDB Base Score: 4.4
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 6.1
CNA Vector (VulnCheck): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Off-by-one
CWE: CWE-193 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒

Physical: Yes
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

09/03/2026 CVE reserved
09/03/2026 +0 days VulDB entry created
09/04/2026 +0 days Advisory disclosed
09/04/2026 +0 days VulDB entry last update

Sourcesinfo

Product: github.com

Advisory: github.com
Status: Not defined

CVE: CVE-2026-85454 (🔒)
GCVE (CVE): GCVE-0-2026-85454
GCVE (VulDB): GCVE-100-398649

Entryinfo

Created: 09/04/2026 01:20
Changes: 09/04/2026 01:20 (75)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!