LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22214: RIOT OS <= 2026.01-devel-317 Stack-Based Buffer Overflow in ethos Serial Frame Parser

RIOT OS versions up to and including 2026.01-devel-317 contain a stack-based buffer overflow vulnerability in the ethos utility due to missing bounds checking when processing incoming serial frame data. The vulnerability occurs in the _handle_char() function, where incoming frame bytes are appended to a fixed-size stack buffer without verifying that the current write index remains within bounds. An attacker capable of sending crafted serial or TCP-framed input can cause the current write index to exceed the buffer size, resulting in a write past the end of the stack buffer. This condition leads to memory corruption and application crash.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22214 is a stack buffer overflow in RIOT OS's ethos serial frame parser. Crafted serial or TCP-framed input can corrupt memory and crash the affected application. The provided sources rate it medium, with high availability impact, and do not show confirmed active exploitation.

Executive priority

Treat this as a moderate availability risk for RIOT OS devices using ethos. Prioritize exposed or safety-sensitive deployments first, because successful exploitation can crash applications, even though active exploitation is not confirmed.

Technical view

RIOT OS through 2026.01-devel-317 lacks bounds checking in ethos _handle_char(). Incoming frame bytes can be written past a fixed-size stack buffer, causing CWE-121 memory corruption and application crash. The source bundle does not name a fixed release or vendor patch.

Likely exposure

Exposure is most likely in embedded or IoT deployments using RIOT OS ethos where serial or TCP-framed input can reach the parser from less-trusted users, devices, or network paths.

Exploitation context

The bundle includes a public Full Disclosure reference tagged as exploit and a VulnCheck advisory, but KEV is false and no source provided confirms active exploitation in the wild.

Researcher notes

The key evidence is a CWE-121 write past a stack buffer in _handle_char() from unchecked frame-byte appends. Sources support crash and memory corruption impact, but not confidentiality loss, code execution, active exploitation, or a named fix.

Mitigation direction

  • Check RIOT OS and VulnCheck guidance for a fixed release or patch.
  • Restrict ethos serial and TCP-framed input to trusted sources only.
  • Avoid exposing ethos-related services across untrusted networks.
  • Prioritize upgrade planning for deployments at or before 2026.01-devel-317.
  • Monitor affected devices for crashes or unexpected restarts.

Validation and detection

  • Inventory RIOT OS versions across embedded and IoT assets.
  • Identify deployments using the ethos utility or serial frame parser.
  • Confirm whether untrusted serial or TCP-framed input can reach ethos.
  • Review vendor advisories for fixed versions before closing remediation.
  • Validate compensating controls restrict access to trusted sources.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-121: 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 lookup
cve · low confidence lookup

CVE-2026-22214 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.8CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

6.8Medium
CVSS 4.0 vector shape for CVE-2026-22214Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
RIOTRIOT OS0unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.