{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82944 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82944 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82944 is a high-severity vulnerability in RT-Labs AB SOEM, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-82944 and fix it if it is affected.\n\nWhat it is: CVE-2026-82944 is a high-severity vulnerability in RT-Labs AB SOEM, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-82944 in the wild and no public exploit code.\n\nAffected product: RT-Labs AB SOEM. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82944/ (Markdown: https://insights.sbomify.com/CVE-2026-82944/index.md)","id":"CVE-2026-82944","markdown":"https://insights.sbomify.com/CVE-2026-82944/index.md","name":"CVE-2026-82944","record":{"aliases":["GHSA-55h8-h3gv-wfcx"],"analysis":null,"analysis_generated_by":null,"assigner":"ENISA","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-131","name":"Incorrect Calculation of Buffer Size"},{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"SOEM version 2.0.0 and earlier contains a vulnerability in multi-segment data transfers where a malicious device can overflow memory buffers. The software checks the total size only once at the beginning, but doesn't track the cumulative size as multiple segments arrive. An attacker can declare a small initial size to pass validation, then send additional segments that exceed the allocated buffer. This allows the attacker to write controlled data beyond buffer boundaries, potentially enabling code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Buffer Overflow in CoE SDO Upload Multi-Segment Data Transfers","id":"CVE-2026-82944","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory Corruption via FMMU Configuration Table Overflow","id":"CVE-2026-82945"},"packages":[],"prev":{"headline":"Out-of-Bounds Read via Unchecked Length Values","id":"CVE-2026-82943"},"products":["SOEM"],"published":"2026-10-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-26","vendors":["RT-Labs AB"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-82944/"}