{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51536 exists.","fix":"No fix has been published for CVE-2026-51536 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-51536 is a critical vulnerability in n/a, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-51536 and fix it if it is affected.\n\nWhat it is: CVE-2026-51536 is a critical vulnerability in n/a, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51536 exists.\n\nAffected product: n/a. 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-51536/ (Markdown: https://insights.sbomify.com/CVE-2026-51536/index.md)","id":"CVE-2026-51536","markdown":"https://insights.sbomify.com/CVE-2026-51536/index.md","name":"CVE-2026-51536","record":{"aliases":["GHSA-wfpp-whc2-qj45"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Industrial Protocol Stack","requires_auth":"none","summary":"A malicious CIP packet can trigger an integer overflow leading to a stack buffer overflow, allowing remote code execution or denial of service in OpENer.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opener","vendor":"opener_project"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"In OpENer 2.3.0 (commit 76b95cf) when parsing incoming CIP (Common Industrial Protocol) network packets, the length parameter is inconsistently typed across the call stack. Specifically, an upstream length calculated as an int is passed to a downstream function that expects an EipInt16 (a 16-bit signed integer). If a maliciously crafted packet with specific length fields is processed, the length parameter can overflow or be truncated into a negative value. This negative length bypasses subsequent bounds checking (due to signed/unsigned comparison issues) and is ultimately used in memory operations, leading to a Stack Buffer Overflow when reading data in DecodePaddedEPath.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Integer overflow in n/a","id":"CVE-2026-51536","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2026-51537"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2026-51535"},"products":["n/a"],"published":"2026-07-13","related":[{"cvss_score":10,"headline":"Memory corruption in OpENer","id":"CVE-2022-43604","kev_date_added":null,"published":"2023-03-16"},{"cvss_score":10,"headline":"Memory corruption in OpENer","id":"CVE-2022-43605","kev_date_added":null,"published":"2023-03-16"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2026-51540","kev_date_added":null,"published":"2026-07-13"},{"cvss_score":9.8,"headline":"Memory corruption in EIP Stack Group","id":"CVE-2020-13556","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2026-51537","kev_date_added":null,"published":"2026-07-13"},{"cvss_score":9.1,"headline":"Auth bypass in n/a","id":"CVE-2026-51538","kev_date_added":null,"published":"2026-07-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["n/a"]},"summary":"A malicious CIP packet can trigger an integer overflow leading to a stack buffer overflow, allowing remote code execution or denial of service in OpENer.","url":"https://insights.sbomify.com/CVE-2026-51536/"}