CVE Intelligence
Medium Memory corruption

CVE-2026-82943 — Out-of-Bounds Read via Unchecked Length Values

SOEM version 2.0.0 and earlier contains vulnerabilities where a malicious device can send messages that cause the master to read data from memory locations beyond the intended buffer. The software uses length values from device responses without validating them against actual buffer sizes. An attacker can exploit this to extract up to 64KB of data from the master's memory.

Published Oct 26, 2026 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: ENISA

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.17%
ahead of 6% of scored CVEs · Oct 30, 2026
Affects
RT-Labs AB
SOEM
CVSS base
6.5
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (RT-Labs AB SOEM).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
RT-Labs AB SOEM < 2.0.1 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.5 CVSS 3.1 Medium 2.8 3.6 a6d3dc9e-0591-4a13-bce7-0f5b31ff6158 via NIST National Vulnerability Database
6.5 CVSS 3.1 Medium — — ENISA via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: a6d3dc9e-0591-4a13-bce7-0f5b31ff6158)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-125 · Out-of-bounds Read

Other CVEs with this weakness →

EPSS over time FIRST

Oct 26, 2026 → Oct 30, 2026 · 5 reading(s) · max 0.17%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Awaiting Analysis
    Oct 26, 2026 · NIST National Vulnerability Database
  • Affected products added · rt-labs ab/soem
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 26, 2026
  • CVSS changed · 6.5
    Oct 26, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 26, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 26, 2026 · Alertas do Telegram
  • CVE published
    Oct 26, 2026 · ENISA

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 26, 2026 – Oct 26, 2026
  • 1× Official description updated · Oct 26, 2026 – Oct 26, 2026

References

1 on the record

Elsewhere on this site

RT-Labs AB
every CVE for this vendor
CWE-125
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-82944 Buffer Overflow in CoE SDO Upload Multi-Segment Data Transfers 5d
  • Medium CVE-2026-82945 Memory Corruption via FMMU Configuration Table Overflow 5d
  • Medium CVE-2026-82946 Null Pointer Dereference in Mailbox Error Handling 5d
  • High CVE-2026-82947 Multiple Out-of-Bounds Reads in Frame Processing 5d
  • High CVE-2026-70388 Memory Corruption via Integer Underflow in Message Length Validation 5d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-82943 is "Out-of-Bounds Read via Unchecked Length Values", rated Medium. It affects SOEM (RT-Labs AB); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.